On Thursday, 12 October 2017 6:07:55 AM NZDT Greg Wilson-Lindberg wrote: > Thanks for the info, now I understand what is going on. Hopefully I can find > a way to get rid of the RPATH, I don't like ignoring errors or warnings. > > I've spent some more time looking into this, I haven't been able to find out > where the -rpath comes from. If I start a devshell none of the environment > variables have it set. In the run.do_compile log none of the environment > variables have it set, it's not set in the run.do_configure log. But in the > log.do_compile file the command that links the library: > > /home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/ > x86_64-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc ... > -Wl,-rpath,/usr/lib > > There it is at the end of the command line. > > As you can see the build for zint is based on CMake. Do you have any > suggestions as to where I can look to figure out how this is getting set, > I've done searches of all of the files in the zint download and the only > ones that have -rpath in them are some files that build a tcl based support > program that has its own autotools based build system.
This seems to be something that CMake handles itself. From a quick google which found the CMake wiki page on the subject [1], you may perhaps set CMAKE_SKIP_RPATH? In theory you could do that via EXTRA_OECMAKE in the recipe i.e. EXTRA_OECMAKE += "-DCMAKE_SKIP_RPATH=TRUE" Cheers, Paul [1] https://cmake.org/Wiki/CMake_RPATH_handling -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto