I'm getting the below warning when I start the developer shell:
# Warning: Compiler Setup error# VS80COMNTOOLS not defined. That should have been set when the# .NET 2005 compiler was installed. You will not be able to do# any native C, C++ or C# development using the default compiler# for MicroStation.#-----------------------------------------------------------------------
I don't want to use the vs 2005 compiler how do I tell bmake to use the microstations compiler?
Jan,
Thank you. I have been able to compile and run a simple pure mdl example that displays a simple dialog box. I used mcomp and mlink to create the ma file for this.
I've inherited several pure mdl programs, complete with make files. I want to now compile and link the first of these programs using bmake to test them. Unfortunately, when I run bmake specifying the make file but got the following error:
BMAKE: Error - Attempting to build with VS 2005 but location is undefined!BMAKE: call trace line: 119, C:\PROGRA~2\Bentley\MICROS~1\MICROS~1\mdl\include\AssertToolSet.mki line: 109, C:\PROGRA~2\Bentley\MICROS~1\MICROS~1\mdl\include\ConfigurePolicy.mki line: 28, C:\PROGRA~2\Bentley\MICROS~1\MICROS~1\mdl\include\mdl.mki line: 8, c:\hastus\menus\menus.mke
The source file is a .mc file.
I thought I saw somewhere on this form that there is a flag to tell Microstations not to use the vs 2005 compiler and use the Microstations compiler? Does something like that exist?
Brenden OReilly said:I thought I saw somewhere on this form that there is a flag to tell Microstations not to use the vs 2005 compiler and use the Microstations compiler? Does something like that exist?
Maybe. But the idea is wrong.
If you bother to check the examples, you saw that there is nothing like "switch VS2005 off" used in them. These simple makefiles do not call VS2005 (or any other native code compiler).
Probably something in your mke is configured to use native code compiler.
Brenden OReilly said:when I run bmake specifying the make file but got the following error:
It does not tell too much.
To share both mke file and also verbose compilation (so e.g. how macros are resolved will be visible) would help.
Regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Answer Verified By: Brenden OReilly