From: "Chris A. Triebel" Newsgroups: comp.os.msdos.djgpp Subject: Re: ALLEGRO Date: Mon, 30 Sep 1996 12:38:42 -0400 Organization: University of New Hampshire - Durham, NH Lines: 62 Message-ID: References: <52mojj$20k AT shore4 DOT intercom DOT net> <324F4117 DOT 1AD AT cs DOT com> NNTP-Posting-Host: sun4.iol.unh.edu Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <324F4117.1AD@cs.com> To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp On Sun, 29 Sep 1996, John M. Aldrich wrote: > Date: Sun, 29 SEP 1996 20:40:07 -0700 > From: John M. Aldrich > To: Jeremy Ford > Newgroups: comp.os.msdos.djgpp > Subject: Re: ALLEGRO > > Jeremy Ford wrote: > > > > Hello, > > > > I just downloaded ALLEGRO for DJGPP and I was wondering how you > > installed it. The documentation says something about running make.exe > > but when I unzip allegro file to c:\allegro there is no make.exe > > file...could someone send me that file or tell me how to compile > > allogro so I can use it... > > You don't need to recompile allegro to use it with your programs. > Allegro should come with the file 'liballeg.a' which you should place in > the \lib directory of your DJGPP installation. It should also include > the necessary header files. Like the library, you can install them in > your \include directory, but it is preferable to simply modify the > C_INCLUDE_PATH and CPLUS_INCLUDE_PATH to put the allegro include > directory on the end. Then just #include the allegro headers like any > other headers and link liballeg.a when you compile. RHIDE has options > to do these things automatically. > > Rebuilding allegro is only necessary if you need to change some part of > it for some reason. > > -- > --------------------------------------------------------------------- > | John M. Aldrich, aka Fighteer I | fighteer AT cs DOT com | > | Plan: To find ANYONE willing to | http://www.cs.com/fighteer | > | play Descent 2 on DWANGO! | Tagline: | > --------------------------------------------------------------------- > > Um ... I don't think allegro came with any compiled code. If I remember correctly, I don't have the .zip file in front of me, allegro was distributed as source only to conserve on space. This would then have to be built into liballeg.a and the setup and test files. Check /contrib/allegro/ for the the makefile ... I think that is where it has been stuck. At any rate it is in the route directory of the allegro sources, wherever they were put. Find the file ... Yes I just checked www.delorie.com in their list and extract area. If the makefile truly does not exist look in http://www.delorie.com/djgpp/dl/ofc/simtel.cgi/simtel/v2tk/ Select alleg21.zip and download the makefile from there. cat ------------------------------------------------------------------------------- "It's not the programming languages that will kill you, its the syntax." "Digging a hole with a bulldozer is much more effective, unless you only know how to use a shovel."