delorie.com/archives/browse.cgi | search |
Message-ID: | <37900886.2B86@iquest.net> |
From: | Jeremy Brown <peart2112Remove AT iquest DOT net> |
Organization: | Purdue University |
X-Mailer: | Mozilla 3.0Gold (Win95; I) |
MIME-Version: | 1.0 |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: allegro troubles |
References: | <378F9063 DOT 1D1 AT iquest DOT net> <378F94D1 DOT 2B27 AT ns DOT sympatico DOT ca> |
Lines: | 26 |
Date: | Fri, 16 Jul 1999 23:37:26 -0500 |
NNTP-Posting-Host: | 209.43.17.206 |
X-Trace: | news1.iquest.net 932186264 209.43.17.206 (Fri, 16 Jul 1999 23:37:44 EDT) |
NNTP-Posting-Date: | Fri, 16 Jul 1999 23:37:44 EDT |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
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 -- "I can't pretend a stranger is a long awaited friend."-Neil Peart peart AT purdue DOT edu http://expert.cc.purdue.edu/~brown6
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |