public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Tobias Andresen <tobiasarp@web.de>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
	"crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Add additional libraries and header files to toolchain
Date: Wed, 17 Feb 2016 06:34:00 -0000	[thread overview]
Message-ID: <56C41474.6000404@web.de> (raw)
In-Reply-To: <54d4b67f30bd4a0cb8075fab6c203d38@svr-chch-ex1.atlnz.lc>

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

  reply	other threads:[~2016-02-17  6:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16  6:39 Tobias Andresen
2016-02-16 20:01 ` Chris Packham
2016-02-17  6:34   ` Tobias Andresen [this message]
2016-02-17 16:30     ` Dan Wilder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56C41474.6000404@web.de \
    --to=tobiasarp@web.de \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=crossgcc@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).