Re: CMake build system progress

Hi Felix,

Thanks for taking a careful look. There were some details I missed. In
short, the concerns you addressed should have been fixed in fc349da.
Please test and send me more complaints.

On 05/22/2014 16:12, Felix Salfelder wrote:
> $ chrpath /tmp/my/little/place/bin/gnucap
> /tmp/my/little/place/bin/gnucap: RPATH=/home/felix/extern/gnucap-upstream/cmake_build/lib:/home/felix/extern/gnucap-upstream/cmake_build/apps
> 
> this is incorrect.

This is the result of my 'gnucap-ui' installation hack. CMake
automatically changes the RPATH for each built executable on install,
but did not for 'gnucap' because I used a hack.

Now I've done things the "correct" way and this problem should be gone.

> also
> $ ldd /tmp/my/little/place/bin/gnucap
> [..]
> libgnucap-default-plugins.so => /home/felix/extern/gnucap-upstream/cmake_build/apps/libgnucap-default-plugins.so (0x00007fc0bf28f000)
> [..]
> 
> is wrong. plugins are supposed to be dlopened, not dynamically linked (and the
> same with main/gnucap-ui).

Fixed.

> and
> $ chrpath /tmp/my/little/place/lib/x86_64-linux-gnu/libgnucap.so
> /tmp/my/little/place/lib/x86_64-linux-gnu/libgnucap.so: no rpath or runpath tag found.
> 
> it's probably better, if the plugin loader code (c_attach.cc, part of
> libgnucap.so) knows where the plugins are supposed to be.

I need to take a look at this.

Thanks,
Kevin Zheng