From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id: <199808182021.WAA17803@father.ludd.luth.se>
Subject: Re: djlsr and include files
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Tue, 18 Aug 1998 22:21:17 +0200 (MET DST)
Cc: djgpp-workers AT delorie DOT com (DJGPP-WORKERS)
In-Reply-To: <Pine.SUN.3.91.980818145245.12510O-100000@is> from Eli Zaretskii at "Aug 18, 98 02:54:00 pm"
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

According to Eli Zaretskii:
> On Sun, 16 Aug 1998, DJ Delorie wrote:
> > > Shouldn't djlsr*.zip include everything necessary to put together
> > > djdev*.zip? I. e. the include files for djgpp/include/ ?
> > 
> > This is a conflict between the "source is what you need to build" and
> > "don't replicate files between zips" rules.  Since most people
> > interested in the sources have djdev installed also, I went with the
> > "don't replicate" rule instead.
> 
> In addition, at least for native builds, you will need several files in 
> lib, like libc.a, specs etc.  So some version of djdev is required 
> anyway.

But it was exactly cross-compiling I was thinking about. And it would
make sense to include everything needed for djdev (and perhaps other
packages, djcrs (sp?)?) in djlsr. It doesn't make sense to have to
download djdev when you can't use it (except you have to, to get the
headers). 

Or is it so that djcrs (ot what its name is, the cross-package)
contains everything needed to build djcrs and djdev (so that package
is really djlsr)?


Cocteau Twins, Victorialand,

							MartinS