The thing is, one can't build PS until CS has been built correctly.So you won't have libcrystalspace.lib until that very first step was achieved successfuly.Build errors with CS tend to be due to not correctly setting up your dev environment(ie. not following instructions from the manual).Please try restarting building CS from scratch until there are no errors then, and only after achieving this successfuly,try to rebuild PS.You may get more direct help on PS build IRC channel, or #crystalspace (on freenode server too).

Please open a new discussion thread, stating your environment dev spec (OS, compiler version, CS version & revision),and the exact errors you get (ie. ./walktest -console -verbose=-scf output).This thread is so old I'd have locked it if I could

jam install is really optional, and in fact should only be used by packagers.One problem with it is that there's no uninstall target, so you have to do it by hand,and may run into problems when you update or run other versions.

jam distclean removes all files produced by compilation, so that only should bedone when you want to restart building from scratch.Stick to ./configure && jam and you'll be fine.

it seems you're building Planeshift, but you don't mention whether CS was previously built without any error,nor if the libcrystalspace.lib file exists.Did you follow instructions (both CS & PS) for MSVC build to the letter ?Did you try asking in #psbuild (or #planeshift-build, don't remember the exact name) IRC channel on freenode.net ?Sorry can't help much, I'm definitely not familiar with MSVC...

I can't provide a really detailed answer, since I never used spr2d, but give some pointers.Everything which is done from XML can be done from code, or how else would CS itself do ? The trick is to check the loader code for this object type, in this case I guesscsSprite2DLoader::Parse() in plugins/mesh/spr2d/persist/standard/spr2dldr.cppA quick look there reveals that the material wrapper is to be set using iMeshObject interface(with 1.4; iirc there was some refactoring a while ago to make spr2d behave more like other meshes).Good luck, and keep us posted about your progress...

that sounds like a "real world" need Since 1.4, there are CS::Geometry::Triangulate3D functions, maybe those can help you.I'll point Jorrit and/or Scott to this post when I see them on IRC, but it may be faster if you asked on CS mailing list about this.

By the way, you really should follow the instructions from the manual matching your CS version.And maybe you just have to set some "current working directory" setting from MSVC to the pathwere all the plugins are.

I'll try to answer, from what I understand in the question... I guess you're talking about walktut ?Anyway...In the application (app.cpp) you can see that when an entity is created in CreatePlayer(),a behaviour is set for it (player_behave) and a set of property classes are attached to the entity.In the behaviour code (behaviour.cpp), it is said that when 'player_behave' named behaviour is requested,the BehaviourPlayer class should be used.Now, this class will receive messages (that is, its SendMessage() member will be called)depending on the property classes the entity has.For example, the entity was attached 'pctools.inventory' propclass, so its behaviour will receive allmessages that this propclass sends, namely pcinventory_addchild and pcinventory_removechild uponaddition and removal of inventory elements (other entities).Each time a propclass sends a message to the player's entity behaviour, BehaviourPlayer::SendMessage()is called, with a "message ID" (so one can distinguish what message was sent), and possibly a parameterblock, which in case of an inventory message holds the entity which was added or removed.

I hope this clears things up a bit.Also note that this is with the "old" messaging system, with the newer one one can just subscribe to message,there's no separate class for behaviour, if I understood it well

When CS is installed, there should be no need to set CRYSTAL environment variable.For CEL, I'm not sure, it's been quite a while since I tried.It would be interesting to check the config.log file, and see the exact reason why the usability check failed...

yes, you need Python 2.5 since that's what the binaries were linked against.There should be no problem with having both 2.5 and 2.6 installed on the same machine.You just may have to create a little scripts which make sure 2.5 is found in PATH before 2.6,and perhaps also set PYTHONHOME to the 2.5 install directory.