Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <002d01c2dc60$06dd4210$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Charles Krug" <charles AT pentek DOT com>, <cygwin AT cygwin DOT com>
References: <20030224223818 DOT GO14960 AT pentek DOT com>
Subject: Re: Minimum Install for Executable Distrubution
Date: Mon, 24 Feb 2003 23:54:10 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Charles Krug wrote:
> Cygwinners:
>
> We've built the gcc/as/ld toolset as a cross compiler to the Altavec
> PowerPC.  We've been using it internally for a couple of weeks.
>
> Those of us with full developer Cygwin installations can run the
> program with no problems.
>
> We'd like to be able to distribute a minimal package to everyone here
> who needs the cross compile capability.
>
> Our first attempts seem to get confused about the correct paths to the
> executables.
>
> This is our first venture into distributing executables to people who
> haven't downloaded the entire package.  What do we need to do to give
> people in the package?
>
> My thought based on the symptoms I've seen is that the gcc tools,
> being UNIX-centric will require at least a minimal official Cygwin
> setup, otherwise it won't grok the mount points.
>
> A coworker believes, "There MUST be a way to build it so that that's
> not necessary,"

You could attempt to build a MinGW-hosted Altavec-cross toolchain.

> To which I reply, "Perhaps, but would it be worth the trouble?"

Quite possibly not.

> I BELIEVE the correct course of action would be to do a default Cygwin
> install and then distribute our cross development toolset.  Would
> there be any problems doing it that way?  Most important (to me), is
> there a Cygwin tool for assembling the correct packages?

cygwin.com, follow "Contributing - Cygwin Packages" for info on package
building.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/