public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Mau Z <zmau1962@gmail.com>
Cc: crossgcc@sourceware.org
Subject: Re: Q: whald should I give my "customers" ?
Date: Mon, 30 Dec 2013 22:58:00 -0000	[thread overview]
Message-ID: <20131230225848.GB3472@free.fr> (raw)
In-Reply-To: <CAPFcPTJ6cxs4k1kGJfLPTu5AXqd+Ypyw67ECVeBbmffmGW+FiQ@mail.gmail.com>

Mau, All,

On 2013-12-31 00:41 +0200, Mau Z spake thusly:
> So, I had built a tool chain.
> Now, I have used it to create an image (root file system).
> Let's suppose that everything went OK, and all is good.

Yes, let's suppose that! ;-)

> Now, my "customers" are a group of application developers, which need
> the tool chain.
> They work on a different site, so I must somehow "deliver" the newly
> created toolchain.
> 
> The do not need the toolchain o the target, just on the development
> host  (their desktops).
> 
> What should I give them ?
>    1) Simply, the "x-tools" directory (300 MB) ?
>    2) Simply, the "x-tools/i686-zm-linux-gnu/bin" directory (21 MB) ?
>    3) any other suggestion ?

3) any other suggestion:
    the "x-tools/i686-zm-linux-gnu: directory as a whole.

;-)

> Are there instruction/advices that I should give them ? do's and don'ts ?

Do's: ensure all your 'users' will have a decent distro so the toolchain
runs on their machines. Alternatively, use yourself a distro that is as
old as the older distro your users may use.

Do's: if your 'users' distro are very disparate, you may want to build a
statically-linked toolchain, see:
    Toolchain options  --->
        [ ] Build Static Toolchain

Do's: preferably install the toolchain in /opt/x-tools/${CT_TARGET}
(or any other generic location) rather than in your home. This is not
strictly required, since toolchains generated with ct-ng are
relocatable, but cleaner nonetheless.

Dont's: expect no problem! :-p

> Is there a good or bad way to "deliver" the newly created toolchain ?

The simplest is just to create a tarball of your x-tools/i686-zm-linux-gnu
directory, and distribute that. Tell your 'users' to extract it wherever
they want, and export PATH="...../i686-zm-linux-gnu/bin:${PATH}"

Note that, if your 'users' are not in the same legal entity as you are,
then you do have some obligations due to the licensing terms og the
different tools you are using (GPLv2+, GPLv3+, LGPLv2.1+, and maybe
others), since you are in fact distributing the toolchain. Be sure to
understand that! ;-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

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

  reply	other threads:[~2013-12-30 22:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-30 22:41 Mau Z
2013-12-30 22:58 ` Yann E. MORIN [this message]
2013-12-30 23:07   ` Mau Z
2013-12-30 23:09   ` ANDY KENNEDY
2013-12-30 23:18     ` Mau Z
2013-12-31 18:57       ` Martin Guy
2013-12-31 19:40         ` Baruch Siach
2013-12-31 21:29           ` Mau Z

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=20131230225848.GB3472@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=crossgcc@sourceware.org \
    --cc=zmau1962@gmail.com \
    /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).