--===============1234553423== Content-Type: multipart/signed; boundary="nextPart4656134.fkerWkqBL0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart4656134.fkerWkqBL0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, Monday 26 May 2008, Alexander Neundorf ra: > Dirk, Sune, Modestas, any comments or interest in this ? Thanks, it's already in use in Debian (for 4.0.80) and end results seem to = be=20 fully compatible with my previous kdelibs 97 patch. However, I have a few=20 suggestions: 1) Could you split dependency generation code to the separate macro for e.g= =2E=20 kdepimlibs and anything else what currently exports dependencies in the sam= e=20 manner to use? 2) What about enclosing whole block (which resets _LIB_DEPENDS according to= =20 LINK_INTERFACE_LIBRARIES) in if (KDE4_ENABLE_EXPERIMENTAL_LIB_EXPORT) or ot= her=20 flag so lib export method can be chosen when building each app individually? =2D-=20 Modestas Vainius --nextPart4656134.fkerWkqBL0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBIOv9dHO9JRnPq4hQRAtmDAKDppdUWeA8AkiuM3kGKQCvPXgetUQCgw7Ii ZXfmmzXXkU48QcZu18ho3Qo= =AGH6 -----END PGP SIGNATURE----- --nextPart4656134.fkerWkqBL0-- --===============1234553423== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem --===============1234553423==--