Very Computer

how does one obtain a static libXm.a (motif library, for static linking)

on a Solaris 2.5.1 system?  /usr/dt/lib only has the dynamic version
(.so files).

thanks in advance,

Rei Shinozuka

Why not just install/mount /usr/dt on the target machine?

My guess is the only way to get a static version is to get
the source and compile it. We use to have the source, but that
was before CDE.
--

[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]

Quote:>how does one obtain a static libXm.a (motif library, for static linking)
>on a Solaris 2.5.1 system?  /usr/dt/lib only has the dynamic version
>(.so files).

(Too many time is/was beign spend on keeping libraries working together
when parts were dynamically linked and parts statically linked; i.e.,
you had old libXm.a and new libX*.so)

It's not supported.  Solaris 64 bit libraries will not ship in static
form.

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

I found a case where dynamic linking Motif failed where static would have
worked.  Sun changed the internal layout of the Motif text widget in 2.6
and a program which used the private data fields broke.

--

--dave c-b
[caveat: I have a bias: I'm contracting for a group that works
        on software stability on Solaris, and using private
        functions and data members is **a real bad thing**]
--
David Collier-Brown,  | Always do right. This will gratify some people
185 Ellerslie Ave.,   | and astonish the rest.        -- Mark Twain

M2N 1Y3. 416-223-8968 | http://java.science.yorku.ca/~davecb

[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]

Quote:>I found a case where dynamic linking Motif failed where static would have
>worked.  Sun changed the internal layout of the Motif text widget in 2.6
>and a program which used the private data fields broke.

The thing you often see is that people will replace widgets in libraries,
copying the freely available source code and modifying it to suit their
needs. This often leeds to error messages about widget version numbers
because they really didn't create a whole new widget, but simply depended
on code still in the library.

Don't touch private data.  It's unfortunate that Solaris 2.x didn't
start hiding all internal lib functions until version 2.6

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.