[OpenWalnut-Dev] Installing OpenWalnut

[Mathias Goldau]

As to expect it didn't work on Mac OSX:

0#18:04:55#math at ipansen# build/release
>/usr/local/openwalnut/bin/OpenWalnut
dyld: Library not loaded: libOWcore.dylib
  Referenced from: /usr/local/openwalnut/bin/walnut
  Reason: image not found
/usr/local/openwalnut/bin/OpenWalnut: line 11: 25617 Trace/BPT trap
     bin/walnut $@

maybe the environment variable is named differently. But this has worked
(tested NavSlices and ImageSpaceLIC):
0#18:05:32#math at ipansen# build/release
>DYLD_LIBRARY_PATH=/usr/local/openwalnut/lib
/usr/local/openwalnut/bin/walnut

cheers math

Am 25.05.11 15:21, schrieb Mathias Goldau:
> Ok, I've installed in /usr/local/openwalnut and everything worked on my linux box. Mac OSX did not compile ATM..
> 
> What I've tried:
>  * /usr/local/openwalnut/bin/OpenWalnut
>  * LD_LIBRARY_PATH=/usr/local/openwalnut/lib /usr/local/openwalnut/bin/walnut
>  * Symlinking /usr/local/openwalnut/bin/* to /usr/local/bin as well as the same for openwalnut/lib and executing just walnut
> 
> math
> 
> 
> Am 24.05.2011 18:18, Sebastian Eichelbaum wrote:
>> Hi List
>>
>> I set up CMake to provide an install target. Issuing make install should put all the binaries, libs, shaders, resources and so
>> on to your CMAKE_INSTALL_PREFIX. This can be set by either ccmake or cmake -D CMAKE_INSTALL_PREFIX=/your/path. Please try this
>> on your machine. Specify a tmp path or something and call "make install". Then, change to the directory and call
>> "bin/OpenWalnut". This file is needed due to the fact, that cmake strips the rpath (real paths to linked libs) from each binary
>> and lib. So the walnut binary is not able to find its needed libOWcore.so and libOWext libs except they were installed to a
>> directory which is known by ld (can be configured in /etc/ld.so.conf or /etc/ld.so.conf.d/ (depending on system)). The same
>> accounts for third party libs which where installed somewhere outside the standard unix paths. Example: you installed teem to
>> /opt/teem like me. Then, the module lib using teem has the path hard-coded in it and works as expected if used from within
>> build dir. After installation, this path was stripped and the module lib is not able to find it anymore. Again, to solve this,
>> add /opt/teem/lib to your ld.so.conf. The OpenWalnut script sets the LD_PRELOAD environmetn variable to point the binary to the
>> _correct_ libs. This has certain advantages, especially if you have multiple walnut installations. Of course, this is only
>> needed if installed on non-standard locations.
>>
>> Additionally, I created FreeDesktop.org conform menu files, an Icon and several other small stuff.  By the way: these files
>> contain an classification for the menu entry in categories. I only specified science there. Please have a look at 
>> http://standards.freedesktop.org/menu-spec/latest/apa.html and maybe you find another useful category.
>>
>> What is not yet working: ========================
>>
>> * headers don't get installed - on most Unix systems, they have to be provided in an additional install target/package *
>> doxygen doc is not installed - similar to headers, programming doc should be delivered separately
>>
>> Whats next: ===========
>>
>> * I will provide extra targets for both * Use of CPack for generating packages (deb, rpm, mac bundle supported (according to
>> their doc))
>>
>> What do I want you to do: =========================
>>
>> * Test installation process!
>>
>> Long-Term Goal: ===============
>>
>> Besides the packages, I want to separate OWcore/OWqt4gui development from module development. OpenWalnut should be a framework,
>> which can be used as ever other lib (like FIND_PACKAGE( OpenWalnut REQUIRED)). This eases development for module-coders and
>> eases us (especially me) to maintain OpenWalnut.
>>
>>
>> Questions? Ask!
>>
>> Bye Sebastian
>>
> 
>