Hi Mark,
thanks for this.
I was already using the SDK setEnv.cmd.
Here is the batchfile that I have been running:
d:
> cd "D:\orxSVN\interpreter-3.x\trunk"
> set SRC_DRV=D:
> set SRC_DIR=\orxSVN\interpreter-3.x\trunk\
> set NO_BUILD_LOG=1
> call "C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat" x86
> call "C:\Program Files\Microsoft Platform SDK\Setenv.cmd" /XP32 /RETAIL
> call "d:\D:\orxSVN\interpreter-3.x\trunk\touchheaders.bat"
> makeorx DEBUG
>
As you can see I have added touchHeaders to it, but NMAKE still stops with a
fatal error looking for xalan.
I have installed the CollabNet command line client (further down the path
than tortoise)
The output is much shorter than before, but I shall quote it all here in
case someone can spot something wrong.
I'm not at this point trying to build 4.0, but will bear the rxApi service
in mind when I come to it.
Thanks, Jon
C:\oorexx>c:\buildorx
C:\oorexx>d:
D:\>cd "D:\orxSVN\interpreter-3.x\trunk"
D:\orxSVN\interpreter-3.x\trunk>set SRC_DRV=D:
D:\orxSVN\interpreter-3.x\trunk>set SRC_DIR=\orxSVN\interpreter-3.x\trunk\
D:\orxSVN\interpreter-3.x\trunk>set NO_BUILD_LOG=1
D:\orxSVN\interpreter-3.x\trunk>call "C:\Program Files\Microsoft Visual
Studio 8
\VC\vcvarsall.bat" x86
Setting environment for using Microsoft Visual Studio 2005 x86 tools.
Attempting to detect a Microsoft Visual Studio installation
Targeting Windows XP 32 RETAIL
The filename, directory name, or volume label syntax is incorrect.
Building Open Object REXX for Windows - Debug Version
'killer' is not recognized as an internal or external command,
operable program or batch file.
Building Rexxapi..
Microsoft (R) Program Maintenance Utility Version 7.00.8882
Copyright (C) Microsoft Corp 1988-2000. All rights reserved.
.
All done rexxapi.dll rxapi.exe
.
Building Kernel....
Microsoft (R) Program Maintenance Utility Version 7.00.8882
Copyright (C) Microsoft Corp 1988-2000. All rights reserved.
.
Generating D:\orxSVN\interpreter-3.x\trunk\\kernel\messages\RexxErrorCodes.h
xalan -o
D:\orxSVN\interpreter-3.x\trunk\\kernel\messages\RexxErrorCodes
.h D:\orxSVN\interpreter-3.x\trunk\\kernel\messages\rexxmsg.xml
D:\orxSVN\interp
reter-3.x\trunk\\kernel\messages\RexxErrorCodes.xsl
'xalan' is not recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: 'xalan' : return code '0x1'
Stop.
***! Error occured !** : build halted
D:\orxSVN\interpreter-3.x\trunk>
2008/7/14 Mark Miesfeld <[EMAIL PROTECTED]>:
> On Mon, Jul 14, 2008 at 5:13 AM, Sahananda (Jon) Wolfers
> <[EMAIL PROTECTED]> wrote:
> > Alright, now I get:
> >
> > D:\orxSVN\interpreter-3.x\trunk>makeorx DEBUG
> > 'svn' is not recognized as an internal or external command,
> > operable program or batch file.
>
> Glad to see you move your source tree so that the path to it does not
> have spaces in it. You will run into problems if you put the source
> in a path that has spaces in it.
>
> > Executing in a svn working copy, but could not determine the svn revision
> > number.
> > Do NOT use this environment for a release build.
>
> If you install the command line version of svn, you can get rid of
> that warning.
>
> http://www.collab.net/downloads/subversion/
>
> get: CollabNet Subversion Command Line Client v1.5.0 (for Windows)
>
> But since you are just building for yourself, you can just ignore the
> warning.
>
> The platform SDK also has a set up bat file. It checks for Visual C++
> on your system and sets everything up. I believe it is better to ran
> that version than the one in Visual C++. But that is a matter of
> taste, running the Visual C++ one will work fine.
>
> Here is the SDK version, change the path to match your set up:
>
> call "C:\home\Tools\MsPlatformSDK\SetEnv.cmd" /XP32 /RETAIL
>
> There is another problem you will probably run into if you have the
> 3.2.0 rxapi installed as a service. It is not compatible with
> building the 4.0.0 version and you will most likely get a crash when
> rexx.img is built.
>
> You can do this to get around it:
>
> C:\home>net stop rxapi
>
> Temporarily rename your ooRexx directory:
>
> C:\home>ren ooRexx ooRexx-temp
>
> Then rename the directory back when you want to use the 3.2.0 version
> of ooRexx. You only need to do the rename when you actually start the
> build.
>
> --
> Mark Miesfeld
>
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
