David,
By default all output is redirected to a log file. In your example the log
file will be: Win32Rel.log in the Win32Rel subdirectory.
The contents of that log file should give us a hint as to what is wrong.
At the very least, a little ways down from the top should be something
like:
Argument check ---
Arg 1 build type:
Arg 2 package:
Arg 3 doc location:
Environment check ---
SRC_DRV: C:
SRC_DIR: \work.ooRexx\wc\main
CPU:
MSVCVER:
NO_BUILD_LOG:
DOC_LOCATION:
Output is appended to the file. You might want to be sure it is deleted
first so that you get just the output from a single trial.
Also, directly from a command prompt run this command:
"C:\Program Files (x86)\Microsoft Visual Studio
11.0\Common7\Tools\VsDevCmd.bat"
and see what the output is. After it runs, check the environment:
C:\work.ooRexx\wc\main>set
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\Administrator\AppData\Roaming
APPVER=6.1
...
Look at the path to be sure it looks okay. There can be a problem with
VsDevCmd.bat. If there is, the path variable will be screwed up after you
run it.
--
Mark Miesfeld
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
