g++ -o cscursor.so ./out/macosxppc/optimize/plugins/video/cursor/cursor.o  -lm -lmx -ldl -Wl,-multiply_defined,suppress -L/usr/local/lib ./out/macosxppc/optimize/libs/libcrystalspace.a -lz -lm -lmx -ldl -Wl,-multiply_defined,suppress -L/usr/local/lib
  ld: Undefined symbols:
_main

Something is wrong with your configuration. It's trying to build each plugin as an application rather than as a dynamic library (bundle). You may have somehow tricked it into thinking that you're running Linux or Darwin. It would be useful to see the output of your configure run.

The Crystalspace Project uses the JAM build system and make is only wrapped around it, please attempt type "jam" after configure instead of "make -k all"

The build system support "make" just as well as it supports "jam". You are free to, and encouraged to, use whichever command feels most comfortable.

Most fairly recent versions of gcc (both 3.x and 4.x) work. There are some known bugs in gcc 4.0.0 and/or 4.0.1 which cause CS to crash, though.

Did you verify for certain that the build command uses the proper compiler and linker flags for CEGUI? On Windows, the latest version of cs-win32libs contains a pre-built copy of CEGUI which should just work "out-of-the-box", so to speak.

Make sure that you're using the correct version of cs-win32libs for the version of CS you've downloaded. Also make sure that you use the correct documentation (which differs between the CS 0.98 release and the CVS source).

Normally, it's best if all the versions and/or dates match.

I tried compilng Knoppix linux 3.9 and gcc 3.3.6 and that is okay.
Can gcc version make error? /3.3.4/

Possibly, depending upon what headers / types the gcc version exports, and/or what compiler features the source requires.

That depends upon what format data the editor exports. If it can export something which CS can import, then it should be compatible. If it has its own custom format, then CS does not support it, though it should be possible write some sort of converter or importer for CS.

Code:

include/iutil/string.h:264: error: type specifier omitted for parameter
  `va_list'
include/iutil/string.h:264: error: parse error before `)' token

It looks like it's all just this one error. What does line 264 (and perhaps the surrounding lines) look like?

Those warnings are new as of today since those functions will be removed in the near future. Code which is using those functions will be rewritten to use more recent API before too long.

At any rate, you didn't show the actual error messages which caused 5 targets to fail building. For additional assistance, you will want to present the error messages from those failures.

Newer versions of cs-win32libs provide a better default for the location of the CS directory, but you may still need to change it if your CS directory is not at the expected location.

CS is designed to be embeddable into other application frameworks, such as QT and wxWidgets, for example. In these cases, you allow QT's or wxWidget's run-loop to drive the application rather than using CS's fallback csDefaultRunLoop(). The wxWidgets-specific application CS/apps/tests/wxtest and canvas plugin CS/plugins/video/canvas/wxgl should provide clues to how this may be done in QT.

Other than C#, Delphi, those features are all supported. For C# integration, the best bet would be to extend CS's already-mature Swig-based scripting integration. Swig is a tool which allows clients to access a C or C++ SDK from other languages. C# is one of the languages supported by Swig. The Swig support in CS is generalized so that the bulk of the API is exposed to other languages through a generic mechanism (CS/include/ivaria/cspace.i), and to add a new language you only need to provide some relatively thin language-specific customization atop cspace.i. For instance, for Python, there are additional Swig input files CS/include/ivaria/pythpre.i, pythpost.i, pyeventh.i, and pythvarg.i. If you are interested in implementing the C# goop atop the existing generic Swig goop, I'm sure that other people would appreciate having it integrated into the project.

Your CEL installation is probably too old. CEL_ZONE_NORMAL was added to CEL on 2005/11/27. Try to grab fresh copies of all projects.

You will find Swig input files (*.i) for Python, Perl, and Java in CS/include/ivaria/.

Code:

configure: creating ./config.status
./config.status: Files/CrystalSpaceLibs/tools/jam: No such file or directory
config.status: creating Jamfile

Unix-style build systems, such as that in CS work a lot better if paths do not contain embedded spaces, such as "c:/Program Files/CrystalSpaceLibs". When you installed cs-win32libs, it should have warned you about this problem and suggested that you choose an alternate location.

Have you consulted the build instructions in the CS manual? There is a section for each supported platform.

http://www.crystalspace3d.org/docs/online/manual/