Re: [Boost-users] Boost configure options for crosscompilation ?
This is the command line I used to build boost using Bjam for an arm platform, not sure if that helps with what you need, but here it is anyway!! bjam "-sGCC_ROOT_DIRECTORY=/opt/montavista/mobilinux/devkit/arm/iwmmxt_le" "-sGCC=iwmmxt_le-gcc" "-sGXX=iwmmxt_le-g++" stage Stage is the folder in which all the libs are placed, other parameters should be self explanatory. James
-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of MikeW Sent: 20 November 2006 15:59 To: boost-users@lists.boost.org Subject: [Boost-users] Boost configure options for crosscompilation ?
I would like to crosscompile Boost under Buildroot.
I created what appeared to be a successful package file, but found that the native compiler and tools were used rather that Buildroot's crosscompiler toolchain.
However, I could not see any other 'configure' options to switch to using a crosscompiler (EPREFIX looked promising at first but seems to be a path prefix, rather than a tool prefix such as "arm-linux-").
I note an earlier post (unable to post a 'follow-up' to it) seemed to successfully do a cross build.
Could you tell me how Boost is 'configure'd to use the crosstools rather than the native tools ?
Thanks, Mike
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.
Hughes, James <jhughes <at> linx.co.uk> writes:
This is the command line I used to build boost using Bjam for an arm platform, not sure if that helps with what you need, but here it is anyway!!
bjam "-sGCC_ROOT_DIRECTORY=/opt/montavista/mobilinux/devkit/arm/iwmmxt_le" "-sGCC=iwmmxt_le-gcc" "-sGXX=iwmmxt_le-g++" stage
Stage is the folder in which all the libs are placed, other parameters should be self explanatory.
James
Thanks, but boost_1_33_1 is distributed with a 'configure' file, and it should be possible to set options on this to get a cross-build. Just need to set a "arm-linux" prefix on each of the toolnames ... somehow. Even so, will have a look at your command to see if/how it can be used. Thanks. Mike
MikeW wrote:
Hughes, James <jhughes <at> linx.co.uk> writes:
This is the command line I used to build boost using Bjam for an arm platform, not sure if that helps with what you need, but here it is anyway!!
bjam "-sGCC_ROOT_DIRECTORY=/opt/montavista/mobilinux/devkit/arm/iwmmxt_le" "-sGCC=iwmmxt_le-gcc" "-sGXX=iwmmxt_le-g++" stage
Stage is the folder in which all the libs are placed, other parameters should be self explanatory.
James
Thanks, but boost_1_33_1 is distributed with a 'configure' file, and it should be possible to set options on this to get a cross-build.
What makes you think it "should be possible"? The configure script is just a thin shell around the bjam commands. And by thin I mean it does not support all, or even many, of the build options possible when using bjam directly. Although technically you could setenv all the above variables James mentions, and then run configure+make. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Rene Rivera <grafikrobot <at> gmail.com> writes:
MikeW wrote:
Thanks, but boost_1_33_1 is distributed with a 'configure' file, and it should be possible to set options on this to get a cross-build.
What makes you think it "should be possible"? The configure script is just a thin shell around the bjam commands. And by thin I mean it does not support all, or even many, of the build options possible when using bjam directly. Although technically you could setenv all the above variables James mentions, and then run configure+make.
Thank you, I must admit I had come to that conclusion. When I said "should be possible" I suppose I was expressing dissatisfaction with the extent to which the existing configure script supported the underlying bjam options. OK, I know, "if it doesn't suit you - write your own" ! I realise that the GNU build system is just one out of the many configuations that Boost attempts to support, I just wish it paid more than lip-service to it, since it appeared to build happily under my ARM-configured Buildroot setup ... except that the built libraries were all "arch=i386" ;-) Maybe as more people try to use Boost under the GNU build rather than as a command-line bjam build, this aspect will improve. Time pressures mean I won't be able to do this at the moment, will just have to hack in a command-line bjam build (or set env the lot ?) Regards, Mike
Hughes, James <jhughes <at> linx.co.uk> writes:
This is the command line I used to build boost using Bjam for an arm platform, not sure if that helps with what you need, but here it is anyway!!
bjam "-sGCC_ROOT_DIRECTORY=/opt/montavista/mobilinux/devkit/arm/iwmmxt_le" "-sGCC=iwmmxt_le-gcc" "-sGXX=iwmmxt_le-g++" stage
Stage is the folder in which all the libs are placed, other parameters should be self explanatory.
James
Thanks, I finally got this to build by inserting "GCC=$(STAGING_DIR)/arm-elf-linux" in my $(MAKE) .... all target in the boost.mk file in my Buildroot system. [Though I think I'm going to have to change the toolchain to use "arm-linux-eabi" soon] Had to explicitly state 'arm-elf-linux' so that the unprefixed tool names (e.g. gcc, ld ...) as used by boost build would work OK. Couldn't find an option to prefix 'arm-elf-linux-' to all the toolnames; the above-mentioned GCC and GXX options don't affect the rest of the tools. There ought to be a TOOL_PREFIX option ... Thanks again, Mike
MikeW <mw_phil <at> yahoo.co.uk> writes:
Thanks, I finally got this to build by inserting "GCC_ROOT_DIRECTORY=$(STAGING_DIR)/arm-elf-linux" in my $(MAKE) .... all target in the boost.mk file in my Buildroot system.
OOPS !! TYPO !! *GCC_ROOT_DIRECTORY* Sorry.
participants (3)
-
Hughes, James -
MikeW -
Rene Rivera