From kde-devel Mon Sep 20 20:43:49 2004 From: Adriaan de Groot Date: Mon, 20 Sep 2004 20:43:49 +0000 To: kde-devel Subject: kopete groupwise libs and closures Message-Id: <200409202243.54012.groot () kde ! org> X-MARC-Message: https://marc.info/?l=kde-devel&m=109571311507530 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi y'all, I'm muddling a bit with --enable-final and --enable-closure, and kopete/protocols/groupwise/libgroupwise is a bit of a stumbling block: the library in the subdir tasks/ depends on the Task class in ., which at the same time . depends on the subclasses of Task in tasks/. 1) One approach is to "don't do that then" and say that --enable-closure can't be used in kdenetwork (anywhere, since there's no per-dir noclosure setting like nofinal). 2) Another is to hackishly add a noclosure option to KDE_OPTIONS, like I recently mentioned on -core-devel. It's not pretty, though, and very single-use (ie. here). 3) A third is to rearrange the libgroupwise/ dir a little so that it doesn't have these circular dependencies, for instance: - - mv tasks/* . - - mv the relvant subset from . to tasks/ Personally, I think only (3) is really doable if we want to call - --enable-closure supported at all. What do y'all think? ======== Dependencies, specific for-instances: libgroupwise/privacymanager.cpp:205: undefined reference to `PrivacyItemTask::dn() const' (PrivacyItemTask is in libgroupwise/tasks/) libgroupwise/tasks/conferencetask.cpp:98: undefined reference to `EventTransfer::hasMessage()' (EventTransfer is in libgroupwise/) - -- Don't worry, 't ain't no shame to be stupid - ol' mouse. GPG: FEA2 A3FE Adriaan de Groot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBT0EJdqzuAf6io/4RAoTtAJ4lMDjeHzbUBOdQQhD2k3W7bH31TACcDeGb uB76K7SjQ7+LiAAal+hGxkY= =26fV -----END PGP SIGNATURE----- >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<