Right, I can see why it was failing before but working now. I need to run SetEnv.cmd before each time I try to build a module. If I restart the machine, it no longer works until I ran the command again. Any thoughts? | [reply] |
SetEnv sets the environment variables for the current command line window. If you close that window and open another, you need to re-run SetEnv in that session to be able to use the compiler.
If you prefer the compiler enabled in all commnd line sessions across reboots, you can run it in one session, and then copy the path, include and lib setting from there into your system settings via:
Start->settings->controlPanel->AdvancedSystemSettings->EnvironmentVari
+ables
And set them either just for the current user, or system wide.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] [d/l] |