I have installed:
MicroStation CONNECT Edition10.15.0.74
MicroStation CONNECT Edition SDK10.15.00.076
What do I need to add to my bmake files to generate release builds? I tried adding the above at the top of my mke files. Bmake successfully added -DNDEBUG to the compiles but I am still able to debug the source using Visual Studio.
nameToDefine = NDEBUG %include cdefapnd.mki %warn "ndebug"
Thanks,
John M.
Hi John,
John Majerle said:Bmake successfully added -DNDEBUG to the compiles
A question is: Why do you use NDEBUG macro?
John Majerle said:What do I need to add to my bmake files to generate release builds?
Based on quick look into .mki files, it seems you should use:
bmake -dNO_DEBUG_INFO
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
John Majerle said:I am still able to debug the source using Visual Studio
Unless you explicitly deleted them from the \mdlapps folder, the debug symbol (*.pdb) files still exist.
\mdlapps
*.pdb
Regards, Jon Summers LA Solutions
Hi John Majerle,
When using a successfully constructed .mke file project, called from the developer shell these commands should provide the desired results:
FYI. Both target build configurations produce Microsoft Symbol Files (PDB files). PDB files can be generated for both Debug and Release configurations and should be retained; along with all other source and binaries for your project; when shipping applications into a user's production environment. This helps ensure any production crash can be quickly and accurately resolved from the PDB (symbol mapping) files. To learn more, see some topics I have provided under our Visual Studio Debugging section.
If you are attempting to compile MDL code w/o a mke file in your own VS make file project, then; although unsupported; you may want to use Microsoft Process Monitor (procmon) to attempt to confirm paths and dependencies taken/needed to make your project configuration work better/best.
HTH,Bob
Answer Verified By: Robert Hook
Hey Robert,
bmake +a +ddebug MyApp.mke
...worked for me. Now when I step into code from Visual Studio I no longer have an optimized build so I can now set breakpoints everywhere and look at the values of all local variables (that were previously optimized away.)
-John M.
Glad to hear that you are up and running.Thank you,Bob