static linking of pwlib with openh323

[Jose Carlos Garcia Sogo]

--CUfgB8w4ZwR/yMy5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 11, 2004 at 07:27:34AM +0200, Kilian Krause wrote:
> Hi Jose,
>=20
> Am Mi, den 11.08.2004 schrieb Jose Carlos Garcia Sogo um 0:22:
> > On Tue, Aug 10, 2004 at 04:14:59PM +0200, Kilian Krause wrote:
> > > Hi,
> > >=20
> > > as the openh323 is providing a libopenh323.a, we very likely need
> > > another openh323 upload too.=20
> >=20
> >  Why this? I know that these libraries are a exception to the rule,  but
> >  libraries don't usually have to be recompiled for .a when a library on
> >  which they depend change... but who knows... :-)
> >=20
> >  Have you tried?
>=20
> well, if the statical linking does work (which i hope it does), then
> pwlib code is included in libopenh323.a (not .so!) at compile time. Thus
> the wrong code of 1.6.6.4-1 is frozen in 1.13.5.4-1 *.a

  Nope, basically that shouldn't happen, unless that's what upstream
  want. I mean, .a files doesn't include code from other libraries they
  depend on. For example, libgnomeui. Its .a file doesn't have all the
  code from all libraries showed as a dependency. The .a file is only
  used when you compile a binary and you want it to be statically linked
  with all its dependencies. Then, the .a file is added to the binary.

--=20
Jose Carlos Garcia Sogo
   jsogo@debian.org

--CUfgB8w4ZwR/yMy5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBGgMTS+BYJZB4jhERAlweAJ9whcbfeQhoRcfjxry7M3Q4FcFb0QCfa+gz
Ykftltx+CfUKvv58I+2z/pM=
=Aklz
-----END PGP SIGNATURE-----

--CUfgB8w4ZwR/yMy5--