I have made 2 changes to handle the
Solaris Gnu problems:
1. For 3.0.2 and Head, I have added
an “Expert settings” area to the Tool option page (in C/C++ Build
properties) with a text field that allows the user to change the command-line
pattern for the tool. This will allow users to fix problems like the “space
after output-flag” problem without creating a new project-type.
2. For Head (3.1), I have created
separate Solaris Gnu project-types with the only difference being the
command-line pattern. I would appreciate it if someone who uses CDT on
Solaris would give this a try.
Thanks,
Leo
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Lott, Jeremiah
Sent: Tuesday, January 03, 2006
11:35 AM
To: CDT
General developers list.
Subject: RE: [cdt-dev] GNU
Tool-chain for Solaris
This is basically what I
remember too. Although I also think there were some people who were using
or extending the default toolchain definitions for their own compilers who
couldn't handle the space.(?) We added that space in, and their compilers
that were previously working suddenly started having errors, so we changed it
back. At least I kind of remember something like that. However, I
think maybe at that time this space/no space was hard-coded into the system,
rather than customizable via xml, so the decision was to return it to its
original state for compatability.(?) My memory is a little fuzzy,
though. Anyone else remember this?
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Doug Schaefer
Sent: Tuesday, January 03, 2006
11:06 AM
To: CDT
General developers list.
Subject: RE: [cdt-dev] GNU
Tool-chain for Solaris
I think it was because we
had one variant that couldn’t handle the space (macosx comes to mind). I
actually think we have more variants that need the space than can’t
handle it.
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Treggiari,
Leo
Sent: Tuesday, January 03, 2006
11:03 AM
To: CDT General developers list.
Subject: RE: [cdt-dev] GNU
Tool-chain for Solaris
I think that the “generic” GNU
compiler definition has never had a space after the –o. I
don’t know the reason.
Leo
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Tuesday, January 03, 2006
10:56 AM
To: CDT General developers list.
Subject: RE: [cdt-dev] GNU
Tool-chain for Solaris
This issue has always
bugged me. Do we know/remember why we don’t have a space after the
‘-o’?
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Treggiari,
Leo
Sent: Tuesday, January 03, 2006
10:51 AM
To: CDT General developers list.
Subject: [cdt-dev] GNU Tool-chain
for Solaris
I have heard from a few people with a problem using the
built-in GNU tool-chain on Solaris because a space is required after the
–o output flag. Currently, they have to modify the tool-chain to
get it to work. Is there anyone using Solaris who has not had to modify
the tool-chain? I will create Solaris specific project types with a space
after the output flag if no one speaks up. What I don’t want to do
is make the change and then find that a different implementation of the GNU
tool-chain on Solaris requires that a space not be present.
Thanks,
Leo
|
