cvs.gedasymbols.org/archives/browse.cgi | search |
From: | "vdspek" <vdspek AT xs4all DOT nl> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | please help allegro 2 |
Date: | 1 Aug 1999 15:22:42 GMT |
Organization: | XS4ALL Internet BV |
Lines: | 21 |
Message-ID: | <01bd4789$8f067a60$258d6dc2@default> |
References: | <01bd470d$d16efa20$21806dc2 AT default> <4EPo3.16757$yD2 DOT 36631 AT newsfeeds DOT bigpond DOT com> |
NNTP-Posting-Host: | dc2-modem3365.dial.xs4all.nl |
X-Trace: | news1.xs4all.nl 933520962 11634 194.109.141.37 (1 Aug 1999 15:22:42 GMT) |
X-Complaints-To: | abuse AT xs4all DOT nl |
NNTP-Posting-Date: | 1 Aug 1999 15:22:42 GMT |
X-Newsreader: | Microsoft Internet News 4.70.1155 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
> > > >I compiled liballeg.a sucessfully, but I cat seem to compile > >any code that uses Winallegro_Handlemessages() in which > >library does it reside, what should I link? should it be in liballeg.a? > >Am I overlooking a PATH setting? I cant find any reference in the docs. > >Please help. > > > It would be helpful if you posted some code that exhibited this problem, as well as the > compile command(s). > Well, it's also the examples provided with the dist. of allegro that have this problem. As I said, anything that uses Winallegro. the example i.q. is ex13.c in allegro/examples the rest compiles fine. Jochem
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |