Joerg Schilling wrote:
> Alan Coopersmith <alan.coopersmith at sun.com> wrote:
>
>> Joerg Schilling wrote:
>>> Brian Cameron <Brian.Cameron at Sun.COM> wrote:
>>>
>>>>> So, why use GDM instead of KDM then? Other than "because it's there" ?
>>>> If someone wants to make KDM support Solaris, I think that would
>>>> be great. As I explained, I think a11y support was the main reason
>>>> we picked GDM over KDM initially.
>> >From my understanding, this would either need a binary standard for C++
>>> or a way to define a different LD_RUN_PATH for gcc compiled binaries.
>> Why? KDM is an application, not a library.
>
> I thought an application links to libraries.
And? Even if it uses C++ libraries, the libraries and applications just
have to be compiled with compatible compilers (for Sun Studio, any version
5.0 or later, for g++, versions using the same ABI as each other).
You may be remembering the discussions about why Sun chose GNOME/GTK over
KDE/Qt - and for the primary development GUI toolkit, that was an issue, but
for additional software that's provided as an option, or software that's being
used like kdm, but not offered as a developement kit to build on, it shouldn't
be an obstacle. (It was also much more of an issue when the GNOME vs. KDE
decision was made 8 years ago at Sun, since the choice was between $3000
Sun C++ and $0 g++ - but now that Sun C++ is also free, the price is no
longer a barrier to usage/adoption.)
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
