Message: previous - next
Month: October 2012

Re: [trinity-devel] [tdegraphics][autotools] regenerate Autoconf/Automake files

From: Darrell Anderson <humanreadable@...>
Date: Wed, 31 Oct 2012 11:44:08 -0700 (PDT)
> Now I understand why nobody have seen so many errors in CMakefiles
> before me and I've got so a lot to fix =)... It's all because
> everybody uses such way to build it...

Please stay on your path. :) For a long time I have wanted to see this happen in Trinity. As the problem basically reduces to packaging, you will be blazing a nice trail. From those efforts I can adapt my own (Slackware) build scripts and the result will be, hopefully, a nice how-to on the wiki.

I don't doubt there are likely bugs in the build process when splitting packages that require nominal patching, but I think we first need to ensure you can build the complete package. :)

In the mean time, as I am unfamiliar with gentoo practices, I recommend first focusing on building the complete package. Get that working to provide you a known base. Thereafter start splitting packages into smaller packages.

> Take a look into my log in the first message (it's corrupted by mail
> sysyem but still readable, here is the normal one:
> )...
> I'm doing the same things...

I'm not an automake guru, but my first thought was what version of automake are you using?

Then I thought this probably is an irrelevant question. :) All of the cmake and admin directories in each module are clones from respective masters in the upstream GIT repository. Patching any of those files means patching only the master copy. Local copies of the repo will not keep the links to the master directories, at least that does not happen on my system. There is a script that is run at the upstream servers to keep everything in sync. In summary this means if one build fails then others are likely to fail too because the base files are all clones.

A key file in this explanation is admin/

  automake*1.6.* | automake*1.7* | automake*1.8* | automake*1.9* | automake*1.10* | automake*1.11* | automake*1.12*)

To my knowledge that covers all expected versions of automake. Hence my statement that the question probably is irrelevant. :)