hmm still not having much luck here...
the problem seems to be that I don't know how to control the final rpath on the resulting libcpprest.so (I'm a total cmake noob, so that's not helping either).
what it is doing currently is setting rpath to the absolute path to my new boost libs, which I guess it is doing because those are calculated dependencies of libcpprest. That creates two problems, firstly, that path will be invalid when I deploy and second, it let's my old system libstdc++ so get pulled into the mix.
My plan was to use $ORIGIN/newlibs as my rpath and then have all the new boost/gcc so's in the 'newlibs' relative folder ... self contained and away from my old system libs
But I just don't know how to control rpath in a cmake build ... any tips would be greatly appreciated (the cmake manual looks pretty daunting)
the problem seems to be that I don't know how to control the final rpath on the resulting libcpprest.so (I'm a total cmake noob, so that's not helping either).
what it is doing currently is setting rpath to the absolute path to my new boost libs, which I guess it is doing because those are calculated dependencies of libcpprest. That creates two problems, firstly, that path will be invalid when I deploy and second, it let's my old system libstdc++ so get pulled into the mix.
My plan was to use $ORIGIN/newlibs as my rpath and then have all the new boost/gcc so's in the 'newlibs' relative folder ... self contained and away from my old system libs
But I just don't know how to control rpath in a cmake build ... any tips would be greatly appreciated (the cmake manual looks pretty daunting)
