[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cdt-dev] Spawner treats environment differently on Windows andLinux
- From: Chris Recoskie <recoskie@xxxxxxxxxx>
- Date: Wed, 7 Jun 2006 14:28:37 -0400
- Delivered-to: email@example.com
+1 from me on the method of the fix, and +1 from me on doing this for 3.1
If we don't do it, some features are going to be busted, and I don't think
anyone is really relying on the previous behaviour.
Team Lead, IBM CDT Team
sky@xxxxxxxxx> "CDT General developers list."
Sent by: <cdt-dev@xxxxxxxxxxx>
RE: [cdt-dev] Spawner treats
07/06/2006 12:47 environment differently on Windows
Please respond to
I've implemented a quick fix for the linux Spawner.
The script is attached to the corresponding bugzilla (
I've tested it on Linux x86 and it works fine, though I've made only a
little testing so far.
In case we all agree to make the Spawner treat the environment on Linux as
it does it in Windows, we should decide whether or not to include the fix
in the 3.1
The major impact of this bug currently is the MBS Internal Builder and all
its clients: Internal Build functionality, Building a single resource
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Sennikovsky, Mikhail
Sent: Wednesday, June 07, 2006 3:07 PM
To: CDT General developers list.
Subject: [cdt-dev] Spawner treats environment differently on Windows
While working on the fix for the MBS Internal Builder-related issue (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=145099), I?ve noticed that
the Spawner treats environment differently on Windows and Linux (see the
Although it might not seem to be a really critical bug especially when we
are close to our release, I?d like to here your opinion on what should be
the right way of handling environment: the way used by the Windows Spaner
or the way used by the Linux one, since the decision might affect other
components using Spawner, e.g. the SIProvider mechanism, MBS Internal
Builder i.e. the way the Path environment variable is treated by those
See the bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=145737 for more
detail and please comment to that bug if you have any ideas regarding this.
cdt-dev mailing list