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] |
Hi Chris,i agree that libraries like libusb etc. should normally not part of the toolchain. But sometimes it seems to be easier to provide a complete toolchain to someone else containing those libraries (if required in special versions)
than providing an rootfs or similar wich contains them. Regards Tobias #Am 16.02.2016 um 21:01 schrieb Chris Packham:
Hi Tobias, On 02/16/2016 07:40 PM, Tobias Andresen wrote:Hi, what would be the best way to add additional libraries and header files (i.e. libusb, ...) to an existing toolchain or add them to the build process of crosstools-ng so the user can select a special version like glibc etc. Thanks in advance.Generally you wouldn't add libraries to crosstool-ng. glibc/uclibc/musl are special because gcc needs to be built against the specific libc implementation. libusb and others aren't required by gcc so don't generally fit the bill. What I suspect you want is a build system that works with toolchains produced by crosstool-ng. Buildroot (https://buildroot.org) is one such build system but I'm sure there are others.
-- 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] |