Mail Archives: djgpp/1997/06/09/07:03:58
Jacob Martin wrote:
>
> ERROR MESSAGES!!!
>
> E:\DJGPP\EXAMPLES>gcc ex1.c
I'm not using allegro so often, but the first thing I do
when I get a new package is to read the readme's:
Here are some parts of them:
readme.txt:
[snip]
============================================
============ Installing Allegro ============
============================================
[snip]
See allegro.txt for instructions on linking your program with
Allegro.
and now allegro.txt:
=======================================
============ Using Allegro ============
=======================================
See readme.txt for a general introduction, copyright details, and
instructions on how to compile Allegro.
All the Allegro functions, variables, and data structures are defined in
allegro.h. You should include this in your programs, and link with
liballeg.a. There are various ways you can do this:
- Give full paths for everything, eg:
#include </allegro/allegro.h>
gcc foobar.c -o foobar.exe /allegro/liballeg.a
- Add your Allegro directory to the include and library search paths
with
the -I and -L compiler options, eg:
#include <allegro.h>
gcc -I/allegro -L/allegro foobar.c -o foobar.exe -lalleg
- Add your Allegro directory to the C_INCLUDE_PATH,
CPLUS_INCLUDE_PATH,
and LIBRARY_PATH in djgpp.env, and then:
#include <allegro.h>
gcc foobar.c -o foobar.exe -lalleg
Robert
--
*****************************************************************
* Robert Hoehne, Fakultaet fuer Mathematik, TU-Chemnitz-Zwickau *
* Post: Am Berg 3, D-09573 Dittmannsdorf *
* e-Mail: Robert DOT Hoehne AT Mathematik DOT TU-Chemnitz DOT DE *
* WWW: http://www.tu-chemnitz.de/~rho *
*****************************************************************
- Raw text -