|From:||Brandon J. Van Every|
|Subject:||Re: [Chicken-users] libffi & cmake|
|Date:||Tue, 20 Feb 2007 14:46:18 -0800|
|User-agent:||Thunderbird 188.8.131.52 (Windows/20061207)|
Mario Domenech Goulart wrote:
Hi Brandon, On Tue, 20 Feb 2007 11:58:58 -0800 "Brandon J. Van Every" <address@hidden> wrote:Mario Domenech Goulart wrote:I'm trying to build Chicken using cmake under GNU/Linux. I can't find a way to enable/disable the compilation with/without libffi.There is no such option in the CMake build. If ffi.h exists on the system, -lffi is added to the linker flags. Is there a reason to disable libffi even when it's available on the system? We could add such an option, but what's the justification for it?Borked systems (mine, for example). :-) I don't know why, but I could not compile Chicken with libffi on my machine. I may be wrong, but I'm pretty sure it's a local problem, since I could build it fine on another system. Anyway, using configure's --without-libffi I could at least have a running Chicken.
If the system can work fine, but is currently borked, then you should fix it. This is true for any build environment on any system.
If all such systems are borked, then if you can define the borking, we can put some system-specific IF(bork) code in there.
If you want a quick 'n' dirty hack for your personal use, just go into CMakeLists.txt and comment out the ffi.h stuff. But I don't see a reason to support that kind of operation with a special build flag. Rather, I think you should find out why it's borked, so we can do what should be done.
Brandon Van Every
|[Prev in Thread]||Current Thread||[Next in Thread]|