| RE: [cdt-dev] Spawner treats environment differently on Windows andLinux |
|
Hi All, I've implemented a quick fix for the linux Spawner. The script is attached to the corresponding bugzilla (https://bugs.eclipse.org/bugs/show_bug.cgi?id=145737). See https://bugs.eclipse.org/bugs/attachment.cgi?id=43732&action=""> 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 functionality. Mikhail From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sennikovsky, Mikhail Hi All, 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 bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=145737) 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
components. 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. Thanks, Mikhail |