From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11859 invoked by alias); 30 Dec 2013 23:18:18 -0000 Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org Received: (qmail 11845 invoked by uid 89); 30 Dec 2013 23:18:18 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=3.5 required=5.0 tests=AWL,BAYES_05,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,LIKELY_SPAM_BODY,RCVD_IN_DNSWL_LOW,SPAM_SUBJECT1,SPF_PASS autolearn=no version=3.3.2 X-HELO: mail-wi0-f182.google.com Received: from mail-wi0-f182.google.com (HELO mail-wi0-f182.google.com) (209.85.212.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Mon, 30 Dec 2013 23:18:17 +0000 Received: by mail-wi0-f182.google.com with SMTP id en1so12043545wid.9 for ; Mon, 30 Dec 2013 15:18:14 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.86.103 with SMTP id o7mr38975353wiz.6.1388445494477; Mon, 30 Dec 2013 15:18:14 -0800 (PST) Received: by 10.194.6.69 with HTTP; Mon, 30 Dec 2013 15:18:14 -0800 (PST) In-Reply-To: References: <20131230225848.GB3472@free.fr> Date: Mon, 30 Dec 2013 23:18:00 -0000 Message-ID: Subject: Re: Q: whald should I give my "customers" ? From: Mau Z To: ANDY KENNEDY Cc: "Yann E. MORIN" , "crossgcc@sourceware.org" Content-Type: text/plain; charset=ISO-8859-1 X-SW-Source: 2013-12/txt/msg00050.txt.bz2 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 wrote: > >> > 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