svn - applications/gtk-qt-engine will builds as is, but the cmake files look a bit rough...
27 Feb
2011
27 Feb
'11
8:29 a.m.
Just a note:
applications/gtk-qt-engine builds with the current CMakeLists.txt in the
directory. But the file looks like a generic cmakelists pulled from a project
other than Trinity. I don't think it matters from looking at the simplicity of
the code. Without the Trinity check included, you do have to supply a complete
set of cmake variables with path, pkgconfig, etc. included. I don't think it
will cause problems later, but it is somewhat of an oddity to look in a
CMakeLists.txt and not see Serghei's familiar Trinity header :)
The build produces the following package files:
02:06 supersff:~/arch/tnotes> cat flist/trinity-app-gtk-qt-engine-list.txt
------------------------------------------------------------
Package: trinity-app-gtk-qt-engine 1222892-1.0
------------------------------------------------------------
/usr/
/usr/lib/
/usr/lib/gtk-2.0/
/usr/lib/gtk-2.0/2.10.0/
/usr/lib/gtk-2.0/2.10.0/engines/
/usr/lib/gtk-2.0/2.10.0/engines/libqtengine.so
/usr/share/
/usr/share/themes/
/usr/share/themes/Qt/
/usr/share/themes/Qt/gtk-2.0/
/usr/share/themes/Qt/gtk-2.0/gtkrc
From what I can tell -- it looks complete. If you notice something missing,
let me know.
--
David C. Rankin, J.D.,P.E.
27 Feb
27 Feb
5:48 p.m.
New subject: [i686 build fails? ] was Re: [trinity-devel] svn - applications/gtk-qt-engine will builds as is, but the cmake files look a bit rough...
On 02/27/2011 02:29 AM, David C. Rankin wrote:
Just a note:
applications/gtk-qt-engine builds with the current CMakeLists.txt in the
directory. But the file looks like a generic cmakelists pulled from a project
other than Trinity. I don't think it matters from looking at the simplicity of
the code. Without the Trinity check included, you do have to supply a complete
set of cmake variables with path, pkgconfig, etc. included. I don't think it
will cause problems later, but it is somewhat of an oddity to look in a
CMakeLists.txt and not see Serghei's familiar Trinity header :)
The build produces the following package files:
02:06 supersff:~/arch/tnotes> cat flist/trinity-app-gtk-qt-engine-list.txt
------------------------------------------------------------
Package: trinity-app-gtk-qt-engine 1222892-1.0
------------------------------------------------------------
/usr/
/usr/lib/
/usr/lib/gtk-2.0/
/usr/lib/gtk-2.0/2.10.0/
/usr/lib/gtk-2.0/2.10.0/engines/
/usr/lib/gtk-2.0/2.10.0/engines/libqtengine.so
/usr/share/
/usr/share/themes/
/usr/share/themes/Qt/
/usr/share/themes/Qt/gtk-2.0/
/usr/share/themes/Qt/gtk-2.0/gtkrc
From what I can tell -- it looks complete. If you notice something missing,
let me know.
Well,
I can't figure out why there would be any difference building on i686 or
x86_64, but the i686 build fails while the x86_64 build worked?? The i686 build
fails when building with a fresh download of the gtk-qt-engine source here:
[ 51%] Building CXX object kcm_gtk/CMakeFiles/kcm_kcmgtk.dir/kcmgtk.o
cd /home/david/tblds/trinity-app-gtk-qt-engine/src/gtk-qt-engine/kcm_gtk &&
/usr/bin/c++ -Dkcm_kcmgtk_EXPORTS -DQT_SHARED -DQT_NO_DEBUG
-DQT_THREAD_SUPPORT -D_REENTRANT -DQT_CLEAN_NAMESPACE -D_GNU_SOURCE
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -march=i686 -mtune=generic -O2 -pipe
-Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wconversion
-Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -Wformat-security
-fno-exceptions -fno-check-new -fno-common -O2 -fPIC -I/opt/qt/include
-I/opt/trinity/include -o CMakeFiles/kcm_kcmgtk.dir/kcmgtk.o -c
/home/david/tblds/trinity-app-gtk-qt-engine/src/gtk-qt-engine/kcm_gtk/kcmgtk.cpp
In file included from
/home/david/tblds/trinity-app-gtk-qt-engine/src/gtk-qt-engine/kcm_gtk/kcmgtk.cpp:23:0:
/opt/trinity/include/klocale.h:25:22: fatal error: tqstring.h: No such file or
directory
compilation terminated.
make[2]: *** [kcm_gtk/CMakeFiles/kcm_kcmgtk.dir/kcmgtk.o] Error 1
make[2]: Leaving directory
`/home/david/tblds/trinity-app-gtk-qt-engine/src/gtk-qt-engine'
make[1]: *** [kcm_gtk/CMakeFiles/kcm_kcmgtk.dir/all] Error 2
make[1]: Leaving directory
`/home/david/tblds/trinity-app-gtk-qt-engine/src/gtk-qt-engine'
make: *** [all] Error 2
Aborting...
It doesn't seem to be seeing my full include path:
export
CMAKE_INCLUDE_PATH=/opt/qt/include:/opt/qt/include/tqt:/usr/include/dbus-1.0:/opt/trinity/include:/opt/trinity/include/libkrandr
because tqstring.h is present in /opt/qt/include/tqt:
02:30 supersff:~/tblds> l /opt/qt/include/tqt/tqstring.h
-rw-r--r-- 1 root root 1214 Feb 19 02:17 /opt/qt/include/tqt/tqstring.h
What is strange, if I then try and rebuild with the gtk-qt-engine source
already present from the first failed build, then the build stops earlier at 14%:
[ 14%] Building CXX object kcm_gtk/CMakeFiles/kcm_kcmgtk.dir/kcmgtk.o
cd /home/david/tblds/trinity-app-gtk-qt-engine/src/gtk-qt-engine/kcm_gtk &&
/usr/bin/c++ -Dkcm_kcmgtk_EXPORTS -DQT_SHARED -DQT_NO_DEBUG
-DQT_THREAD_SUPPORT -D_REENTRANT -DQT_CLEAN_NAMESPACE -D_GNU_SOURCE
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -march=i686 -mtune=generic -O2 -pipe
-Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wconversion
-Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -Wformat-security
-fno-exceptions -fno-check-new -fno-common -O2 -fPIC -I/opt/qt/include
-I/opt/trinity/include -o CMakeFiles/kcm_kcmgtk.dir/kcmgtk.o -c
/home/david/tblds/trinity-app-gtk-qt-engine/src/gtk-qt-engine/kcm_gtk/kcmgtk.cpp
In file included from
/home/david/tblds/trinity-app-gtk-qt-engine/src/gtk-qt-engine/kcm_gtk/kcmgtk.cpp:23:0:
/opt/trinity/include/klocale.h:25:22: fatal error: tqstring.h: No such file or
directory
compilation terminated.
make[2]: *** [kcm_gtk/CMakeFiles/kcm_kcmgtk.dir/kcmgtk.o] Error 1
make[2]: Leaving directory
`/home/david/tblds/trinity-app-gtk-qt-engine/src/gtk-qt-engine'
make[1]: *** [kcm_gtk/CMakeFiles/kcm_kcmgtk.dir/all] Error 2
make[1]: Leaving directory
`/home/david/tblds/trinity-app-gtk-qt-engine/src/gtk-qt-engine'
make: *** [all] Error 2
Can't explain it, but something needs to be tweaked :)
--
David C. Rankin, J.D.,P.E.
7 p.m.
New subject: [trinity-devel] [i686 build fails? ] was Re: [trinity-devel] svn - applications/gtk-qt-engine will builds as is, but the cmake files look a bit rough...
On 02/27/2011 11:48 AM, David C. Rankin wrote:
I can't figure out why there would be any
difference building on i686 or
x86_64, but the i686 build fails while the x86_64 build worked?? The i686 build
fails when building with a fresh download of the gtk-qt-engine source here:
Correction it was the build on another i686 box that succeeded. Same build
script. Strange... (I'll keep looking..)
--
David C. Rankin, J.D.,P.E.
4813
days inactive
4813
days old
2 comments
1 participants
participants (1)
-
David C. Rankin