Benjamin Reed wrote: > It looks like there's some kind of post-processing going on during a > make install, but if using DESTDIR, you get errors like this: > > -- Installing /opt/roots/kdelibs/opt/kde4/bin/dcopserver > install_name_tool: can't open file: /opt/kde4/bin/dcopserver (No such > file or directory) > -- Installing /opt/roots/kdelibs/opt/kde4/lib/libDCOP.dylib.5.0.0 > -- Installing /opt/roots/kdelibs/opt/kde4/include/dcopclient.h > -- Installing /opt/roots/kdelibs/opt/kde4/include/dcopobject.h > -- Installing /opt/roots/kdelibs/opt/kde4/include/dcopstub.h > -- Installing /opt/roots/kdelibs/opt/kde4/include/dcopref.h > -- Installing /opt/roots/kdelibs/opt/kde4/include/dcoptypes.h > -- Installing /opt/roots/kdelibs/opt/kde4/include/kdatastream.h > -- Installing /opt/roots/kdelibs/opt/kde4/lib/libkdeinit_dcopserver.dylib > install_name_tool: can't open file: > /opt/kde4/lib/libkdeinit_dcopserver.dylib (No such file or directory)
CMake translates the install_name of the binaries using install_name_tool when they are installed. It looks like the code generated to do this does not account for DESTDIR. This is probably a CMake bug which I'll investigate fixing for the 2.4.3 release. -Brad _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
