<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] [RFC] kdelibs4-devel and cmake macros
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20kdelibs4-devel%20and%20cmake%20macros&In-Reply-To=%3C50422043.5080402%40colin.guthr.ie%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="018401.html">
<LINK REL="Next" HREF="018409.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] [RFC] kdelibs4-devel and cmake macros</H1>
<B>Colin Guthrie</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20kdelibs4-devel%20and%20cmake%20macros&In-Reply-To=%3C50422043.5080402%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] [RFC] kdelibs4-devel and cmake macros">mageia at colin.guthr.ie
</A><BR>
<I>Sat Sep 1 16:48:35 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="018401.html">[Mageia-dev] [RFC] kdelibs4-devel and cmake macros
</A></li>
<LI>Next message: <A HREF="018409.html">[Mageia-dev] [RFC] kdelibs4-devel and cmake macros
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18403">[ date ]</a>
<a href="thread.html#18403">[ thread ]</a>
<a href="subject.html#18403">[ subject ]</a>
<a href="author.html#18403">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and Matteo at 01/09/12 14:12 did gyre and gimble:
><i> On 01/09/2012 14:36, Angelo Naselli wrote:
</I>>><i> Hi, I recently had to work with some cmake macros and i found that
</I>>><i> they were already on the system installing kdelibs4-devel. I am a
</I>>><i> KDE user and developer so it's not a big problem for me, but some
</I>>><i> colleagues are not. Now isn't be possible to have a
</I>>><i> kdelibs4-cmake-macros package? I think that can be useful for those
</I>>><i> who don't want to install a lot of kde developer packages and get
</I>>><i> benefit by using already developed macros.
</I>><i>
</I>>><i> WDYT? Angelo
</I>><i> +1
</I>><i>
</I>><i> Just for example, currently I need FindGLIB2.cmake to port an
</I>><i> application from an old style makefile to cmake but the application is
</I>><i> not based on kde and I can't make kdelibs4 a requirement.
</I>><i> To avoid this requirement I've to implement FindGLIB2 functionalities
</I>><i> into the main CMakeLists.txt but it is not that comfortable.
</I>
This doesn't sound like a good reason to me. Surely any porting work
you'll be doing you'll want to push upstream. Would upstream be happy
adding a dependency on KDE macros? I wouldn't expect so. Thus the
approach you've taken just now seems like a good one.
Col
--
Colin Guthrie
colin(at)mageia.org
<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
Day Job:
Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
Open Source:
Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="018401.html">[Mageia-dev] [RFC] kdelibs4-devel and cmake macros
</A></li>
<LI>Next message: <A HREF="018409.html">[Mageia-dev] [RFC] kdelibs4-devel and cmake macros
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18403">[ date ]</a>
<a href="thread.html#18403">[ thread ]</a>
<a href="subject.html#18403">[ subject ]</a>
<a href="author.html#18403">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>