[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zeromq-dev
Subject:    Re: [zeromq-dev] Change Build Tool To CMake
From:       Steven McCoy <steven.mccoy () miru ! hk>
Date:       2010-01-27 12:32:38
Message-ID: 7f8a97b61001270432t5953685q2ec1b4e68c76b947 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2010/1/27 Peter Alexander <vel.accel@gmail.com>

> My understanding is that CMake is being widely adopted over autotools
> for many various reasons in many complex projects (e.g. KDE, VTK,
> 3dSlicer, and Apache Qpid, and potentially Qt).
>
> I find it to be a very intuitive, flexible, fast and complete build
> system. I haven't built a project with autoconf/autotools in years..
> imho naturally.
>
>
If you want a challenge, have a go with OpenPGM 2, ensuring compatibility on
RHEL 4 with CMake 2.4 all the way through to modern distributions: RHEL 5.4,
Fedora Core 12, Ubuntu 9.10, etc.  It looks like there is no out-of-box
support for Intel C Compiler 11, Sun Studio, MinGW32 or MinGW-w64 at all on
Linux.  I already had to write a custom macro for PIC shared objects which
entailed a lot of slash escapes:

http://code.google.com/p/openpgm/source/browse/tags/release-1-2-18/openpgm/pgm/CMake/macros.cmake

The other parts are reasonably straight forward - multiple build systems:
release, debug, profiled, 32 or 64-bit builds,  then all the options and
pkgconfig based auto-configuration.  Integrating NET-SNMP can be painful as
on RedHat it insists on pulling in RPM libraries, Perl, and others.  Source
code for unit tests sits side-by-side with the target modules, but must be
compiled with less strict warnings.

I'd like to get Wine-gcc working but there's just too many things broken.

Google were using SCons for Chromium but recently moved back to Make.  I'd
love to see OpenOffice.org or the Mozilla projects migrate to SCons or CMake
as they have absolutely zero dependency analysis with Make today.  20 minute
re-build process for changing one source file is insane, especially so if
you cannot run from the build directory.

-- 
Steve-o

[Attachment #5 (text/html)]

2010/1/27 Peter Alexander <span dir="ltr">&lt;<a \
href="mailto:vel.accel@gmail.com">vel.accel@gmail.com</a>&gt;</span><br><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div><div></div><div class="h5">My understanding is that CMake is being widely \
adopted over autotools</div></div> for many various reasons in many complex projects \
(e.g. KDE, VTK,<br> 3dSlicer, and Apache Qpid, and potentially Qt).<br>
<br>
I find it to be a very intuitive, flexible, fast and complete build<br>
system. I haven&#39;t built a project with autoconf/autotools in years..<br>
imho naturally.<br><br></blockquote><div><br></div><div>If you want a challenge, have \
a go with OpenPGM 2, ensuring compatibility on RHEL 4 with CMake 2.4 all the way \
through to modern distributions: RHEL 5.4, Fedora Core 12, Ubuntu 9.10, etc.  It \
looks like there is no out-of-box support for Intel C Compiler 11, Sun Studio, \
MinGW32 or MinGW-w64 at all on Linux.  I already had to write a custom macro for PIC \
shared objects which entailed a lot of slash escapes:</div>

<div><br></div><div><a \
href="http://code.google.com/p/openpgm/source/browse/tags/release-1-2-18/openpgm/pgm/C \
Make/macros.cmake">http://code.google.com/p/openpgm/source/browse/tags/release-1-2-18/openpgm/pgm/CMake/macros.cmake</a></div>


<div><br></div><div>The other parts are reasonably straight forward - multiple build \
systems: release, debug, profiled, 32 or 64-bit builds,  then all the options and \
pkgconfig based auto-configuration.  Integrating NET-SNMP can be painful as on RedHat \
it insists on pulling in RPM libraries, Perl, and others.  Source code for unit tests \
sits side-by-side with the target modules, but must be compiled with less strict \
warnings.</div>

<div><br></div><div>I&#39;d like to get Wine-gcc working but there&#39;s just too \
many things broken.</div><div><br></div><div>Google were using SCons for Chromium but \
recently moved back to Make.  I&#39;d love to see OpenOffice.org or the Mozilla \
projects migrate to SCons or CMake as they have absolutely zero dependency analysis \
with Make today.  20 minute re-build process for changing one source file is insane, \
especially so if you cannot run from the build directory.</div>

<div><br></div><div>-- </div><div>Steve-o</div></div>



_______________________________________________
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev


[prev in list] [next in list] [prev in thread] [next in thread]