From kde-core-devel Fri Apr 24 20:28:06 2009 From: "Aaron J. Seigo" Date: Fri, 24 Apr 2009 20:28:06 +0000 To: kde-core-devel Subject: Re: RFC v2: adding a temporary, non-BC gauranteed, 'private' library Message-Id: <200904241428.06757.aseigo () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=124060496913165 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart2113957.zjEcBtKHQ7" --nextPart2113957.zjEcBtKHQ7 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Friday 24 April 2009, Alexander Neundorf wrote: > On Friday 24 April 2009, Aaron J. Seigo wrote: > > On Friday 24 April 2009, Alexander Neundorf wrote: > > > Would it be an option to make it optional whether the lib is built > > > shared or static, making static the default and for releases, and you > > > as a developer could switch it to shared so you get the advantages you > > > mention ? > > > > is there a CMake directive along the lines of > > link_static_or_dynamic_depending_on_which_is_available? > > > > i don't realistically see us running around prior to release and changi= ng > > all possibly affected cmake files. > > If you skip the SHARED/STATIC/MODULE in > > (kde4_)add_library(foo (SHARED|STATIC|MODULE) ${srcs} ) > > then it depends on the value of the BUILD_SHARED_LIBS variable whether it > will be built as a shared or a static one. no, i meant the other way around. in target_add_libraries, if i put=20 knotificationareitem in there is it smart enough to know when to use static= vs=20 dynamic linkage depending on what's available on the system? i don't mind changing the CMakeLists.txt in knotificationareaitem (that's j= ust=20 one file :) but i do mind changing N different apps scattered all over kde'= s=20 svn. =2D-=20 Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software --nextPart2113957.zjEcBtKHQ7 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAknyINYACgkQ1rcusafx20MJcACdGTxK5emBbYHNg0b0yNAFTHq5 4tAAnidUHj424jBBzlhYQqyJfaQ8Fktt =HAW8 -----END PGP SIGNATURE----- --nextPart2113957.zjEcBtKHQ7--