Neo Posted May 29, 2012 Share Posted May 29, 2012 Hello happy campers, I might be missing something but compared to every other major 3d packages, Houdini seems to fall behind supporting VC users. I'm simply wondering if there is any hope of successfully compiling Houdini v11/v12 x64 plugins with Visual Studio 2010? Thx Quote Link to comment Share on other sites More sharing options...
eetu Posted May 29, 2012 Share Posted May 29, 2012 I might be missing something but compared to every other major 3d packages, Houdini seems to fall behind supporting VC users. I was just last week battling problems arising from Nuke stuff needing to be compiled with VS2005, while Houdini needs the almost-spanking-new 2008 Quote Link to comment Share on other sites More sharing options...
Neo Posted May 29, 2012 Author Share Posted May 29, 2012 Thank you for your input eery, I swear never to look back on VS 2008... now you are telling me we have no other choice than using a dinosaur, VS 2005 that is? Quote Link to comment Share on other sites More sharing options...
symek Posted May 29, 2012 Share Posted May 29, 2012 I was just last week battling problems arising from Nuke stuff needing to be compiled with VS2005, while Houdini needs the almost-spanking-new 2008 well, Maya2013 takes VC2010, but and at the same time, requires ancient (7 years old) gcc4.1.2 (here comes 4.7!) Quote Link to comment Share on other sites More sharing options...
Neo Posted May 29, 2012 Author Share Posted May 29, 2012 (edited) Hi Symek, I'm very new to Houdini so I'm a little confused, maybe you can help us clear some facts that could help other folks as well. 1- Houdini v12 is in fact 2012 right? 2- Regarding to the Side Effects website, v13/2013 has not been released yet, is that correct? 3- Can houdini-12.0.581-win64-vc9 plugins be compiled with VS 2008? (I'm asking this because VS 2010 can use the vc90 compiler) 4- Is there any Wizard that could create VS 2008/2010 Projects? (make files make me dizzy) Thank you, your feedback is very appreciated. Edited May 29, 2012 by Neo Quote Link to comment Share on other sites More sharing options...
Guest mantragora Posted May 29, 2012 Share Posted May 29, 2012 1. Autodesk numbering doesn't work here. For example Houdini 8 was available in 2006. 2. Look up. 3. Yes, they can. Check this topic. I attached there example VS Solution that you can tweek. 4. Yeah. He is called "Mantragora". Check project that he created in answer above. Quote Link to comment Share on other sites More sharing options...
Neo Posted May 29, 2012 Author Share Posted May 29, 2012 Oh interesting, I tried to compile your VS 2008 solution and the lines: "$(H12_PATH)/custom/houdini/dsolib/*.a" "$(H12_PATH)/custom/houdini/dsolib/*.lib" ...cough some errors so I removed them and dragged all the .lib and .a to the project (from dsolib). I get 413 unresolved external symbols and I'm clueless at this point. Any hint would be appreciated. Is the Mantragora Wizard hosted somewhere so we can play with it? Quote Link to comment Share on other sites More sharing options...
Guest mantragora Posted May 29, 2012 Share Posted May 29, 2012 (edited) What errors ? Can you copy them here ? Have you added "H12_PATH" variable in Windows ? How it looks ? Have you set it exactly like in the post where this solution was added ? If so, have you noticed that between %H12_VERSION% variable and Houdini name there is a space ? Mantragora is my name and I am THE WIZARD ! EDIT: BTW. Do you have "MSVCDir" environment variable set ? It needs to point to "VC" directory of your VS2008 installation: MSVCDir=C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC Edited May 30, 2012 by mantragora Quote Link to comment Share on other sites More sharing options...
Neo Posted May 30, 2012 Author Share Posted May 30, 2012 (edited) Alright, I added the variables and Abracadabra! It works. Thank you very much for your support everyone! I managed to compile the SOP_Star plugin inside VS 2010 using vc90 tool set. Now, I'm hitting a wall when using the vc100 as the compiler looks for boost_thread-vc100-mt-1_46_1.lib, which doesn't exist. My question is, if I go to the trouble of compiling the boost libs, is there any chance the compiled plugin will work properly? Compiled under VS 2010 using the vc100 tool set that is. Edited May 30, 2012 by Neo Quote Link to comment Share on other sites More sharing options...
edward Posted May 31, 2012 Share Posted May 31, 2012 My question is, if I go to the trouble of compiling the boost libs, is there any chance the compiled plugin will work properly? Compiled under VS 2010 using the vc100 tool set that is. NO Quote Link to comment Share on other sites More sharing options...
Neo Posted May 31, 2012 Author Share Posted May 31, 2012 (edited) I guess you are right, we've celebrated the fact that the compilation and the creation of the plugin did work with either VS 2010 vc90 and/or vc100. But when attaching houdini.exe process to VS debug, the output console cough this: 'houdini.exe': Loaded 'C:\dev\workgroups\houdini\12_0\myPlugin.dll', Symbols loaded. 'houdini.exe': Unloaded 'C:\dev\workgroups\houdini\12_0\myPlugin.dll' I'm running out of ideas at this point... I was under the impression that compiling with VS 2010 (vc90) would be the equivalent of using VS 2008... I guess we're in need of Jedi Master Wisdom! PS: Regarding Boost libs, for compiling with vc100, this seems to be the way to go: http://boost.teeks99.com/ Edited May 31, 2012 by Neo Quote Link to comment Share on other sites More sharing options...
edward Posted June 1, 2012 Share Posted June 1, 2012 From what I gather from various blogs read awhile back, VS 2010 is supposed to be able to support compiling with older "toolsets". ie. You can use VS2010 to build using the VS2008 compiler. This is *only* if you have both versions installed on your system. Secondly, I don't understand your boost question. For that case, you're clearly using the VS2010 compiler, which will NOT WORK. There's no reason to build boost at all because if you built your plugin correctly using the VS2008 compiler, then it would have automatically linked in the boost dll that comes with Houdini 12. Quote Link to comment Share on other sites More sharing options...
Neo Posted June 1, 2012 Author Share Posted June 1, 2012 (edited) Exactly, We managed to compile Houdini plugins with 2010 and the vc90 toolset. The plugin does compile with the vc100 toolset and the v100 boost libs, but the plugin wont load in Houdini v12. So... case closed. Thank you all for your inputs. Edited June 1, 2012 by Neo Quote Link to comment Share on other sites More sharing options...
Neo Posted June 1, 2012 Author Share Posted June 1, 2012 Yikes, the debug version doesn't load into Houdini v12... I tried to set up the same project properties as the release and even then... the plugin wont work. Anyone have an idea on what I could have missed? Quote Link to comment Share on other sites More sharing options...
edward Posted June 4, 2012 Share Posted June 4, 2012 You must compile with the -MD compiler option (ie. link against the release CRT), because that is what Houdini is linked against. You can still disable optimizations and enable C7 debug symbols for your debug builds (ie. -Od -Z7). Quote Link to comment Share on other sites More sharing options...
edward Posted June 4, 2012 Share Posted June 4, 2012 PS. http://www.sidefx.com/docs/hdk12.0/hdk_intro_debugging.html Quote Link to comment Share on other sites More sharing options...
Neo Posted June 4, 2012 Author Share Posted June 4, 2012 (edited) Got it thank you, for some reason, when using the processor definition _DEBUG, the plugin does not load. Otherwise the debug works fine with the setting suggested. Edited June 4, 2012 by Neo Quote Link to comment Share on other sites More sharing options...
edward Posted June 5, 2012 Share Posted June 5, 2012 That's probably because that causes various system headers to think that you're using the debug CRT (-MDd) when you're not. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.