Show Posts
1
Technical Help: Problems BEFORE entering the game /
« on: February 15, 2005, 06:00:46 am »
Tharizdun, you should be aware that with a clean CVS build of recent (Feburary 15, 2005) cal3d, some CrystalSpace Plugins may not compile.
For instance, the sprcal3d plugin (./CS/out/linuxx86/optimize/plugins/mesh/sprcal3d/object/sprcal3d.o) needs to have the CalCoreMesh * on 366 of sprcal3d.cpp and the following addCoreMesh(coremesh) on 369 changed to CalCoreMeshPtr and addCoreMesh(coremesh.get()) respectively.
There are at least two other places this same error has been made in this file alone. In both cases, substituing the RefPtr and the pointer getter will fix the problem. However, since the getter returns a const pointer, some badly behaved code may still get in trouble when playing with that pointer\'s value.
After those fixes, CrystalSpace should compile fine.
For someone who doesn\'t develop C/C++ software, knowing how to fix problems with RefPtr (http://www.elcel.com/docs/opentop/API/ot/RefPtr.html) based C++ code outside of the original developer\'s environment can be a bit tricky, if not neigh impossible.
For instance, the sprcal3d plugin (./CS/out/linuxx86/optimize/plugins/mesh/sprcal3d/object/sprcal3d.o) needs to have the CalCoreMesh * on 366 of sprcal3d.cpp and the following addCoreMesh(coremesh) on 369 changed to CalCoreMeshPtr and addCoreMesh(coremesh.get()) respectively.
There are at least two other places this same error has been made in this file alone. In both cases, substituing the RefPtr and the pointer getter will fix the problem. However, since the getter returns a const pointer, some badly behaved code may still get in trouble when playing with that pointer\'s value.
After those fixes, CrystalSpace should compile fine.
For someone who doesn\'t develop C/C++ software, knowing how to fix problems with RefPtr (http://www.elcel.com/docs/opentop/API/ot/RefPtr.html) based C++ code outside of the original developer\'s environment can be a bit tricky, if not neigh impossible.