Open Emerix opened 11 years ago
Apparently I'm an idiot. I blame the lack of caffeine
The application you build HAS to use the same toolchain you used to compile boost. The build-android.sh seems to default to the 4.6 toolchain while Nvidia Nsight Tegra Visual Studio Edition defaults to 4.7.2
Would be lovely if we could pick the toolchain with a parameter for the boost compilation
Thats a good idea, how would you like to pick the tool chain? with just a configuration value or an argument?
On Thu, Mar 28, 2013 at 1:43 PM, Emerix notifications@github.com wrote:
Apparently I'm an idiot. I blame the lack of caffeine
The application you build HAS to use the same toolchain you used to compile boost. The build-android.sh seems to default to the 4.6 toolchain while Nvidia Nsight Tegra Visual Studio Edition defaults to 4.7.2
Would be lovely if we could pick the toolchain with a parameter for the boost compilation
— Reply to this email directly or view it on GitHubhttps://github.com/MysticTreeGames/Boost-for-Android/issues/24#issuecomment-15586389 .
Moritz Wundke www.MysticTreeGames.com www.DarkCultureGames.com http://www.darkculturegames.com/
I'd suggest leaving it as is for default and if you want another maybe adding -toolchain46 (or the others) as a parameter for calling build-android.sh
Yep that seams to be the best option.
On Sat, Mar 30, 2013 at 4:32 PM, Emerix notifications@github.com wrote:
I'd suggest leaving it as is for default and if you want another maybe adding -toolchain46 (or the others) as a parameter for calling build-android.sh
— Reply to this email directly or view it on GitHubhttps://github.com/MysticTreeGames/Boost-for-Android/issues/24#issuecomment-15676365 .
Moritz Wundke www.MysticTreeGames.com www.DarkCultureGames.com http://www.darkculturegames.com/
Hey there!
I'm getting the following weird errors when linking my project against the boost libraries. Any idea where that might be coming from? I don't suppose renaming the files by taking the -gcc-mt from the filename broke anything.
I compiled the 1.53 Boost with the official NDK 8d according to your instructions on my Ubuntu VM
1>Link: 1>
.LTHUNK0' referenced in section
.text._ZN5boost16exception_detail10bad_alloc_D1Ev[_ZN5boost16exception_detail10bad_alloc_D1Ev]' of D:/master/svn/ogre/ogre/AndroidDependencies/lib\libboost_thread.a(thread.o): defined in discarded section.text._ZN5boost16exception_detail10bad_alloc_D2Ev[_ZN5boost16exception_detail10bad_alloc_D5Ev]' of D:/master/svn/ogre/ogre/AndroidDependencies/lib\libboost_thread.a(thread.o) 1>
.LTHUNK2' referenced in section.text._ZN5boost16exception_detail14bad_exception_D1Ev[_ZN5boost16exception_detail14bad_exception_D1Ev]' of D:/master/svn/ogre/ogre/AndroidDependencies/lib\libboost_thread.a(thread.o): defined in discarded section
.text._ZN5boost16exception_detail14bad_exception_D2Ev[_ZN5boost16exception_detail14bad_exception_D5Ev]' of D:/master/svn/ogre/ogre/AndroidDependencies/lib\libboost_thread.a(thread.o) 1>.LTHUNK30' referenced in section
.text._ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED1Ev]' of D:/master/svn/ogre/ogre/AndroidDependencies/lib\libboost_thread.a(thread.o): defined in discarded section.text._ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED5Ev]' of D:/master/svn/ogre/ogre/AndroidDependencies/lib\libboost_thread.a(thread.o) 1>
.LTHUNK36' referenced in section.text._ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED1Ev]' of D:/master/svn/ogre/ogre/AndroidDependencies/lib\libboost_thread.a(thread.o): defined in discarded section
.text._ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED5Ev]' of D:/master/svn/ogre/ogre/AndroidDependencies/lib\libboost_thread.a(thread.o) 1>collect2.exe : error : ld returned 1 exit status