I need a robust method of detecting whether I should use automake or cmake to build a package. During this transition to cmake both build options need to be supported.

I realize if I build with auotmake on more recent systems that the build effort will fail, but I can continue building on older systems that support older versions of automake.

I was detecting the presence of CMakeLists.txt, but now I am unsure that is a good idea.

Is there a better, more sound method to use to know when a package will build under cmake?

Darrell


--- On Mon, 3/7/11, Serghei Amelian <serghei@...> wrote:

> From: Serghei Amelian <serghei@...>
> Subject: Re: [trinity-devel] ALSA support are requested, but not found on your system
> To: trinity-devel@...
> Date: Monday, March 7, 2011, 8:08 PM
> On Tuesday 08 March 2011 03:57:53
> Darrell Anderson wrote:
> > Yay!
> >
> > I updated to cmake 2.8.4.
> >
> > arts built without errors.
> >
> > Just to be sure I rebuilt tqtinterface too.
> >
> > Where is the short list of what packages should build
> with cmake?
> >
> > Darrell
> 
> There: kdelibs, kdebase, kdepim, kdevelop, kwebdev, amarok,
> knetworkmanager 
> and few more, which are not commited to svn yet.
> 
> Each of them have a list of options which can be activated
> or deactivated. 
> Open main CMakeLists.txt of each package to check which
> options are available 
> (for this, you can use ccmake as well, instead plain
> cmake).
> 
> Most of packages needs argument "-DBUILD_ALL=ON"
> 
> -- 
> Serghei
> 
> ---------------------------------------------------------------------
> 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
> 
>