Re: Q: whald should I give my "customers" ?

[Mau Z <zmau1962 at gmail dot com>]

Thanks again (worth a lot for me).

I have no  problems with licenses (all in the same city).

I thought that the idea is that the whole system is compiled with the
same toolchain (rootfs + drivers + applications).
Is'nt it so ?

But this leeds me to snother question which deserves a separate thread.....


Thanks
Mau


On Tue, Dec 31, 2013 at 1:09 AM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
> <snip>
>> > 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! ;-)
>
> I would almost say to install the ct-ng locally, build the toolchain,
> then do the following command
>
> for i in .build/* ; test ! ".build/tarballs" = "$i" && rm -rf $i ; done
>
> finally package up the whole local install, providing a short installer
> script (like runme or something) that would allow the user to configure
> ct-ng locally, build the toolchain, and viola!  You are there (without
> any problems with licenses, machine binary differences, and the toolchain
> would be dynamically built -- which is FAR EASIER to do than build it
> statically (I've had problems with statically linked gcc's and such).
>
> That would be my 0.02 USD.
>
> Andy

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