Rony,
The problem with the PATH is because the new SDK's use delayed environment
variable expansion. This is disabled by default in older operating systems
like XP, and as you've seen, it results in the path being wiped out. Not
sure why the Microsoft developers do that. It could be that they too want
to move forward, not live in the past. <grin>
I've found that the simplest thing to do is to enable it in the registry.
You can get this info by doing: cmd /? at the command line.
Delayed environment variable expansion is NOT enabled by default. You
can enable or disable delayed environment variable expansion for a
particular invocation of CMD.EXE with the /V:ON or /V:OFF switch. You
can enable or disable completion for all invocations of CMD.EXE on a
machine and/or user logon session by setting either or both of the
following REG_DWORD values in the registry using REGEDT32.EXE:
HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\DelayedExpansion
and/or
HKEY_CURRENT_USER\Software\Microsoft\Command Processor\DelayedExpansion
to either 0x1 or 0x0. The user specific setting takes precedence over
the machine setting. The command line switches take precedence over the
registry settings.
If delayed environment variable expansion is enabled, then the exclamation
character can be used to substitute the value of an environment variable
at execution time.
Have fun.
--
Mark Miesfeld
_____
From: Rony G. Flatscher [mailto:rony.flatsc...@wu-wien.ac.at]
Sent: Saturday, November 07, 2009 1:23 PM
To: Open Object Rexx Developer Mailing List
Subject: Re: [Oorexx-devel] Cannot compile ooRexx for Windows using latest
rev. 5307
Mark Miesfeld wrote:
On Sat, Nov 7, 2009 at 8:16 AM, Mark Miesfeld <mailto:miesf...@gmail.com>
<miesf...@gmail.com> wrote:
On Sat, Nov 7, 2009 at 8:03 AM, Rony G. Flatscher
<mailto:rony.flatsc...@wu-wien.ac.at> <rony.flatsc...@wu-wien.ac.at> wrote:
Just went to <http://msdn.microsoft.com/en-us/windows/bb980924.aspx>
<http://msdn.microsoft.com/en-us/windows/bb980924.aspx> which
offers a SDK supporitng Windows 7 (dated August 2009) and one supporting
Windows Server 2008 (dated February 2008). Is using the Windows 7 SDK o.k.?
That should be fine, I think.
I just committed a change so that trunk will compile with older
versions of the SDK.
A problem with moving to the Windows 7 SDK could be this: I haven't
compiled with that late of a SDK, yet, so I can't guarantee that you
won't run into some other compile error. With each new SDK, Microsoft
will / may drop some support for older features. There is always the
chance that the newest SDK may drop something being used in the
current code base. There is still stuff in the Windows code that was
for Windows 3.1.
Thank you very much for your efforts!
In the meantime I have downloaded the Win7 SDK version and installed it.
Using it to set the environment seems to wipe out the current PATH value;
didn't have time to look into this further. Correcting the PATH by hand and
then compiling ooRexx did work, so there should be no incompatibilities be
introduced by it.
In the meantime I will drop back to the Server 2003 SDK script thanks to
your efforts, which are highly appreciated!
---rony
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
