When i execute b2.exe, I receive an error: link.jam: no such file or directory Then it compiles ok but with hardcoded paths. This may be the reason for not recognizing hardcode-dll-paths? -----Original Message----- From: Vladimir Prus <ghost@cs.msu.su> To: "boost-users@lists.boost.org" <boost-users@lists.boost.org> Sent: Fri, 10 Jan 2014 9:00 PM Subject: Re: [Boost-users] Cross compiling boost Windows -> Arm On 10.01.2014 22:47, Marius Adrian DOBRESCU wrote:
Hello. I have a problem compiling boost with arm-none-linux-gnueabi-g++ on Windows. Shared library dependencies paths seems to be hard-coded with Windows paths:
Example: build\bin.v2\libs\filesystem\build\gcc-arm\release\target-os-linux\threading-multi\...
I tried to build with --prefix. Not working. Hardcode-dll-paths not working too. Tried to specify an explicit -rpath. The so shared libraries are compiled with hard-coded paths inside, with backslash \\\ and I cannot use them on linux-arm. On stage directory they are hard-coded too.
Any idea how can I disable this behavior and what options should I pass to boost and where?
I want simple libraries without full rpaths and the build must be done on Windows with gcc-gnueabi.
Marius, Did you try: b2 hardcode-dll-paths=false ? What's the exact command line you've used for building? Also, I am not sure what's the exact problem you're having. While using host paths for cross-compiling is certainly wrong, I would have expected dynamic linker to just ignore paths that are not valid. - Volodya _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org<mailto:Boost-users@lists.boost.org> http://lists.boost.org/mailman/listinfo.cgi/boost-users