9 Dec
2011
9 Dec
'11
6:23 a.m.
I'm trying to build some trinity
components manually, since no
binaries, nor build scrips (PKGBUILD) are available for my
distro
(arch),
There are some archers hanging out here. I would be surprised if there are no build
scripts. They might be cleverly hidden, but I'm sure they exist.
and I wonder, why when I try to compile something
using
autotools (because obviously it hasn't been ported to cmake
yet) it
keeps me asking for Qt >=4.3 and <5.0.
I have the same problem on Slackware. I submitted bug report 582
(http://bugs.pearsoncomputing.net/show_bug.cgi?id=582) against the problem. My workaround
was to remove the Qt4 package from my build system.
Besides I looked a little at files present in the
admin dir
and I
found that some of the paths for libraries are hardcoded
and point to
(example) /usr/share/kde3 or /usr/share/qt.
Some examples?
Another thing, shouldn't automake files be removed
form
components
that have been ported to CMake. Since autotools-based
compiling aren't
really supported for those...
I'm sure that will happen eventually.
And I'd be grateful of someone could write a little about
how to port
trinity components to cmake. I'd like to help, I get the
main idea,
but I don't know where too look for dependencies and stuff
like that.
That is a great idea. Serghei is the master cmake planner here. Whether he has time for
writing is up to him. Some others here have helped, so maybe somebody can start a wiki
page about the topic.
Darrell