Here is my script. call "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools \VsDevCmd.bat" set SRC_DIR=\cygwin\home\dashley\temp set SRC_DRV=c: set DOC_LOCATION=c:\cygwin\home\dashley\orxdocs cd %SRC_DIR% call makeorx.bat NODEBUG PACKAGE %DOC_LOCATION%
Here is the output of the script (called from cygwin bash): dashley@win7_vm ~ $ cmd.exe /k "c:\users\dashley\compile32.bat" C:\cygwin\home\dashley>call "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\VsDevCmd.bat" C:\cygwin\home\dashley>set SRC_DIR=\cygwin\home\dashley\temp C:\cygwin\home\dashley>set SRC_DRV=c: C:\cygwin\home\dashley>set DOC_LOCATION=c:\cygwin\home\dashley\orxdocs C:\cygwin\home\dashley>cd \cygwin\home\dashley\temp C:\cygwin\home\dashley\temp>call makeorx.bat NODEBUG PACKAGE c:\cygwin \home\dashley\orxdocs Syntax: makeorx BUILD_TYPE [PACKAGE] [DOC_LOCATION] Where BUILD_TYPE is required and exactly one of DEBUG NODEBUG BOTH Where PACKAGE is optional. If present and exactly PACKAGE the Windows ooRexx install package will be built. If creating the install package, the ooRexx PDF documentation must be located in the doc subdirectory of the root build directory. If it is not, an attempt will be made to copy it from the directory specified by the third optional argument: DOC_LOCATION. Note that alternatively, DOC_LOCATION can be specified as an environment variable. I.e., set DOC_LOCATION=C:\myDocs makeorx NODEBUG PACKAGE and makeorx NODEBUG PACKAGE C:\myDocs are equivalent commands. By default all output is redirected to a log file. To turn this off, set the environment variable NO_BUILD_LOG to any value. I.e., set NO_BUILD_LOG=1 C:\cygwin\home\dashley\tempexit > There is some line wrap in the above output so do not worry about that. I have also tried with and without the "call" in the batch file with the same results. I have also verified that the Visual C++ env variables are set prior to calling the makeorx.bat file. David Ashley On Wed, 2013-08-28 at 09:47 -0700, Mark Miesfeld wrote: > Hi David, > > > As I remember, this is the same problem you had several years ago when > you first tried to set up the Windows build. > > > Have you tried running makeorx.bat manually from the command line? Or > is this from a script? > > > Can you post the exact message you are getting? > > > -- > 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
