14 Mar
2011
14 Mar
'11
9:04 p.m.
As I wrote in my previous post, I haven't YET given up.
Yes, I have noticed the build time difference with tqtinterface, arts, kdelibs, and
kdebase. :) Thank you Serghei!
The core Trinity modules are almost ported to cmake? Hmm. I don't see that in my local
svn tree. I updated svn yesterday. I see the following:
tqtinterface
arts
kdelibs
kdebase
kdegraphics
kdevelop
kdewebdev
kdepim
Core packages with no CMakeLists.txt:
kdebindings
kdeaccessibility
kdeutils
kdemultimedia
kdenetwork
kdeadmin
kdeartwork
kdegames
kdetoys
kdeedu
kdeaddons
kdesdk
Perhap I'm missing something obvious, but that does not seem like "almost"
to me. :)
Darrell
--- On Mon, 3/14/11, Timothy Pearson <kb9vqf(a)pearsoncomputing.net> wrote:
From: Timothy Pearson
<kb9vqf(a)pearsoncomputing.net>
Subject: Re: [trinity-devel] Downgrading autoconf/automake
To: trinity-devel(a)lists.pearsoncomputing.net
Date: Monday, March 14, 2011, 3:19 PM
From what I hear, cmake porting isn't too hard once
you get used to
it. I will be helping with this once I get my new
hard
disk (which I
will be ordering on Thursday).
As I understand it (someone correct me if I'm wrong),
there is too
much risk of the autotools api changing again,
which
is what broke
building to begin with, so rather than having to
worry
about fixing
the headers with each new version of autotools,
it'd
be much easier to
just use cmake. I've also heard that a
project that is
correctly setup
for cmake can be easier to work with when doing
the
actual build than
when trying to build with autotools.
Not to mention the time required for building the following
packages:
kdelibs:
with Automake: 50 minutes
with CMake: 7 minutes
kdebase:
with Automake: 60 minutes
with CMake: 10 minutes
See a distinct advantage there? ;-) This would
greatly help when fixing
bugs or adding new features.
Also, from what I can see, the core Trinity modules are
almost ported to
CMake. I am working through the Debian/Ubuntu build
glitches now, and
will have a better handle on the current status of things
as my builds
progress.
Don't give up yet!
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting