Mastercam X7 SDK issue with writing stl files

[ashjo16]

Hello i am a grad student from Iowa State Uni

 

I am in the process of migrating our add-on software package from X6 to X7(using X7 SDK, VS2012, C++)

 

However when I openup a CAD file through the add-on software ( IGES,STEP),

 

The code crashes at functions that initiate creating STL files.

 

The function name (from file Stl_CH.h in SDK) are :

 

void wr_stl(real err_tol, FILE *f, LPCTSTR fname, long ent_idn, MC_BOOL ascii_data, MC_BOOL silent, MC_BOOL use_wcs, MC_BOOL okIfNotVisible, MC_BOOL okIfBlanked=FALSE);

 

void wr_stl(real err_tol, FILE *f, LPCTSTR fname, long ent_idn, MC_BOOL ascii_data, MC_BOOL silent);

 

When I use either of these functions the mastercam crashes.

 

Here is the code snippet I am using below:

 

FILE * stl_file;

fopen_s(&stl_file,file.GetBuffer(), "wt");

wr_stl(0.001, stl_file, "", -1, false, true,false,false,false);// crashes at this point.!

fclose (stl_file);

 

It always works fine in X6 but crashes in X7, which is confusing.

 

Can somebody help please.?

 

ThankYou for help.

Ash

[Roger Martin from CNC Software]

>> I am in the process of migrating our add-on software package from X6 to X7(using X7 SDK, VS2012, C++)

 

When building CHooks (which are MFC "extension" style) DLLs, they must be built using the same compiler "tool set" as the version used to build the version of Mastercam being targeted.

 

For X6/X7 that would be tine tool set from Visual Studio 2010 ( which is the v100 toolset).

Visual Studio 2012 by default used the v110 toolset.

To find this setting in your C++ Project

Open the Project Properties and under Configuration Properties select the General category

On this dialog you should see the setting for -> Platform Toolset

 

^^^ This does not mean that you cannot use Visual Studio 2012 "as your IDE" ^^^

Just make sure that the Platform Toolset in your X6/X7 CHook Project is v100 and you should be good.

[ashjo16]

Thanks for the reply,

 

Let me try that, I will get back to you.

 

Thanks once again.

Ash

[ashjo16]

I switched back to VS 2010 toolset and fixed this problem,

 

Thanks

Ashish