1
0
forked from 0ad/0ad
0ad/source/workspaces/gcc/readme.txt
2004-05-13 17:21:27 +00:00

34 lines
1.2 KiB
Plaintext
Executable File

Linux build instructions
The Linux build is, so far, a bit hackish. Things might not work on another
system than mine, but it should work. The source/gcc/ folder contains some
header files that exist to override and bug-fix some system headers. If you
have trouble with them, try renaming the offending header, and see if it does
you any good ;-)
What do I need?
- Xerces-C++ installed and in standard include path
- glext.h - you can put it in source/gcc/GL/ if you don't have access to the
system include path
- The Makefile is made for GCC 3.x.x - GCC 2.x might work, but it's not likely
Where are built things put?
The linux makefile follows the general directory layout of the VS workspaces:
source/gcc/: makefile, system header overrides
binaries/: The built binaries - called "prometheus"
source/gcc/deps/: Automatically generated dependency information for all
source files
source/gcc/o/: Object files
Makefile Targets:
all (default): build the prometheus executable
prof: build the prometheus.prof executable (instrumented version with call-counting)
clean: Remove all object, depend, and executable files
run: build prometheus and run it (from the binaries directory)
runProf: build prometheus.prof and run it