From: sproctor AT enter DOT net (Sean)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: allegro troubles
Date: Mon, 19 Jul 1999 21:47:02 GMT
Message-ID: <379f9ca1.28521772@news.enter.net>
References: <378F9063 DOT 1D1 AT iquest DOT net> <378F94D1 DOT 2B27 AT ns DOT sympatico DOT ca> <37900886 DOT 2B86 AT iquest DOT net>
X-Newsreader: Forte Agent 1.5/32.452
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 207.16.154.41
X-Original-NNTP-Posting-Host: 207.16.154.41
X-Trace: 19 Jul 1999 17:47:54 -0400, 207.16.154.41
Organization: Enter.Net
Lines: 26
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

On Fri, 16 Jul 1999 23:37:26 -0500, Jeremy Brown
<peart2112Remove AT iquest DOT net> wrote:

>Okay,
>
>	I tried using this '-lalleg' as a command line option while compiling
>same thing and as obvious as it may sound I am including allegro.h, but
>in the case of allegro should i use the '""' or the '<>' I think it's
>probably more proper to use the double quotes as for it linking with
>liballeg.a I'm not quite sure wether it is or not what do I to tell if
>it is or not?  As far as if my system can handle it it should it
>compiled every example program without worries.
>
>Something else maybe?
>
>Jeremy
>
>
>> 
>> Are you including allegro.h?
>> Linking with liballeg.a?
>> 
>> -Mike
use <>  read the allegro docs and such, they tell you what to do.

Sean