Netbeans and Maya API

[Robert Bateman]

You can use any IDE you want, but you are restricted to using Visual C++ as the compiler due to CRT dependencies in the Maya API. It just means you'll have to set netbeans up to call a makefile for VC++.... probably not worth it imho - but others have done it with MingW et al.

[mindsample]

its not the kind of thing where I need additional steps or confusion, so no, it sounds like it is not worth it.
Thanks

[mindsample]

I am using Maya 2009 64bit, are there any compatibility issues with certain versions of Visual Studio? I read that i.e. 2008 was compiled with VC2005, and hence any other version is to be avoided for developing plug-ins?

[Robert Bateman]

I am using Maya 2009 64bit, are there any compatibility issues with certain versions of Visual Studio? I read that i.e. 2008 was compiled with VC2005, and hence any other version is to be avoided for developing plug-ins?

I'm only using VC2005 at the moment, and certainly don't have any problems. AFAIK, VC2008 should be ok unless you start trying to stream MMatrix et al into std::iostream related classes (since that brings CRT dependencies into your code). The Maya API does a pretty good job of not being CRT dependent, so it should be OK (at least it was during the previous transitions between VC6->2001->2003->2005). I don't see any reason why the transition to 2008 would be any different.

[mindsample]

I'm only using VC2005 at the moment, and certainly don't have any problems. AFAIK, VC2008 should be ok unless you start trying to stream MMatrix et al into std::iostream related classes (since that brings CRT dependencies into your code). The Maya API does a pretty good job of not being CRT dependent, so it should be OK (at least it was during the previous transitions between VC6->2001->2003->2005). I don't see any reason why the transition to 2008 would be any different.

I couldnt get it to work with 64bit and VC8, I am now using 2005 and it works fine with maya 2008 (32) ... at the end of the day I dont care too much I just want to write code. The compile issue for 64bit I will have to deal with later.

One thing that still doesnt work is the IDE aided popups (what do you call them?), i.e. I dont get any interactive help when I type commands into my code-window, I dont know why, everything compiles fine and seems to be linked nicely, any suggestions on how to get this to be switched on ?

[Robert Bateman]

VC++ 2005 is VC 8.0 ????

For 64 bit, make sure you have the 64 bit tools and compiler installed (it isn't by default - just check by re-running the VC installer). Having installed it, open your 32bit sln, goto Build->configuration manager, in the 'Active solution platform' select 'new' from the drop down list. Put 'x64' as the new platform, and copy settings from Win32.

Finally, modify the lib path to the x64 folder. Do a clean build, and that should be it. For sanities sake, spend some time trawling through the project settings and change any Debug/ to $(IntDir)/

This is only needed because VC fails to modify all of the output files, so they can end up being shared between the 32bit and 64 bit versions (which you do not want to happen!), which can lead to unresolved externals and other linker nastiness.

One thing that still doesnt work is the IDE aided popups (what do you call them?), i.e. I dont get any interactive help when I type commands into my code-window, I dont know why, everything compiles fine and seems to be linked nicely, any suggestions on how to get this to be switched on ?

Intellisense? Visual Assist (http://wholetomato.com/) ftw.

[mindsample]

sorry, i get confused, i hate those naming conventions - vc8 - 2005 ? vc 2008 = vc9 ?

maya 2008 = maya9 ?
maya 2009 = maya10 ?

Anyways, I never get the x64 option from any drop down, I have to re-install and double check yet again whats going on ... madness!

[mindsample]

Intellisense? Visual Assist (http://wholetomato.com/) ftw.[/QUOTE]


I mean the internal one, its strange, I had it working yesterday (it just did), now it doesnt. I know I must sound like an idiot but installing this is more complicated than writing the code!!

[Carina]

I had it working yesterday (it just did), now it doesnt.
That is the beauty of Intellisense (and a good reason to use VisualAssist instead)

[mindsample]

I hope it is worth the money. It certainly looks good on their website.

Thanks guys.

[Carina]

If you're seriously interested in development, it's definitely worth the money. You can always give it a go with the free trial and decide for yourself!

[Robert Bateman]

I hope it is worth the money.

It's the best use of $99 you'll ever find. Use up the free trial completely before buying though, and keep an eye on when your maintenance runs out (so you can grab the latest version at that point). I've only had to do 2 maintenance upgrades since I bought it circa 2001 (you won't need to do one until you switch to VC++ 2010 or whatever the 2008 replacement is).

The default VC intellisense was never that good with C++ (It's really good for C# and VB though). Visual Assist craps on it from a very big height!

A couple of tips though. Add the maya include dirs to the stable includes in the VA options. The insert closing }) on {( option is really annoying imo. Some useful shortcuts:

Alt+G - goto definition
Shift+Alt+O - open file in workspace
Shift+Alt+S - find symbol
Alt+O - Open corresponding h or cpp

Also, select some code in a method, hold your mouse over it for a second, then do refactor->Extract Method.
Hold your mouse over a function name/variable/class name, then do refactor->Rename.

It's also worth editing the Autotext file (found in the options->Advanced->Suggestions). I've changed the defaults so that they conform to my coding style, and added little things like //h slaps out my standard header format, //c for a cpp file, /// for function comment etc.

Once you've used it for a bit, you'll be amazed you ever programmed without it....

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.