delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/03/11/09:25:56

From: gfoot AT mc31 DOT merton DOT ox DOT ac DOT uk (George Foot)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro configuration problem
Date: 11 Mar 1997 11:12:04 GMT
Organization: Oxford University
Lines: 28
Message-ID: <5g3em4$f8p@news.ox.ac.uk>
References: <3324A2D9 DOT 778D AT hotmail DOT com>
NNTP-Posting-Host: mc31.merton.ox.ac.uk
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

rocket88 (rocket88 AT hotmail DOT com) wrote:
: Hi,
: I am having a problem compiling Allegro.  When I run make.exe, is it
: from the command line and what do I use as input?  Also when I enter
: "alleg" in Rhides options/lib,  the compiler doesnt recognize it (I get
: an error)
: What do I need to do to get up and running.  I have the faqs, but I
: guess I am missing the answer somewhere.

To build Allegro, you should simply go to the Allegro directory (wherever 
you put it) and type `make', on its own, with no parameters. If this gives
file not found, you need to download mak375b.zip from your distribution 
site and unzip this with the -d parameter into your D:\DJGPP directory.

The reason you can't link in the alleg library is that you haven't 
successfully built it yet - you have to get make to finish its job first.

Note that to compile Allegro you also need all the C++ development tools,
because some of the utility programs are written in C++.

: My machine setup has 2 hard drives, (c&d) with both djgpp and allegro
: on d.  my autoexec looks like:

You AUTOEXEC.BAT looks fine to me.

-- 
George Foot <gfoot AT mc31 DOT merton DOT ox DOT ac DOT uk>
Merton College, Oxford.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019