Compiling For Maya 8.5

[jeffm3]

Has the compiler requirements changed for Maya 8.5?

Because I get this error when trying to compile an older plugin:
......\include\maya/MTypes.h(256) : error C2632: 'long' followed by 'long' is illegal

CODE
MTypes.h:
#if defined(_WIN32)
    typedef unsigned long long MUint64;
#elif defined(sgi) || defined(linux)
#if defined(Bits64_)
    typedef unsigned long MUint64;
#else
    typedef unsigned long long MUint64;
#endif

I've been using Microsoft Visual C++ 6.0. It compiled ok with Maya 8.0.

Is it possible to get it working with MSVC++ 6.0 still?

[rob-bateman]

get a new compiler. VC++ 2005 will do the trick nicely (the express edition is a free download, then you only need to install the windows platform SDK).

[jeffm3]

Yeah, it may be time for an update.

[mmeijer]

If VS 2005 still gives you problems, consider building a new
solution using the plugin wizard.

http://www.highend3d.com/boards/index.php?showtopic=234873

[rob-bateman]

QUOTE(mmeijer @ 03/09/07, 04:37 AM) [snapback]261916[/snapback]
If VS 2005 still gives you problems, consider building a new
solution using the plugin wizard.

I piece of advice i strongly disagree with...

[jeffm3]

Well, I may not have to upgrade just yet!

It looks like MSVC++ 6.0 does not support a 64-bit data type called 'long long',
so all occurences of 'long long' should be replaced with LONGLONG or __int64.

Thanks.

[rob-bateman]

I'd still say upgrade though. VC6 really is terrible when you compare it to VC2005. Just upgrade and you'll be happy you did...

[heron3d]

I get similar errors when I try to compile with Visual Studio 2005 version 8. Is there a difference between MSVC6 and what I am using? The plugin wizard fails when I try to create a new project from scratch. Or can I use Microsoft Visual Studio.NET 2003 to program for Maya 8.5?

Nikos P

[jeffm3]

I don't use the plugin wizard, but I do know that the 'long long' data type should
be recognized by both Visual Studio 2003 and 2005, so I don't see how you can get
the same error message as me.
I would think this error is specific to older compilers like MSVC++ 6.0.

BTW, I also had a lot of "std is not a namespace" compilation errors, but after
I added:
#include

to all my code, those were fixed too. I think it will also work if REQUIRE_IOSTREAM
is added to the list of pre-processor definitions too.

Although, now I see this recommendation is best:
#include

[rob-bateman]

QUOTE(heron3d @ 03/10/07, 05:09 PM) [snapback]261975[/snapback]
The plugin wizard fails when I try to create a new project from scratch. Or can I use Microsoft Visual Studio.NET 2003 to program for Maya 8.5?

http://www.highend3d.com/boards/index.php?...iling&st=15

see the post's from me and Hajime near the bottom. You don't need to set the include dir's for the platform SDK if you are using the full version of 2005 (only need to do it for the express edition).

[lelapinblanc]

QUOTE(Rob Bateman @ 03/09/07, 09:01 AM) [snapback]261921[/snapback]
I piece of advice i strongly disagree with...

I think i may agree with rob, but i don't know why

I run VS2005 team edition, and i can build the applications sucessfully that are in devkit/applications...

BUT.....

When i follow the directions for installing the pluginwizard to 2005 here is what happens:

the first time i select mayapluginwizard when creating a project it gives me some diaglog about names and pages......

so i named it mymayaplugin......

the next time i try to create a maya plugin with the wizard it says project creation fails when i click mayapluginwizard, and i notice that now i have a template called mymayaplugin in the same template list with mayapluginwizard.

i delete mymayaplugin from my projects and backup directories, but the mymayaplugin remains in the template list, and attempting to create a project with mayapluginwizard continues to fail.

I am new to this, and would be eternally grateful for a little direction......

I'm running maya 8.5 and VS2005 team edition

thank you

[rob-bateman]

QUOTE(lelapinblan @ 03/18/07, 08:33 AM) [snapback]262473[/snapback]
I think i may agree with rob, but i don't know why

because it sucks? Generally i think it's better to manually set up the projects, since you get a lot more control over how things are setup and initialised. The project types in the wizard have always been a bit too simplistic for my actual needs, and tbh I find it quicker to do it manually.