I'm trying to build Trinity from SVN. I'm still using my old build scripts with automake. As I have not tested my build environment since last autumn, I wanted to make one run to ensure everything still works before trying other things. Basically, start with a known good environment.
According to recent list conversations, building with automake should still work with distros using older autotools.
Building tqtinterface failed immediately:
============================================ cp: cannot create regular file `admin/libtool.m4.in': No such file or directory cp: cannot create regular file `admin/ltmain.sh': No such file or directory make: admin/Makefile.common: No such file or directory make: *** No rule to make target `admin/Makefile.common'. Stop. ============================================
There no longer is an svn admin directory in the tqtinterface sources.
The wiki says "The current SVN tree is being ported to CMake. You cannot build part of the tree with CMake and then start building with autoconf."
Do I now have to build tqtinterface with cmake? If so, then I according to the wiki I cannot build the remaining packages with autotools.
I saw nothing obvious in the list archives.
Darrell
On Sat, Mar 5, 2011 at 10:24 PM, Darrell Anderson humanreadable@yahoo.com wrote:
I'm trying to build Trinity from SVN. I'm still using my old build scripts with automake. As I have not tested my build environment since last autumn, I wanted to make one run to ensure everything still works before trying other things. Basically, start with a known good environment.
According to recent list conversations, building with automake should still work with distros using older autotools.
Building tqtinterface failed immediately:
============================================ cp: cannot create regular file `admin/libtool.m4.in': No such file or directory cp: cannot create regular file `admin/ltmain.sh': No such file or directory make: admin/Makefile.common: No such file or directory make: *** No rule to make target `admin/Makefile.common'. Stop. ============================================
There no longer is an svn admin directory in the tqtinterface sources.
The wiki says "The current SVN tree is being ported to CMake. You cannot build part of the tree with CMake and then start building with autoconf."
Do I now have to build tqtinterface with cmake? If so, then I according to the wiki I cannot build the remaining packages with autotools.
I saw nothing obvious in the list archives.
I think that just means that you can't build part of TDE using autotools and the other part with cmake (as in, a mixed build). But you should be able to one OR the other, from what I've seen in the mailing list.
Considering there were no major changes in tqtinterface between 3.5.12 and the svn version, you may be able to grab the 3.5.12 tarball and use it's admin directory, but I'd suggest waiting for Serghei (spelling?) (the TDE cmake wizard) to input to let you know if this will work.
It may also work if the admin directory in 3.5.12 was empty -- just mkdir it and then generate the autools stuff. I never had a good chance to explore the TDE sources, so I couldn't tell you if it was empty or not, though...
On 03/05/2011 11:03 PM, Kristopher Gamrat wrote:
Considering there were no major changes in tqtinterface between 3.5.12 and the svn version, you may be able to grab the 3.5.12 tarball and use it's admin directory, but I'd suggest waiting for Serghei (spelling?) (the TDE cmake wizard) to input to let you know if this will work.
Can you point me to the 3.5.12 source tarball? I have looked at the web site but I couldn't find it
Thanks
http://mirror.its.uidaho.edu/pub/trinity/releases/3.5.12/
Darrell
--- On Sun, 3/6/11, Baho Utot baho-utot@columbus.rr.com wrote:
From: Baho Utot baho-utot@columbus.rr.com Subject: Re: [trinity-devel] Building tqtinterface fails To: trinity-devel@lists.pearsoncomputing.net Date: Sunday, March 6, 2011, 8:05 AM On 03/05/2011 11:03 PM, Kristopher Gamrat wrote:
Considering there were no major changes in
tqtinterface between 3.5.12
and the svn version, you may be able to grab the
3.5.12 tarball and
use it's admin directory, but I'd suggest waiting for
Serghei
(spelling?) (the TDE cmake wizard) to input to let you
know if this
will work.
Can you point me to the 3.5.12 source tarball? I have looked at the web site but I couldn't find it
Thanks
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@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
On 03/06/2011 12:33 PM, Darrell Anderson wrote:
http://mirror.its.uidaho.edu/pub/trinity/releases/3.5.12/
Darrell
[putollin]
Thanks
On Sun, Mar 6, 2011 at 9:05 AM, Baho Utot baho-utot@columbus.rr.com wrote:
On 03/05/2011 11:03 PM, Kristopher Gamrat wrote:
Considering there were no major changes in tqtinterface between 3.5.12 and the svn version, you may be able to grab the 3.5.12 tarball and use it's admin directory, but I'd suggest waiting for Serghei (spelling?) (the TDE cmake wizard) to input to let you know if this will work.
Can you point me to the 3.5.12 source tarball? I have looked at the web site but I couldn't find it
The link is in the left navigation bar near the bottom. Clicking that will take you to a page with a "What's New" link, links to installation instructions for Debian, Ubuntu, and Slackware, and a link to download source tarballs. This is a link to tarballs for each individual package, with tarballs for the entire source near the bottom of the page. This is probably a bit cleaner and easier than looking at an FTP list if you're not used to FTP (most mirrors show stuff in FTP-style, even if they use HTTP).
On Sunday 06 March 2011 05:24:47 Darrell Anderson wrote:
[...]
The wiki says "The current SVN tree is being ported to CMake. You cannot build part of the tree with CMake and then start building with autoconf."
Actually this is not really true statement. Few months ago I built kdebase (with autotools) against kdelibs (build using cmake). Of course, cmake will not build against autotools, because cmake needs few special helper files (import files).
Do I now have to build tqtinterface with cmake? If so, then I according to the wiki I cannot build the remaining packages with autotools.
You can try. Building using cmake is really simple (and faster as well):
mkdir /tmp/tqt.build cd /tmp/tqt.build cmake /path/to/tqt/source \ -DCMAKE_INSTALL_PREFIX=/opt/tqt -DWITH_QT3=ON make sudo make install
1) Note that out-of-source mode is recommended. 2) Be sure that QTDIR variable environment are set, to avoid troubles while detecting path to QT 3) Is required patched QT3 ( http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/Qt3 )
Good luck
Noted about qt3.
Does qt3 need to be rebuilt before tqtinterface?
Can tqtinterface only be built now with cmake?
What does "out-of-source mode" mean?
Darrell
--- On Sun, 3/6/11, Serghei Amelian serghei@thel.ro wrote:
From: Serghei Amelian serghei@thel.ro Subject: Re: [trinity-devel] Building tqtinterface fails To: trinity-devel@lists.pearsoncomputing.net Date: Sunday, March 6, 2011, 2:52 AM On Sunday 06 March 2011 05:24:47 Darrell Anderson wrote:
[...]
The wiki says "The current SVN tree is being ported to
CMake. You cannot
build part of the tree with CMake and then start
building with autoconf."
Actually this is not really true statement. Few months ago I built kdebase (with autotools) against kdelibs (build using cmake). Of course, cmake will not build against autotools, because cmake needs few special helper files (import files).
Do I now have to build tqtinterface with cmake? If so,
then I according to
the wiki I cannot build the remaining packages with
autotools.
You can try. Building using cmake is really simple (and faster as well):
mkdir /tmp/tqt.build cd /tmp/tqt.build cmake /path/to/tqt/source \ -DCMAKE_INSTALL_PREFIX=/opt/tqt -DWITH_QT3=ON make sudo make install
- Note that out-of-source mode is recommended.
- Be sure that QTDIR variable environment are set, to
avoid troubles while detecting path to QT 3) Is required patched QT3 ( http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/Qt3 )
Good luck
-- Serghei
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@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
On 6 March 2011 12:37, Darrell Anderson humanreadable@yahoo.com wrote:
Noted about qt3.
Does qt3 need to be rebuilt before tqtinterface?
Can tqtinterface only be built now with cmake?
What does "out-of-source mode" mean?
Darrell
--- On Sun, 3/6/11, Serghei Amelian serghei@thel.ro wrote:
From: Serghei Amelian serghei@thel.ro Subject: Re: [trinity-devel] Building tqtinterface fails To: trinity-devel@lists.pearsoncomputing.net Date: Sunday, March 6, 2011, 2:52 AM On Sunday 06 March 2011 05:24:47 Darrell Anderson wrote:
[...]
The wiki says "The current SVN tree is being ported to
CMake. You cannot
build part of the tree with CMake and then start
building with autoconf."
Actually this is not really true statement. Few months ago I built kdebase (with autotools) against kdelibs (build using cmake). Of course, cmake will not build against autotools, because cmake needs few special helper files (import files).
Do I now have to build tqtinterface with cmake? If so,
then I according to
the wiki I cannot build the remaining packages with
autotools.
You can try. Building using cmake is really simple (and faster as well):
mkdir /tmp/tqt.build cd /tmp/tqt.build cmake /path/to/tqt/source \ -DCMAKE_INSTALL_PREFIX=/opt/tqt -DWITH_QT3=ON make sudo make install
- Note that out-of-source mode is recommended.
- Be sure that QTDIR variable environment are set, to
avoid troubles while detecting path to QT 3) Is required patched QT3 ( http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/Qt3 )
Good luck
-- Serghei
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@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
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@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
Qt3 needs the patch, here: http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/Qt3
It adds some support functions afaik and won't break anything
Calvin.
On Sunday 06 March 2011 19:37:14 Darrell Anderson wrote:
Noted about qt3.
Does qt3 need to be rebuilt before tqtinterface?
Yes, you need patched version.
Can tqtinterface only be built now with cmake?
I'm not sure, Tim can confim if dropped autotools suport.
What does "out-of-source mode" mean?
Keeping source tree separate from binaries tree (make is run out of source tree).
Darrell
Does qt3 need to be rebuilt before tqtinterface?
Yes, you need patched version.
Ok.
A previous presumption was that qt3 was installed from the distro. Patching qt3 somewhat changes that presumption.
Seems to me the qt3 sources should now be a part of the svn sources tree, already patched.
Darrell
On Sunday 06 March 2011 20:34:43 Darrell Anderson wrote:
Does qt3 need to be rebuilt before tqtinterface?
Yes, you need patched version.
Do the qca-1 and qca-tls packages need to be rebuilt against the patched qt-3.3.c package?
Nope, as far I know, qt3 do not broke backward compatibility.
-
Baho Utot -
calvin morrison -
Darrell Anderson -
Kristopher Gamrat -
Serghei Amelian