Boost is a terrible thing.. It demands to be in the global include/lib directories.
Nothing a wizard can do about that..
/* links updated */

... really, because I use Visual Studio 2008 and have the Boost include and library paths set-up in my project properties (not the global properties) and it works fine.jacmoe wrote:It turned out that I updated the wizards all for nothing, so I am just going to revert.
Boost is a terrible thing.. It demands to be in the global include/lib directories.
Nothing a wizard can do about that..
/* links updated */

Yeah, a big factor behind me compiling everything myself. Whilst I do like some of the features Boost offers, the cost in compile time can become very frustrating in the iterative development style I tend to work in. I love the simplicity in code, just not the inordinate amount of time the compiler needs to perform it's template magic... nor the size explosion seemingly simple templates can sometimes add to an executable.jacmoe wrote:You are excused - but the SDK uses Boost.
I'm quite certain I don't have it set up globally since I always set-up include and library paths on a per-project basis since I use multiple machines to develop on so I need the settings to be part of the project, and not part of the machine. This is how I have always included Boost and it has always worked, I'm honestly not sure how it is causing you problems. In fact, it can't possibly set-up globally since if I remove it from my project properties, I get a load of "cannot find file" errors when building.jacmoe wrote:Uh-huh - how?
You're sure that you haven't got some sneaky global include paths set up?
I am not considering myself a master of Visual Studio, but I'm no stranger to it either.
If you tell me what I did wrong, I'd be happy to learn a new trick.
Here is the contents of my "Project Properties -> Linker -> Additional Library Directories" (for a Debug build, release is the same except for $(OGRE_HOME)\lib\Release):$(OGRE_HOME)\include
$(OGRE_HOME)\include\OGRE
$(OGRE_HOME)\include\OIS
$(OGRE_HOME)\boost_1_42
It is also worth noting that you must only include a single version of Boost (and for that I choose the one that comes with OGRE) when building your application. I had a problem with this when I tested the Insimnax Framework against 1.7 since I include a cut-down version of Boost with the ICL so I can use smart pointers, the version I include is 1.40 and the version OGRE uses is 1.42; this lead to an issue where my application was trying to link against the 1.40 libraries (which I didn't have) instead of the 1.42 libraries (that OGRE provides). The solution was to only include the version of Boost that comes with OGRE, and not any other versions that I had on my machine.$(OGRE_HOME)\lib
$(OGRE_HOME)\lib\Debug
$(OGRE_HOME)\boost_1_42\lib

Yes, I'm using the pre-compiled SDK.jacmoe wrote:Did you try compiling against the precompiled SDK?



Code: Select all
OgreAppWizard90.ico
OgreAppWizard90.vsdir
OgreAppWizard90.vsz
I got OGRE_HOME/boost_1_42 with the VS2008 SDK, though you keep mentioning boost_1_41.jacmoe wrote:I will update the wizards to using OGRE_HOME/boost_1_41 for includes and OGRE_HOME/boost_1_41/lib for libs...





make no sense to me, I don't understand where this text is supposed to go.try adding this to the js extension under run. (In 'Folder Options' in File Explorer.)
C:\WINDOWS\System32\WScript.exe "%1" %*










See the ABSOLUTE_PATH parameter?VSWIZARD 7.0
Wizard=VsWizard.VsWizardEngine.9.0
Param="WIZARD_NAME = OgreAppWizard90"
Param="ABSOLUTE_PATH = C:\Program Files\Ogre VC9 Express AppWizard"
Param="FALLBACK_LCID = 1033"
