Support Board
Date/Time: Sat, 01 Feb 2025 01:59:22 +0000
Post From: C++ Configuration Instructions missing step?
| [2019-05-29 13:40:25] |
| ForgivingComputers.com - Posts: 992 |
|
The extra steps of releasing and loading DLLs take a little getting used to, but not a big deal.
Update: I found out as long as you use Analysis>>Build Custom Studies DLL>>Build>>Build With Visual C++ - Debug menu item, you don't need to do the release and load dance. You do, however, need to stop debugging in Visual Studio or you won't be able to save the file. Finally, the steps are the same with 32-bit and 64-bit versions. I would like to stay full-time in 64-bit, but I only know how to do 32-bit builds if I restart 32-bit Sierra. Does anyone know if there is a shortcut to change the bits within Visual Studio without getting involved with projects and solutions, etc. (the stuff you used to have to do)? It would be nice if the Sierra menu items that build with Visual Studio could build them both, at least for the Release code. It appears that the VisualCCompile.bat file is being created by the application, as it has file names in it. To hide the compiler warnings, I added /W0 to the Additional Compiler Parameters, but I still get other command line warnings: cl : Command line warning D9025 : overriding '/W3' with '/W0'
cl : Command line warning D9002 : ignoring unknown option '/JMC' cl : Command line warning D9002 : ignoring unknown option '/std:c++17' cl : Command line warning D9002 : ignoring unknown option '/diagnostics:classic' |