trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: January 2012

Re: [trinity-devel] autotools to cmake

From: L0ner sh4dou <sh4dou@...>
Date: Sun, 15 Jan 2012 12:32:01 +0100
2012/1/15 Robert Xu <robxu9@...>:
> Hello all,
>
> I've JUST discovered these scripts while browsing the Cmake wiki randomly...
> http://websvn.kde.org/trunk/KDE/kdesdk/cmake/scripts/
>
> There seem to be some KDE3 conversion scripts o3o
> Could this help make our life a lot easier or no?
>

I worte here about them some time ago. They need some fixing since
when I used them they couldn't generate correct CMake files for
trinity.
Anyway the preffered mothod of porting is to wite CMake files
manually, since that way you have more control.

---------- Forwarded message ----------
From: Serghei Amelian <serghei@...>
Date: 2011/12/9
Subject: Re: [trinity-devel] Porting to cmake.
To: trinity-devel@...

Actually writing cmake rules are realy simple, because I developed macros to
simplify the process, is a simple copy/paste procedure. Most of time is
consumed developing check procedures.

http://www.trinitydesktop.org/wiki/bin/view/Developers/CMakeConversionProcess

Manually porting is preffered, because resulted files are very clean,
predictible and easily debugable, with no useless dependencies.

--
Serghei
-----------------------------------


> --
> email is so cluttered that it triggered this signature. :|
> xu_robert will be away from 11 Jan to 28 Jan with note: finals and SATs.
> later daze. :: Robert Xu :: rxu.lincomlinux.org :: protocol.by/rxu
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-devel-unsubscribe@...
> For additional commands, e-mail: trinity-devel-help@...
> 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
>