Add qt3 to poky
cover Add qt3 to poky
From: Xiaofeng Yan <[email protected]>
Packages qt3 from "OE" is needed by LSB Test Suite. So I add it to Poky.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: xiaofeng/distro
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/distro
Thanks,
Xiaofeng Yan <[email protected]>
---
Xiaofeng Yan (2):
qt3: Add qt3 because lsb test need it
qt3: Add two class(qt3e.bbclass and qt3x11.bbclass) files into
meta/classess/
meta/classes/qt3e.bbclass | 11 +++ meta/classes/qt3x11.bbclass | 15 ++++ meta/recipes-qt/qt3/qt-x11-free-common.inc | 91 +++++++++++++++++++++ meta/recipes-qt/qt3/qt-x11-free-native_3.3.5.bb | 65 +++++++++++++++ meta/recipes-qt/qt3/qt-x11-free/configure.patch | 51 ++++++++++++ meta/recipes-qt/qt3/qt-x11-free/gcc4_1-HACK.patch | 28 +++++++ meta/recipes-qt/qt3/qt-x11-free/no-examples.patch | 16 ++++ meta/recipes-qt/qt3/qt-x11-free_3.3.6.bb | 13 +++ meta/recipes-qt/qt3/qt-x11-free_3.3.7.bb | 16 ++++ 9 files changed, 306 insertions(+), 0 deletions(-) create mode 100644 meta/classes/qt3e.bbclass create mode 100644 meta/classes/qt3x11.bbclass create mode 100644 meta/recipes-qt/qt3/qt-x11-free-common.inc create mode 100644 meta/recipes-qt/qt3/qt-x11-free-native_3.3.5.bb create mode 100644 meta/recipes-qt/qt3/qt-x11-free/configure.patch create mode 100644 meta/recipes-qt/qt3/qt-x11-free/gcc4_1-HACK.patch create mode 100644 meta/recipes-qt/qt3/qt-x11-free/no-examples.patch create mode 100644 meta/recipes-qt/qt3/qt-x11-free_3.3.6.bb create mode 100644 meta/recipes-qt/qt3/qt-x11-free_3.3.7.bb
PATCH 1/2 qt3: Add qt3 because lsb test need it
From: Xiaofeng Yan <[email protected]>
These package has been added from meta-openembedded.
Changes from the meta-openembedded version:
1 Add "-L ${STAGING_LIBDIR} -I ${STAGING_INCDIR_NATIVE}" to function do_configure() in file qt-x11-free-native_3.3.5.bb
2 Remove do_stage and transfer contents from do_stage to do_install in file qt-x11-free-native_3.3.5.bb
3 Add LIC_FILES_CHKSUM in file qt-x11-free-native_3.3.5.bb
4 Remove -plugin-sql-mysql from "QT_CONFIG_FLAGS" in file qt-x11-free-common.inc
5 Add "install -m 0755 ${STAGING_BINDIR_NATIVE}/moc3 ${S}/bin/moc install -m 0755 ${STAGING_BINDIR_NATIVE}/uic3 ${S}/bin/uic" to function do_compile() in file qt-x11-free-common.inc 6 Change do_stage to do_install_prepend in file qt-x11-free-common.inc
7 Add LIC_FILES_CHKSUM in file qt-x11-free_3.3.7.bb
--- meta/recipes-qt/qt3/qt-x11-free-common.inc | 91 +++++++++++++++++++++ meta/recipes-qt/qt3/qt-x11-free-native_3.3.5.bb | 65 +++++++++++++++ meta/recipes-qt/qt3/qt-x11-free/configure.patch | 51 ++++++++++++ meta/recipes-qt/qt3/qt-x11-free/gcc4_1-HACK.patch | 28 +++++++ meta/recipes-qt/qt3/qt-x11-free/no-examples.patch | 16 ++++ meta/recipes-qt/qt3/qt-x11-free_3.3.6.bb | 13 +++ meta/recipes-qt/qt3/qt-x11-free_3.3.7.bb | 16 ++++ 7 files changed, 280 insertions(+), 0 deletions(-) create mode 100644 meta/recipes-qt/qt3/qt-x11-free-common.inc create mode 100644 meta/recipes-qt/qt3/qt-x11-free-native_3.3.5.bb create mode 100644 meta/recipes-qt/qt3/qt-x11-free/configure.patch create mode 100644 meta/recipes-qt/qt3/qt-x11-free/gcc4_1-HACK.patch create mode 100644 meta/recipes-qt/qt3/qt-x11-free/no-examples.patch create mode 100644 meta/recipes-qt/qt3/qt-x11-free_3.3.6.bb create mode 100644 meta/recipes-qt/qt3/qt-x11-free_3.3.7.bb
meta/recipes-qt/qt3/qt-x11-free-common.inc new file +91 -0
@@ -0,0 +1,91 @@ +DESCRIPTION = "Qt/X11 Version ${PV} is a full fledged cross-platform application framework" +SECTION = "x11/libs" +PRIORITY = "optional" +LICENSE = "GPL QPL" +HOMEPAGE = "http://www.trolltech.com" + +S = "${WORKDIR}/qt-x11-free-${PV}" + +inherit qmake_base qt3x11 + +export QTDIR = "${S}" +STAGING_QT_DIR = "${STAGING_DIR_HOST}/qt3" +ARCH_i686 = "x86" +EXTRA_OEMAKE = "-e" + +QT_CONFIG_FLAGS = "-release -shared -qt-zlib -no-nas-sound -no-sm -qt-libpng -no-gif -no-xinerama \ + -no-tablet -no-xkb -no-dlopen-opengl -no-nis -no-cups -thread -verbose" + +EXTRA_ENV = 'QMAKE="${STAGING_BINDIR_NATIVE}/qmake -after INCPATH+=${STAGING_INCDIR} \ + INCPATH+=${STAGING_INCDIR}/freetype2 LIBS+=-L${STAGING_LIBDIR}" \ + QMAKESPEC="${QMAKESPEC}" LINK="${CXX} -Wl,-rpath-link,${STAGING_LIBDIR}" \ + AR="${TARGET_PREFIX}ar cqs" \ + MOC="${STAGING_BINDIR_NATIVE}/moc3" UIC="${STAGING_BINDIR_NATIVE}/uic3" MAKE="make -e"' + +do_configure() { + echo "yes" | ./configure -prefix ${prefix} ${QT_CONFIG_FLAGS} -no-fast \ + -L${STAGING_LIBDIR} -I${STAGING_INCDIR} -I${STAGING_INCDIR}/freetype2 -I${STAGING_INCDIR}/mysql + + # force regenerate + rm -f src/qtmain.pro + cat Makefile >makefile + find . -name "Makefile"|xargs rm -f + (cd src && qmake -spec ${QMAKESPEC} ) + (cd plugins/src && qmake -spec ${QMAKESPEC} ) + (cd tools && qmake -spec ${QMAKESPEC} ) + (cd tools/qvfb && qmake -spec ${QMAKESPEC} ) +} + +do_compile() { + unset CFLAGS + unset CXXFLAGS + install -m 0755 ${STAGING_BINDIR_NATIVE}/moc3 ${S}/bin/moc + install -m 0755 ${STAGING_BINDIR_NATIVE}/uic3 ${S}/bin/uic + + oe_runmake -C src ${EXTRA_ENV} + oe_runmake -C plugins/src ${EXTRA_ENV} + oe_runmake -C tools ${EXTRA_ENV} + oe_runmake -C tools/qvfb ${EXTRA_ENV} +} + +do_install_prepend() { + install -d ${STAGING_QT_DIR}/bin + ln -sf ${STAGING_BINDIR_NATIVE}/moc3 ${STAGING_QT_DIR}/bin/moc + ln -sf ${STAGING_BINDIR_NATIVE}/uic3 ${STAGING_QT_DIR}/bin/uic + ln -sf ${STAGING_BINDIR_NATIVE}/qmake ${STAGING_QT_DIR}/bin/qmake + install -d ${STAGING_QT_DIR}/lib + oe_soinstall lib/libqt-mt.so.${PV} ${STAGING_QT_DIR}/lib + install -d ${STAGING_QT_DIR}/include/private + for f in include/*.h + do + install -m 0644 $f ${STAGING_QT_DIR}/include/ + done + for f in include/private/*.h + do + install -m 0644 $f ${STAGING_QT_DIR}/include/private + done + for f in lib/*.prl + do + install -m 0644 $f ${STAGING_QT_DIR}/lib + done +} + +do_install() { + install -d ${D}${libdir}/ + oe_soinstall lib/libqt-mt.so.${PV} ${D}${libdir}/ + install -d ${D}${bindir}/ + install -m 0755 bin/designer bin/assistant tools/qvfb/qvfb bin/qtconfig ${D}${bindir} + install -d ${D}${prefix}/plugins/ + cp -pPR plugins/imageformats plugins/sqldrivers plugins/designer ${D}${prefix}/plugins/ +} + +PACKAGES =+ "qt-x11-plugins-imageformats qt-x11-plugins-sqldrivers qt-x11-plugins-designer \ + qt-x11-designer qt-x11-assistant qt-x11-qvfb qt-x11-qtconfig" +FILES_qt-x11-plugins-imageformats = "${prefix}/plugins/imageformats/*.so" +FILES_qt-x11-plugins-sqldrivers = "${prefix}/plugins/sqldrivers/*.so" +FILES_qt-x11-plugins-designer = "${prefix}/plugins/designer/*.so" +FILES_qt-x11-designer = "${bindir}/designer" +FILES_qt-x11-assistant = "${bindir}/assistant" +FILES_qt-x11-qvfb = "${bindir}/qvfb" +FILES_qt-x11-qtconfig = "${bindir}/qtconfig" +FILES_qt-x11-dbg += "${prefix}/plugins/*/.debug ${D}/qt-x11-plugins-debug"
meta/recipes-qt/qt3/qt-x11-free-native_3.3.5.bb new file +65 -0
65 lines not on this page · raw message
meta/recipes-qt/qt3/qt-x11-free/configure.patch new file +51 -0
51 lines not on this page · raw message
meta/recipes-qt/qt3/qt-x11-free/gcc4_1-HACK.patch new file +28 -0
@@ -0,0 +1,28 @@ + +# +# Patch managed by http://www.holgerschurig.de/patcher.html +# + +--- qt-x11-free-3.3.6/src/tools/qstring.h~gcc4_1.patch ++++ qt-x11-free-3.3.6/src/tools/qstring.h +@@ -60,7 +60,7 @@ + #endif + #endif + +- ++#define Q_NO_PACKED_REFERENCE + /***************************************************************************** + QString class + *****************************************************************************/ +@@ -194,9 +194,9 @@ + char latin1() const { return ucs > 0xff ? 0 : (char) ucs; } + ushort unicode() const { return ucs; } + #ifdef Q_NO_PACKED_REFERENCE +- ushort &unicode() { return *(&ucs); } ++ ushort &unicode() { return *((ushort*)&ucs); } + #else +- ushort &unicode() { return ucs; } ++ ushort &unicode() { return (ushort)ucs; } + #endif + #ifndef QT_NO_CAST_ASCII + // like all ifdef'd code this is undocumented
meta/recipes-qt/qt3/qt-x11-free/no-examples.patch new file +16 -0
@@ -0,0 +1,16 @@ + +# +# Patch managed by http://www.mn-logistik.de/unsupported/pxa250/patcher +# + +--- qt-embedded-free-3.3.2/Makefile~no-examples 2003-08-11 16:37:25.000000000 +0200 ++++ qt-embedded-free-3.3.2/Makefile 2004-05-11 15:53:53.000000000 +0200 +@@ -11,7 +11,7 @@ + install: FORCE + @$(MAKE) qt.install + +-all: symlinks src-qmake src-moc sub-src sub-tools sub-tutorial sub-examples ++all: symlinks src-qmake src-moc sub-src sub-tools + @echo + @echo "The Qt library is now built in ./lib" + @echo "The Qt examples are built in the directories in ./examples"
meta/recipes-qt/qt3/qt-x11-free_3.3.6.bb new file +13 -0
@@ -0,0 +1,13 @@ +DEPENDS = "uicmoc3-native freetype virtual/libx11 libxft libxext libxrender libxrandr libxcursor mysql virtual/libgl" +PROVIDES = "qt3x11" +PR = "r3" + +SRC_URI = "ftp://ftp.trolltech.com/qt/source/qt-x11-free-${PV}.tar.bz2 \ + file://configure.patch \ + file://no-examples.patch \ + file://gcc4_1-HACK.patch" + +require qt-x11-free-common.inc + +SRC_URI[md5sum] = "dc1384c03ac08af21f6fefab32d982cf" +SRC_URI[sha256sum] = "04f12083f6a6f7a8fd4d34a6c1efd37db76a67580c424f4fb7b7c43c0565e6ae"
meta/recipes-qt/qt3/qt-x11-free_3.3.7.bb new file +16 -0
@@ -0,0 +1,16 @@ +DEPENDS = "uicmoc3-native freetype virtual/libx11 libxmu libxft libxext libxrender libxrandr libxcursor virtual/libgl" +PROVIDES = "qt3x11" +PR = "r4" + +LIC_FILES_CHKSUM = "file://LICENSE.GPL;md5=b07b0d5ac6b1822effe47173a1744433 \ + file://LICENSE.QPL;md5=b81b6b6fc04ed873adde5aa901c0613b" + +SRC_URI = "ftp://ftp.trolltech.com/qt/source/qt-x11-free-${PV}.tar.bz2 \ + file://configure.patch \ + file://no-examples.patch \ + file://gcc4_1-HACK.patch" + +require qt-x11-free-common.inc + +SRC_URI[md5sum] = "655e21cf6a7e66daf8ec6ceda81aae1e" +SRC_URI[sha256sum] = "48c05b501029f0640db665fbc7f981a0efbf69ad3cf87a43c5eea4872f4f7ba1"
Signature · 1 line
1.7.0.4
PATCH 2/2 qt3: Add two class(qt3e.bbclass and qt3x11.bbclass) files into meta/classess/
In reply to Xiaofeng YanFrom: Xiaofeng Yan <[email protected]>
Two files from OE are needed to compile qt3
--- meta/classes/qt3e.bbclass | 11 +++++++++++ meta/classes/qt3x11.bbclass | 15 +++++++++++++++ 2 files changed, 26 insertions(+), 0 deletions(-) create mode 100644 meta/classes/qt3e.bbclass create mode 100644 meta/classes/qt3x11.bbclass
meta/classes/qt3e.bbclass new file +11 -0
@@ -0,0 +1,11 @@ +# +# override variables set by qmake_base to compile Qt/X11 apps +# +export QTDIR="${STAGING_DIR_HOST}/qte3" +export QTEDIR="${STAGING_DIR_HOST}/qte3" +export OE_QMAKE_UIC="${STAGING_BINDIR_NATIVE}/uic3" +export OE_QMAKE_MOC="${STAGING_BINDIR_NATIVE}/moc3" +export OE_QMAKE_CXXFLAGS="${CXXFLAGS} " +export OE_QMAKE_INCDIR_QT="${STAGING_INCDIR}/qte3/include" +export OE_QMAKE_LIBDIR_QT="${STAGING_LIBDIR}/qte3/lib" +export OE_QMAKE_LIBS_QT="qte"
meta/classes/qt3x11.bbclass new file +15 -0
@@ -0,0 +1,15 @@ +DEPENDS_prepend = "${@["qt3x11 ", ""][(bb.data.getVar('PN', d, 1) == 'qt-x11-free')]}" +EXTRA_QMAKEVARS_POST += "CONFIG+=thread" +# +# override variables set by qmake_base to compile Qt/X11 apps +# +export QTDIR = "${STAGING_DIR_HOST}/qt3" +export OE_QMAKE_UIC = "${STAGING_BINDIR_NATIVE}/uic3" +export OE_QMAKE_MOC = "${STAGING_BINDIR_NATIVE}/moc3" +export OE_QMAKE_CXXFLAGS = "${CXXFLAGS} -DQT_NO_XIM" +export OE_QMAKE_INCDIR_QT = "${QTDIR}/include" +export OE_QMAKE_LIBDIR_QT = "${QTDIR}/lib" +export OE_QMAKE_LIBS_QT = "qt" +export OE_QMAKE_LIBS_X11 = "-lXext -lX11 -lm" +export OE_QMAKE_LIBS_OPENGL = "-lGLU -lGL -lXmu" +export OE_QMAKE_LIBS_OPENGL_QT = "-lGL -lXmu"
Signature · 1 line
1.7.0.4
Quoted 3 lines · On Tuesday 01 March 2011 07:12:09 Xiaofeng Yan wrote:
From: Xiaofeng Yan <[email protected]>
Packages qt3 from "OE" is needed by LSB Test Suite. So I add it to Poky.
If we're adding this solely for LSB compliance, do we need the "embedded" portions of Qt3 (i.e. qt3e.bbclass)? AFAICT the LSB documentation doesn't mention it explicitly and if we don't add it it's one less thing we have to support (I'm convinced it's not widely used in any case).
Cheers,
Paul
Op 1 mrt 2011, om 11:23 heeft Paul Eggleton het volgende geschreven:
Quoted 9 lines · On Tuesday 01 March 2011 07:12:09 Xiaofeng Yan wrote:
Quoted 3 lines
From: Xiaofeng Yan <[email protected]>
Packages qt3 from "OE" is needed by LSB Test Suite. So I add it to Poky.
If we're adding this solely for LSB compliance, do we need the "embedded" portions of Qt3 (i.e. qt3e.bbclass)? AFAICT the LSB documentation doesn't mention it explicitly and if we don't add it it's one less thing we have to support (I'm convinced it's not widely used in any case).
And since there was never a qtopia for qt3 I highly doubt anyone is using qt3/e.
regards,
Koen
Quoted 2 lines · On Tuesday 01 March 2011 10:33:08 you wrote:
And since there was never a qtopia for qt3 I highly doubt anyone is using qt3/e.
Well, you never know what people are doing behind closed doors. There was also once a version of SystemRescueCD that was using the then-current version of QtParted with Qt/Embedded 3.x to avoid including X.
For our purposes though it's only for LSB at this stage, so embedded appears to be superfluous.
Cheers,
Paul
Quoted 10 lines · Paul Eggleton
Quoted 2 lines · On Tuesday 01 March 2011 10:33:08 you wrote:
And since there was never a qtopia for qt3 I highly doubt anyone is using qt3/e.
Well, you never know what people are doing behind closed doors. There was also once a version of SystemRescueCD that was using the then-current version of QtParted with Qt/Embedded 3.x to avoid including X.
For our purposes though it's only for LSB at this stage, so embedded appears to be superfluous.
Quoted 7 lines
Cheers,
Paul
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky
Hi All,
Qt3 could be superfluous because qt4 can include qt3 functions. But the most important is that our lsb-image must meet LSB's requirement. Otherwise our yocto can't be permitted to use the LSB Certified trademark. So qt3 is just for passing LSB test on lsb-image.
Thanks
Yan
I think we should be sure to clearly label the Qt3 as only provided for LSB compatibility in the recipe, that way if someone tries to use it, they can understand why it was added/maintained.
--Mark
Quoted 31 lines · Xiaofeng Yan
Quoted 10 lines · Paul Eggleton
Quoted 2 lines · On Tuesday 01 March 2011 10:33:08 you wrote:
And since there was never a qtopia for qt3 I highly doubt anyone is using qt3/e.
Well, you never know what people are doing behind closed doors. There was also once a version of SystemRescueCD that was using the then-current version of QtParted with Qt/Embedded 3.x to avoid including X.
For our purposes though it's only for LSB at this stage, so embedded appears to be superfluous.
Quoted 7 lines
Cheers,
Paul
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/pokyHi All,
Qt3 could be superfluous because qt4 can include qt3 functions. But the most important is that our lsb-image must meet LSB's requirement. Otherwise our yocto can't be permitted to use the LSB Certified trademark. So qt3 is just for passing LSB test on lsb-image.
Thanks
Yan
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky
Quoted 4 lines · Mark Hatle
I think we should be sure to clearly label the Qt3 as only provided for LSB compatibility in the recipe, that way if someone tries to use it, they can understand why it was added/maintained.
Mark,
I thought we talked about this before, I did not think we where going for 100% compliant in core yocto, and if needed, this can be part of the WR layer in order to complete compliance. I don't think we want to carry around a recipe that is purely for compatibility at that level.
Sau!
Quoted 39 lines
--Mark
Quoted 25 lines · Xiaofeng Yan
Quoted 10 lines · Paul Eggleton
Quoted 2 lines · On Tuesday 01 March 2011 10:33:08 you wrote:
And since there was never a qtopia for qt3 I highly doubt anyone is using qt3/e.
Well, you never know what people are doing behind closed doors. There was also once a version of SystemRescueCD that was using the then-current version of QtParted with Qt/Embedded 3.x to avoid including X.
For our purposes though it's only for LSB at this stage, so embedded appears to be superfluous.
Quoted 7 lines
Cheers,
Paul
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/pokyHi All,
Qt3 could be superfluous because qt4 can include qt3 functions. But the most important is that our lsb-image must meet LSB's requirement. Otherwise our yocto can't be permitted to use the LSB Certified trademark. So qt3 is just for passing LSB test on lsb-image.
Quoted 6 lines
Thanks
Yan
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky
Quoted 11 lines · Saul Wold
Quoted 4 lines · Mark Hatle
I think we should be sure to clearly label the Qt3 as only provided for LSB compatibility in the recipe, that way if someone tries to use it, they can understand why it was added/maintained.
Mark,
I thought we talked about this before, I did not think we where going for 100% compliant in core yocto, and if needed, this can be part of the WR layer in order to complete compliance. I don't think we want to carry around a recipe that is purely for compatibility at that level.
What I remember is we were not sure it would go into 1.0. And we were not yet sure what we wanted to do with a QT compatibility library, if it would ever go into "meta", another layer, or...
I think LSB compliance makes sense in the meta layer because of the new "poky-lsb" distro. It shouldn't hurt to carry this forward and maintain it for compatibility sake as part of the poky-lsb work. (But I won't complain if it doesn't make it into 1.0, and we delay a final decision on if it goes in at all until later -- I just want to make sure the code isn't lost though...)
--Mark
Quoted 42 lines
Sau!
Quoted 39 lines
--Mark
Quoted 25 lines · Xiaofeng Yan
Quoted 10 lines · Paul Eggleton
Quoted 2 lines · On Tuesday 01 March 2011 10:33:08 you wrote:
And since there was never a qtopia for qt3 I highly doubt anyone is using qt3/e.
Well, you never know what people are doing behind closed doors. There was also once a version of SystemRescueCD that was using the then-current version of QtParted with Qt/Embedded 3.x to avoid including X.
For our purposes though it's only for LSB at this stage, so embedded appears to be superfluous.
Quoted 7 lines
Cheers,
Paul
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/pokyHi All,
Qt3 could be superfluous because qt4 can include qt3 functions. But the most important is that our lsb-image must meet LSB's requirement. Otherwise our yocto can't be permitted to use the LSB Certified trademark. So qt3 is just for passing LSB test on lsb-image.
Quoted 6 lines
Thanks
Yan
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky
Quoted 17 lines · Mark Hatle
Quoted 11 lines · Saul Wold
Quoted 4 lines · Mark Hatle
I think we should be sure to clearly label the Qt3 as only provided for LSB compatibility in the recipe, that way if someone tries to use it, they can understand why it was added/maintained.
Mark,
I thought we talked about this before, I did not think we where going for 100% compliant in core yocto, and if needed, this can be part of the WR layer in order to complete compliance. I don't think we want to carry around a recipe that is purely for compatibility at that level.
What I remember is we were not sure it would go into 1.0. And we were not yet sure what we wanted to do with a QT compatibility library, if it would ever go into "meta", another layer, or...
Quoted 6 lines
I think LSB compliance makes sense in the meta layer because of the new "poky-lsb" distro. It shouldn't hurt to carry this forward and maintain it for compatibility sake as part of the poky-lsb work. (But I won't complain if it doesn't make it into 1.0, and we delay a final decision on if it goes in at all until later -- I just want to make sure the code isn't lost though...)
I would like to hold off on this change at this point.
We can visit later.
Thanks
Sau!
Quoted 45 lines
--Mark
Quoted 42 lines
Sau!
Quoted 39 lines
--Mark
Quoted 25 lines · Xiaofeng Yan
Quoted 10 lines · Paul Eggleton
Quoted 2 lines · On Tuesday 01 March 2011 10:33:08 you wrote:
And since there was never a qtopia for qt3 I highly doubt anyone is using qt3/e.
Well, you never know what people are doing behind closed doors. There was also once a version of SystemRescueCD that was using the then-current version of QtParted with Qt/Embedded 3.x to avoid including X.
For our purposes though it's only for LSB at this stage, so embedded appears to be superfluous.
Quoted 7 lines
Cheers,
Paul
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/pokyHi All,
Qt3 could be superfluous because qt4 can include qt3 functions. But the most important is that our lsb-image must meet LSB's requirement. Otherwise our yocto can't be permitted to use the LSB Certified trademark. So qt3 is just for passing LSB test on lsb-image.
Quoted 6 lines
Thanks
Yan
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky