Debug name

Would it be possible if you change the project information to build the debug linker library and dll with _d appended to the name so it follows Ogre naming conventions, and (more importantly) makes it so I don't have to rename them manually upon a rebuild just so I can place them in the same global path?

EDIT: Added poll...

it follows Ogre naming conventions
ogre plugin naming convention is without _d.

so I don't have to rename them manually upon a rebuild just so I can place them in the same global path
Why not use added lib path in project properties instead of global path ?
In this case you can specify per debug/release path using $(ConfigurationName) dev env variable.

Unless you have up to 20 apps using PLSM2 and really need a global path, it seems a better option, no ?

True overall, but I do have more then twenty projects setup using such things, many are using plsm2, the only reason many of the rest are not is because I've yet to get around to adding in such things manually as it means having to open another one and copy it around. Just far simpler overall if each build type has its own naming convention.

twenty projects setup using such things
Looking forward those to appear in http://www.ogre3d.org/phpBB2addons/viewtopic.php?t=8

Please start a Poll on this forum, and I'll follow results.

Heh, will add when I have something worthy to show, right now most of them do less then your demo app on the user side (although quite a bit larger on the code side for future additions). There is one that I am helping someone make (see the CEGUI thread I made) that is easily the most usable of any apps I have (it was using the normal terrainscenemanager, but I converted to use PLSM2); when I get that CEGUI interface working when I get time at home (hopefully tonight, mabye tomarrow), I'll take some pictures and make a description to post up.

makes it so I don't have to rename them manually upon a rebuild just so I can place them in the same global path?
I voted 'no' because a) I belive that the clearest way of differentiating your build is to have your libs in debug/release folders, and your bins in ditto. b) 'The same global path' is definately prone to all sorts of errors, especially when maintaining different versions of the same thing, and/or upgrading/rebuilding.

Just my 2 cents.

I say yes because it's the most flexible.

If you want to continue keeping things in two separate folders, it works for you.

If you want to put things all in the same folder, it works for you.

I agree. If everyone does it. You might need to recompile third-party stuff to get what you want, or use two folders anyway.
But - as you said - this brings more flexibility, and the cost is minimal.
I prefer two folders because it prevents me from doing goof-ups (no pun intended).

I still do use two folders, but I have each folder as a global lookup folder, same thing with Ogre itself.

I'll wait monday for final anwsers and make the changes then.
So hurry up, voters.