Occulis
13-05-2006 15:19:09
I'm confused as to exactly which MapEditor and PLSM2 project is "the right one", who is working on it, and where I can help. Actually, I'm confused over several things and it's not for lack of reading. Maybe I can help answer these questions and update the wiki once I know for sure what the deal is.
1) Are Falagard and Tuan working together on one project, multiple projects, or none at all?
2) Is the map editor at http://tuan.kuranes.free.fr/Ogre.html the same as the one in OgreAddons? The main page says, "plsm2 is in OgreAddons CVS", but the two distributions differ.
3) Why are there different distribution methods with different file sets? IE:
PLSM Distribution method 1:
1) Are Falagard and Tuan working together on one project, multiple projects, or none at all?
2) Is the map editor at http://tuan.kuranes.free.fr/Ogre.html the same as the one in OgreAddons? The main page says, "plsm2 is in OgreAddons CVS", but the two distributions differ.
3) Why are there different distribution methods with different file sets? IE:
PLSM Distribution method 1:
- Downloaded http://tuan.kuranes.free.fr/OgreSDK_PLSM2_source.zip[/*:m]
- Extracted everything into C:\dev\3rdparty\compile\plsm[/*:m]
- Projects were extracted into C:\dev\3rdparty\compile\plsm\Samples\PagingLandScape2\scripts[/*:m]
- Loaded C:\dev\3rdparty\compile\plsm\plsm2.sln -- It's missing Samples\MapEditor\scripts\MapEditor.vcproj[/*:m]
- Actually, it's missing the whole Samples\MapEditor\ subdirectory. The only one it has is PagingLandScape2.[/*:m]
- Ran diffs between unzipped files and the current ogreaddons cvs. Only diffs are that files are missing.[/*:m][/list:u]
PLSM Distribution method 2:
- Use cvs to check out ogreaddons.[/*:m]
- Notice relative include directories and link directories do not match the same ones used by other ogreaddon projects. (See below)[/*:m]
- Also notice if yo uuse CVS you'll need to move files after doing a CVS checkout. See The please-read-me-file.txt in paginglandscape\Samples\MapEditor.[/*:m][/list:u]
4) OgreAddon Projects and the default include paths
There doesn't seem to be any consistency here.
Some addon projects them assume you have a directory setup like:
c:\somedir\ogrenew
c:\somedir\ogreaddons
while others assume:
c:\somedir\ogrenew
c:\somedir\ogrenew\ogreaddons
And I can't remember which, but I swear at one point I found an addon which, based on the relative paths in the vcproj files, seemed to expect the directory structure to be set up like:
c:\somedir\ogrenew
c:\somedir\ogrenew\Samples\Common\ogreaddons
Which is it? Are all of these project contributors just not talking to each other? Seems likely. Again, maybe I'm simply missing out on some information.
Thanks for any help you can give!
- Use cvs to check out ogreaddons.[/*:m]