Re: CMake build system progress

On Mon, Jun 09, 2014 at 07:30:17PM -0500, Kevin Zheng wrote:
> Sorry for the belated fix, could you check abcfc37 in cmake-WIP to see
> if RPATH is now correctly installed?

Hi Kevin.

nevermind. i've got other things to do as well, and the issue turns out
to be more complex :(

$ mkdir cmakebuild
$ cd !$
$ cmake ..; make install

i get
$ chrpath /usr/local/bin/gnucap
/usr/local/bin/gnucap RPATH=/usr/local/lib/x86_64-linux-gnu:/usr/local/lib/x86_64-linux-gnu/gnucap

this is not particularly wrong, bug the second entry is never required.

then, running gnucap from builddir does not work.

$ chrpath main/gnucap 
main/gnucap: RPATH=/home/felix/extern/gnucap-upstream/cmakeb/lib:::::::::::::::::::::::::
$ chrpath lib/libgnucap.so 
lib/libgnucap.so: RPATH=::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
$ main/gnucap
[..]
load libgnucap-default-plugins.so
     ^ ? libgnucap-default-plugins.so: cannot open shared object file: No such file or directory
[..]

autotools uses libtool and the implementation does not support plugins
either. my workaround is potentially suboptimal (and not tested) wrt.
portability, but at least this works on linux. (can somebody tell me how
it fails on non-linux?).

also this thread [1] about the brokenness of RPATH (on linux), libtool,
portability and everything is elucidating. as it seems you decided to
set RPATH in main/gnucap by default (ftr: i'm now convinced that this is
wrong, see [1]). is there a cmake option that lets me disable it?

cheers
felix

[1] https://lists.debian.org/debian-devel/1999/01/thrd5.html#02245