Hi Eric,

thanks, that helped, indeed! I commented out the check for libRT. Moreover, I adjusted the hardcoded include location for the qt headers. I provide that via the CPATH environment variable, but I guess one could supply it through a command line switch if needed. In any case, the cool thing is that waf configure now completes without complaining.

Next I tried building the whole thing. The problem is that the build fails because it doesn’t seem to find some boost headers (array.h and chrono.h), and it also doesn’t find the log4cxx symbols. 

I’ll see whether I can sort these out - it’s probably just a matter of setting some include and library paths for the build. I’ll dig into the waf scripts and keep you posted :) 

Thanks in advance,

Michael


> On 6 Oct 2015, at 11:13, Eric Müller <[log in to unmask]> wrote:
> 
> Hi Michael,
> 
> the waf build system uses the "wscript" files for configuration and build.
> It's Python-based (which is just one ++ ;)) => use "#" to comment out lines.
> 
> => Just try to comment out this line in spikeyhal/wscript (line 114 for me):
>    conf.check_cxx(lib='rt', uselib_store='RT', mandatory=1)
>    # alternatively, try to set "mandatory" to "False" (or 0)
> 
> Non-existing "uselibs" (like RT in this case) do NOT trigger an error, so you
> don't need any further changes.
> 
> Cheers,
> Eric
> 
> 
> 
> Quoting Michael Schmuker <[log in to unmask]>:
> 
>> Hi,
>> 
>> Eric, thanks for your help. I got a bit further by using
>> 
>> $ LIBRARY_PATH=<path_to_googletest_build> CPATH=<path_to_googletest_include> ./waf configure --boost-includes ... --boost-libs …
>> 
>> Two other dependencies then emerged, first gsl (which was straightforward to install with homebrew), and Qt - I used Qt4 from the anaconda python distribution and added the paths to the respective environment variables for the compiler.
>> 
>> However, now the dependency on librt is a real dealbreaker. Librt is not available on OSX. Going by the forums, this seems to be a rather common problem on OSX (and somehow linked to Qt), and it is often solved by simply not linking against rt, without loss of functionality (maybe some of the librt symbols are provided by some other standard lib on OSX).
>> 
>> Is there an easy way to skip the test for librt presence, and tell the linker not to link against librt? I assume that this means tweaking the build system. Unfortunately my waf skills are definitely underdeveloped, and I can’t figure out how to do this.
>> 
>> Any hints or ideas? Many thanks in advance :)
>> 
>> Best,
>> 
>> Michael
>> 
>> P.S.: By the way, why does Spikeyhal require Qt? Could Spikeyhal be built without it, without loss of core functionality?
>> 
>> 
>> 
>>> On 1 Oct 2015, at 17:33, Eric Müller <[log in to unmask]> wrote:
>>> 
>>> Hey Michael,
>>> 
>>> the standard GCC env vars should work (i.e. that's a workaround ;-)).
>>> In this case:
>>> 
>>> $ export CPLUS_INCLUDE_PATH=/to/parent/dir/of/gtest/folder # or CPATH
>>> $ waf configure
>>> 
>>> Cheers,
>>> Eric
>>> 
>>> 
>>> Am 01.10.2015 18:11 schrieb Michael Schmuker <[log in to unmask]>:
>>>> 
>>>> Dear Spikey-Users,
>>>> 
>>>> I’m trying to build the spikey-demo package on OSX. I installed log4cxx and libusb via homebrew, and I use the latest boost via the anaconda python distribution. This made waf configure happy. But one problem is still remaining:
>>>> 
>>>> I wasn’t able to point waf to the GoogleTest library, which is in a custom location on my machine. Is there a command line switch or an environment variable that I can use to point waf to the gtest headers?
>>>> 
>>>> Thanks in advance,
>>>> 
>>>> Michael
> -- 
> gggqGZZ
> 
> ########################################################################
> 
> To unsubscribe from the KIP-SPIKEY-USERS list, click the following link:
> http://listserv.uni-heidelberg.de/cgi-bin/wa?TICKET=NzM1OTA3IG0uc2NobXVrZXJAQklPTUFDSElORUxFQVJOSU5HLk5FVCBLSVAtU1BJS0VZLVVTRVJTINKZx7t3Of66&c=SIGNOFF



Michael Schmuker
School of Engineering and Informatics
University of Sussex
http://biomachinelearning.net

########################################################################

To unsubscribe from the KIP-SPIKEY-USERS list, click the following link:
https://listserv.uni-heidelberg.de/cgi-bin/wa?SUBED1=KIP-SPIKEY-USERS