OK, I put the leading '\' on and got as far as the error message below.

C:\oorexx>c:\buildorx

C:\oorexx>d:

D:\>cd "D:\My Documents\ooRexx Project\interpreter-3.x\trunk"

D:\My Documents\ooRexx Project\interpreter-3.x\trunk>set SRC_DRV=D:

D:\My Documents\ooRexx Project\interpreter-3.x\trunk>set SRC_DIR="\My
Documents\
ooRexx Project\interpreter-3.x\trunk\"

D:\My Documents\ooRexx Project\interpreter-3.x\trunk>makeorx DEBUG
'svn' is not recognized as an internal or external command,
operable program or batch file.
Executing in a svn working copy, but could not determine the svn revision
number.
Do NOT use this environment for a release build.

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..
***! Error occured !** : build halted

I shall have to find out how to move my repository.  I've tried a simple cut
& paste and it is chuntering away - we shall see if that works when it has
finished.

cheers,

Jon



2008/7/14 Rick McGuire <[EMAIL PROTECTED]>:

> Does it just terminate with nothing else at that point?  I've never
> seen it do that before.  The messages about svn and killer are benign,
> and not a problem.  I've never run the Express C++ before, but with
> visual studio, there's a batch file that needs to be run to set up the
> environment variables for the compile.
>
> However, I suspect the problem might be as simple as needing a leading
> "\" on your SRC_DIR environment variable.  I'm also a little nervous
> about the spaces in the path name.  I'm not sure anybody has ever done
> a build using a path with spaces, and it could cause some unexpected
> problems at some stage.
>
> Rick
>
> On Mon, Jul 14, 2008 at 6:52 AM, Sahananda (Jon) Wolfers
> <[EMAIL PROTECTED]> wrote:
> > Game to try it out.  Without having made any changes to coreclasses.orx
> at
> > this point.  First build said I needed to set SRC_DIR & SRC_DRV
> environment
> > variables, so I wrote this little batch file:
> >
> >> d:
> >> cd "D:\My Documents\ooRexx Project\interpreter-3.x\trunk"
> >> set SRC_DRV=D:
> >> set SRC_DIR="My Documents\ooRexx Project\interpreter-3.x\trunk\"
> >> makeorx DEBUG
> >
> > Some sort of success, this is what I see in the console:
> >>
> >> C:\oorexx>c:\buildorx
> >>
> >> C:\oorexx>d:
> >>
> >> D:\>cd "D:\My Documents\ooRexx Project\interpreter-3.x\trunk"
> >>
> >> D:\My Documents\ooRexx Project\interpreter-3.x\trunk>set SRC_DRV=D:
> >>
> >> D:\My Documents\ooRexx Project\interpreter-3.x\trunk>set SRC_DIR="My
> >> Documents\o
> >> oRexx Project\interpreter-3.x\trunk\"
> >>
> >> D:\My Documents\ooRexx Project\interpreter-3.x\trunk>makeorx DEBUG
> >> 'svn' is not recognized as an internal or external command,
> >> operable program or batch file.
> >> Executing in a svn working copy, but could not determine the svn
> revision
> >> number.
> >> Do NOT use this environment for a release build.
> >>
> >> Building Open Object REXX for Windows - Debug Version
> >> 'killer' is not recognized as an internal or external command,
> >> operable program or batch file.
> >> The system cannot find the path specified.
> >>
> >> D:\My Documents\ooRexx Project\interpreter-3.x\trunk\My Documents\ooRexx
> >> Project
> >> \interpreter-3.x\trunk>c:\buildorx
> >
> > Am I starting off in the wrong directory perhaps?
> >
> > thanks,
> >
> > Jon
> >
> >
> > 2008/7/14 Rick McGuire <[EMAIL PROTECTED]>:
> >>
> >> You don't actually need to  move the newly built files into your
> >> rexx_home to use this.  Just CD into "..\trunk\Win32dbg" after the
> >> build and you should be able to run the new rexx version directly from
> >> there without having to touch your installed one.  Do a "taskkill /F
> >> /IM rxapi.exe" to kill the existing rxapi process, then "rexx -v" to
> >> verify you have the new version.  You'll want to do another taskkill
> >> when you're done working with the new build so your default setup
> >> picks up the matching version.
> >>
> >> Rick
> >>
> >> On Mon, Jul 14, 2008 at 6:00 AM, Sahananda (Jon) Wolfers
> >> <[EMAIL PROTECTED]> wrote:
> >> > OK, I have the C++ compiler installed together with SP1.  All went
> >> > smoothly
> >> > using the Windows installers, except it made me register, but then
> >> > refers to
> >> > the GUI for entering the key, but I dont appear to have a GUI, just a
> >> > command line utility.  Anyway, I have saved the key and will use it
> >> > if/when
> >> > the software complains.
> >> >
> >> > I have tortoise SVN loaded with the repository root at D:\My
> >> > Documents\ooRexx Project\
> >> > I have rexx 3.2.0 loaded with rexx_home at c:\oorexx
> >> >
> >> > What I think I have to do next is:
> >> > a) make changes to the versioned file at  D:\My Documents\ooRexx
> >> > Project\interpreter-3.x\trunk\kernel\RexxClasses\coreclasses.orx
> >> > b) change directory to D:\My Documents\ooRexx
> >> > Project\interpreter-3.x\trunk
> >> > c) type "makeorx DEBUG"
> >> > d) if the make succeeds I will have an ooRexx build somewhere that I
> >> > will
> >> > have to move into rexx_home
> >> > That seems like enough steps for now.
> >> >
> >> >
> >> > does that sound more or less right?
> >> >
> >> > thanks,
> >> >
> >> > Jon
> >> >
> >> >
> >> > 2008/7/13 Mark Miesfeld <[EMAIL PROTECTED]>:
> >> >>
> >> >> On Sun, Jul 13, 2008 at 11:14 AM, Mark Miesfeld <[EMAIL PROTECTED]>
> >> >> wrote:
> >> >>
> >> >> > Here is link to get Visual C++ 2005:
> >> >> >
> >> >> > http://www.microsoft.com/express/2005/download/default.aspx#
> >> >> >
> >> >> > on that page you have to look closely at the different selections,
> >> >> > they kind of blend together.  Be sure you select C++ and not say
> C#.
> >> >>
> >> >> Jon,
> >> >>
> >> >> On that page, below the download buttons is some move detail on what
> >> >> you need to do.  You should also install the service pack 1.  There
> is
> >> >> an install update for Vista.  You don't need that and I would skip
> >> >> that.
> >> >>
> >> >> Then, of course, you also need to install the Platform SDK.  There is
> >> >> a link on the page to instructions for installing the SDK.  On the
> >> >> page for the SDK, it lists a bunch of steps for updating some stuff
> in
> >> >> Visual C++.  That stuff is only needed if you are going to be using
> >> >> 'Projects' from within Visual C++.  Since you will be building using
> >> >> the command line, I would not fool with stuff for now.
> >> >>
> >> >> I just saw that Dave posted a link to get the ISO image.  I would get
> >> >> the ISO image if you can burn your own CDs.  It gives you better
> >> >> control.
> >> >>
> >> >> Here's a link to the SDK ISO image.  I think it is easier to install
> >> >> Visual C++ from CD and then install the SDK from CD.
> >> >>
> >> >>
> >> >>
> >> >>
> http://www.microsoft.com/downloads/details.aspx?FamilyId=E15438AC-60BE-41BD-AA14-7F1E0F19CA0D&displaylang=en
> >> >>
> >> >> --
> >> >> 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
> >> >
> >> >
> >>
> >>
> -------------------------------------------------------------------------
> >> 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
> >
> >
> > -------------------------------------------------------------------------
> > 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
> >
> >
>
> -------------------------------------------------------------------------
> 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
>
-------------------------------------------------------------------------
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

Reply via email to