This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See crosstool-NG for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Help: verify / package expected crosstool-ng build outcomes


Hello,

After some trial and error, I believe I have finally build an ARM
cross compiler using the GCC 4.7.2 tool chain.

I am a little out of my comfort zone here, so a little insight would be grand.

Next steps are to tell Qt Creator (?), or possibly Mentor Graphics
CodeBench, about the tools, build a simple app, verify it for the x86
desktop, then see it build using cross compiler and see it run on
device.

What I've got it seems is a package in the form of /opt/x-tools/TARGET
(original name I know), which appears to be an
arm-unknown-linux-gnueabi directory which includes the gcc, g++, ld,
and other tools we would need to build cross compiler? And some
includes and libraries and such.

* How do we go about packaging the cross compiler itself for other
developers among our team?

* Or about telling our development IDE's that the tool chain exists?

Thanks in advance.

Regards,

Michael Powell

--
For unsubscribe information see http://sourceware.org/lists.html#faq


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]