From:	Charles Terry <cterry AT plinet DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Installing Allegro
Date:	Fri, 17 Apr 1998 08:43:53 -0700
Organization:	All USENET -- http://www.Supernews.com
Lines:	39
Message-ID:	<353778B9.825@plinet.com>
References:	<D1FB30BBA491D1118E6D006097BCAE3927FB0D AT Probe-nt-2a DOT Probe DOT co DOT uk>
NNTP-Posting-Host:	1924 AT 207 DOT 174 DOT 3 DOT 110
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Shawn Hargreaves wrote:
> 
> Charles Terry writes:
> > I don't know exactly why it happend but
> > when I built the allegro library, <liballeg.a>it created it but
> > didn't copy it to the %DJDIR%/lib directory.  I did it manually.
> 
> That is rather worrying. It would be good if someone who has seen
> this problem could investigate it, and try to find out why the
> copy call is failing...
> 
> > make all (i think) will build all the examples,tools,info docs,
> > and the library, whereas make only builds the library.
> 
> Not true. The default action is to build everything: you only
> need to select other targets if you want to specifically recompile
> a particular program.
> 
>         Shawn Hargreaves.
Well I'll add what I can.
I thought somthing like make all was nessary because after the
copy failed the library wasn't available for the build of the
other stuff in the package. I copied the library before
trying to build the other stuff then did the packages individually.
I got mail from the guy who started this thread and thats how he ended
up doing it too.
There was a huge thread about the copy command not being able
to deal with '/' in makefiles this last week, right?

I unzipped to c:\djgpp\allegro
and I'm using Dos 6.2 
and as far as I know I'm not using any replacement commandline
packages.

As a contribution to the allegro project maybe I'll stash my allegro
stuff and try it again and pay attention.
I'll let you know.
Charles Terry

- Raw text -