Re: CMake build system progress

Hi Kevin.

On Thu, May 22, 2014 at 01:55:52PM -0500, Kevin Zheng wrote:
> Committed in c8538cb, please have a look.

paths and list of files look good to me.

now there are some library related issues.

what i did
$ cmake -DCMAKE_INSTALL_PREFIX:PATH=/tmp/my/little/place ..
$ make install

then

$ 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.

$ ldd /tmp/my/little/place/bin/gnucap
linux-vdso.so.1 (0x00007fffa4fff000)
libgnucap.so => /home/felix/extern/gnucap-upstream/cmake_build/lib/libgnucap.so (0x00007fc0bf722000)
[..]

it should read
libgnucap.so => /tmp/my/little/place/lib/<triplet>/libgnucap.so (0x00007fc0bf722000)

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).

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.

from what i remember, these things should work within my autotools branch. i
might be wrong. please consider to have a look.
$ git checkout autotools
$ ./bootstrap
$ mkdir autotools_build
$ cd !$
$ ../configure --prefix=/tmp/somewhere
$ make install
$ (ldd, chrpath etc.)

regards
felix