Re: [Orpg-devel] update

[Timothy P. <de...@ne...>]

Ok, so shall i delete the entire CVS & create 5 different empty projects =
there
with the various names? Will wait for confirmation before I do but should=
n't be
too much trouble.

Toolkit looks reasonable to me and should all be able to run in Windows. =
Im just
downlaoding CEGUI, Ogre and Eclipse to see if I can get the current CVS t=
o run.

CVS =3D CVSROOT, putting stuff in the module directories created (that wa=
y cvs co
module gets the entire stuff relevant to the module) I think?

By the custom libs do you mean enable CEGUI support? Sounds like a lot of=
 fun :(

Im in IRC when I can, but I left ICQ/MSN On at Uni so cant get onto that =
@ w/e.

Cheers,

Tim

Quoting George Mochrie <dr...@bl...>:

 the toolkit...

         gfx and various low level stuff: ogre
         interface: cegui
         physics: ode
         sound: openal
         network: hawknl?
         scripting: lua?

 ...and preferred IDE (eclipse) have been more or less decided on. The
 lack of automake support in eclipse is both a blessing and a curse. It
 complicates the build process on *nix, but the same build process should
 work on windows too. Together with the cross platform natures of all the
 other components this should make building on windows a relativly simple
 affair, requiring only specifying the correct build settings for each
 project.

 ogre 1.0 requires CEGUI 0.2 for it's user interface components and there
 is no deb. As I write this I am compiling my own versions of CEGUI and
 ogre (not for installation) to link orpg against. This is a pain but
 does allow us more control over the final binaries. I'll post
 instructions on building these 2 libs on debian once i have done it
 myself. It may be an idea to use custom versions of more of the
 libraries we use, perhaps even down to things like libjpeg. For now
 something that works with the GUI would be good :)

 um, i think i kinda messed up with cvs... where do i put stuff?

 we could do with scrubbing CVS TBH. Eclipse seems to have it's own way
 of doing things... we can share the same workspace via CVS, currently I
 have the ogre and CEGUI libraries in the workspace too, but as long as
 you tell CVS to ignore those directories it should be fine. Then all our
 options and settings will be shared. Currently orpg is 5 projects...

         orpgs (server) - The server process, will required ode and
         possible ogre too to be able to handle the 3d environment of the
         game.

         orpgc (player client) - The game

         orpga (admin client) - Like the NWN dmclient

         orpgb (world builder) - Models and maps and the like can be
         designed elsewhere, but they all get tied together into the game
         here.

         liborpg (game engine) - Provides a layer above the various
         libaries to provide a game engine.

 I'm still learning all of the stuff here, some of it i've not even
 started on.

 there's a lot more to write, but i'll do it later ;)





 -------------------------------------------------------
 SF email is sponsored by - The IT Product Guide
 Read honest & candid reviews on hundreds of IT Products from real users.
 Discover which products truly live up to the hype. Start reading now.
 http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
 _______________________________________________
 Orpg-devel mailing list
 Orp...@li...
 https://lists.sourceforge.net/lists/listinfo/orpg-devel