I believe I got cel to compile, you should give a example with the instructions, like :ex (C:/duh/cs) then it will be (export CRYSTAL=/c/duh/cs) and (export PATH=$PATH:/c/duh/cs)
This time I down load the latest CVS SNAPSHOT unstable version. Don't see any cel files that be use for test and I still don't see a configure and jam file for CRYSTAL CORE.
Here's the cel compile log.
Tony@TONY-763C465C03 /c/cs/cs/cel
$ export CRYSTAL=/C/CS/CS
Tony@TONY-763C465C03 /c/cs/cs/cel
$ export PATH=$PATH:/C/CS/CS
Tony@TONY-763C465C03 /c/cs/cs/cel
$ ./configure
checking build system type... i686-pc-mingw32
checking host system type... i686-pc-mingw32
checking how to create a directory... mkdir
checking how to create a directory tree... mkdir -p
checking for gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to treat C++ warnings as errors... -Werror
checking how to enable C++ PIC generation... no
checking if -shared is accepted... -shared
checking if -soname is accepted... yes
checking for install... install
checking for ranlib... ranlib
checking for doxygen... no
checking for makeinfo... makeinfo
checking for perl5... no
checking for perl... no
checking for perl5... no
checking for perl... no
checking for swig... no
checking how to enable C++ compilation warnings... -Wall
checking how to suppress C++ unused variable warnings... -Wno-unused
checking how to suppress C++ uninitialized warnings... -Wno-uninitialized
checking for pthread... no
checking how to suppress C++ `long double' warnings... no
checking for python... no
checking for pkg-config... no
checking for cppunit-config... no
checking for libcppunit... no
checking for cs-config... /C/CS/CS/cs-config
checking if Crystal Space version >= 0.99... yes (version 0.99)
checking if Crystal Space SDK is usable... yes
checking for Crystal Space static plugins... no
checking build mode... optimize
configure: creating ./config.status
config.status: creating Jamfile
config.status: executing Jamconfig commands
configure:
Please note that this project uses Jam as its build tool,
therefore you must type 'jam' to build the project.
Jam home:
http://www.perforce.com/jam/jam.htmlJam source:
ftp://ftp.perforce.com/jam/Tony@TONY-763C465C03 /c/cs/cs/cel
$ checking for pthread... no
sh: checking: command not found
Tony@TONY-763C465C03 /c/cs/cs/cel
$ checking how to suppress C++ `long double' warnings... no
> checking for python... no
> checking for pkg-config... no
> checking for cppunit-config... no
> checking for libcppunit... no
> checking for cs-config... /C/CS/CS/cs-config
> checking if Crystal Space version >= 0.99... yes (version 0.99)
> checking if Crystal Space SDK is usable... yes
> checking for Crystal Space static plugins... no
> checking build mode... optimize
> configure: creating ./config.status
> config.status: creating Jamfile
> config.status: executing Jamconfig commands
> configure:
>
> Please note that this project uses Jam as its build tool,
> therefore you must type 'jam' to build the project.
>
> Jam home:
http://www.perforce.com/jam/jam.html> Jam source:
ftp://ftp.perforce.com/jam/>
>
> Tony@TONY-763C465C03 /c/cs/cs/cel
> $~