The easiest answer is that you should probably go ahead and try the 0.24 
dev version, because last summer I spent a couple months working over 
the build system to make it easier to deal with the dependencies.  In 
particular, it now supports automatically downloading the correct 
versions of Boost and Crystal Space from our site and compiling them for 
you, and then installing them in a staging directory so that VOS can 
find it and build against it.

We're long overdue for a new release based on the 0.24 branch, but 
before that happens we should decide what new features (if any) are 
going to go in -- in particular anything that would make a good demo for 
when I show VOS to potential donors/investors.  One thing that would be 
pretty easy would be some basic interactivity like like a "clickable" 
type that would let you send a message to the server when you clicked on 
a certain object, so you could trigger server-side events from it.

On the topic of GNU autotools vs. Visual Studio, it's an unfortunate 
maintanance hassle to have two parallel build systems.  I've been 
experimenting with scripts that generate Visual Studio project files 
automatically from the Makefiles [1].  That does mean that you need to 
have Cygwin or Mingw set up to properly edit the build system, even on 

[1] It's a Frankenstein combination of GNU make, sed, m4 and shell 
scripting that can be found in "autovcproj.mak", "autovcproj.m4" and 
autosln.m4 in the VOS source directory.

I've looked at some other build systems (particularly Jam) and come to 
the conclusion that while many of them are certainly better than plain 
hand-maintained makefiles, they don't actually stand up so well in 
comparison to the full GNU autotools suite.  

Unfortunately, compiling cross-platform software is inherently 

On Sun, Feb 18, 2007 at 02:27:48PM -0800, Ken Taylor wrote:
> Hi all,
> I've been going through the gamut of trying to get everything in 0.23 to
> compile (Once I master that, I'll move on to the 0.24 dev version). I'm
> using the MINGW/MSYS environment under windows2000 and got the base VOS
> libraries and example programs compiling fine. The only hack I needed to do
> was due to me using windows2000 instead of XP, and is described in my post
> here
> Now I've compiled crystal space and ter'angreal... I got all the building to
> work (I needed to remove cygwin from my execution path, because cygwin's
> pkg-config was confusing the configure process) but when I try to run
> ter'angreal it gives me the error
> crystalspace.pluginmgr.loadplugin:
>   could not load plugin ''
> crystalspace.application.terangreal:  No iVosA3DL plugin!
> This implies to me that when I configured crystal space, it didn't correctly
> find the a3dl libraries. Going back through config.log, it looks like indeed
> the checks for a3dl failed. They failed, apparently, because the a3dl
> headers did not compile because it could not find the *boost* headers...
> Under msys, my filesystem looks like this:
> /usr/local -- all the headers from vos and crystal space got installed here
> /usr/local/vos-win32-mingw-libs-0.23.0 -- boost and wxwidgets are under here
> I configured crystal space with the following command line:
> ./configure --with-metaobject_a3dl=/usr/local
> I guess my question is -- what's the preferred method of getting a3dl to
> correctly find boost? Should I just merge my vos-win32-mingw-libs-0.23.0
> directory down into my normal /usr/local? Or is there some command line
> option I should use when configuring?
> If it matters, I'm using the pre-packaged CS version from
> CS-2006-04-15.tar.gz, and I'm using crystal space's library package
> CrystalSpaceLibs0.99r0_022 to cover all the other crystal space libs.
> Thanks!
> -Ken
> (ps, I've never really used a gnu-style build environment before, so it's
> pretty fun learning all this stuff.  I could just go ahead and make the
> project under visual studio, but I wanted at least two build methods working
> (MS-style and GNU-style) so if I ever get around to writing patches I could
> test them and make sure they build both ways.)
> _______________________________________________
> vos-d mailing list

[   Peter Amstutz  ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ]
[Lead Programmer][Interreality Project][Virtual Reality for the Internet]
[ VOS: Next Generation Internet Communication][ ]
[ ][ pgpkey:  18C21DF7 ]

Attachment: signature.asc
Description: Digital signature

vos-d mailing list

Reply via email to