zarb-ml/mageia-dev/2012-September/018409.html


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85

<!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=%3C50425FA9.9000208%40linux.it%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="018403.html">
   <LINK REL="Next"  HREF="018410.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] [RFC] kdelibs4-devel and cmake macros</H1>
    <B>Angelo Naselli</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=%3C50425FA9.9000208%40linux.it%3E"
       TITLE="[Mageia-dev] [RFC] kdelibs4-devel and cmake macros">anaselli at linux.it
       </A><BR>
    <I>Sat Sep  1 21:19:05 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="018403.html">[Mageia-dev] [RFC] kdelibs4-devel and cmake macros
</A></li>
        <LI>Next message: <A HREF="018410.html">[Mageia-dev] [RFC] kdelibs4-devel and cmake macros
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#18409">[ date ]</a>
              <a href="thread.html#18409">[ thread ]</a>
              <a href="subject.html#18409">[ subject ]</a>
              <a href="author.html#18409">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Il 01/09/2012 16:48, Colin Guthrie ha scritto:
&gt;<i> This doesn't sound like a good reason to me. Surely any porting
</I>&gt;<i> work you'll be doing you'll want to push upstream. Would upstream
</I>&gt;<i> be happy adding a dependency on KDE macros? I wouldn't expect so.
</I>&gt;<i> Thus the approach you've taken just now seems like a good one.
</I>
Good point.

But the real good approach in my opinion is that kde team should
send upstream -to cmake- their macros.

I don't like to reinvent the wheel, and moreover what happens as
soon as someone develops a library for developers and need the same
dependencies as in KDE applications (SQLite, SANE, SIP, RUby,...)?
Two FindXXX.cmake on the system.
I'm not sure it's good reason as well :)

Angelo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - <A HREF="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</A>

iEYEARECAAYFAlBCX6YACgkQqEs9DA4DquDH4ACgrUnCYKEZqO8YalLdufCLJt5M
UFwAoJz1ZQqEE3VtYcNdQFLyRdVzXZoY
=tWvW
-----END PGP SIGNATURE-----
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="018403.html">[Mageia-dev] [RFC] kdelibs4-devel and cmake macros
</A></li>
	<LI>Next message: <A HREF="018410.html">[Mageia-dev] [RFC] kdelibs4-devel and cmake macros
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#18409">[ date ]</a>
              <a href="thread.html#18409">[ thread ]</a>
              <a href="subject.html#18409">[ subject ]</a>
              <a href="author.html#18409">[ 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>