[Buildroot] [Bug 6854] New: Update to Qt 5.2.1

[Buildroot] [Bug 6854] New: Update to Qt 5.2.1

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6854

           Summary: Update to Qt 5.2.1
           Product: buildroot
           Version: 2014.02
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: syntheticpp at gmx.net
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Also adds a patch which missed 5.2.1 and is needed for cmake projects for
non-opengl systems.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 6854] Update to Qt 5.2.1

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6854

--- Comment #1 from syntheticpp at gmx.net 2014-02-06 13:21:28 UTC ---
Created attachment 5222
  --> https://bugs.busybox.net/attachment.cgi?id=5222
Update to 5.2.1

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 6854] Update to Qt 5.2.1

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6854

--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2014-02-06 13:23:43 UTC ---
Thanks a lot!

However, could you submit patches to the mailing list? See the contribution
process detailed at
http://buildroot.org/downloads/manual/manual.html#_contributing_to_buildroot.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 6854] Update to Qt 5.2.1

[Vicente Olivert Riera]

On 02/06/2014 01:23 PM, bugzilla at busybox.net wrote:
> https://bugs.busybox.net/show_bug.cgi?id=6854
>
> --- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2014-02-06 13:23:43 UTC ---
> Thanks a lot!
>
> However, could you submit patches to the mailing list? See the contribution
> process detailed at
> http://buildroot.org/downloads/manual/manual.html#_contributing_to_buildroot.
>

I was testing Qt-5.2.1. I agree with the removal of these patches:

qt5base-0001-Fix-build-MIPS64-bigendian.patch
qt5base-0007-detect-posix_fallocate-at-configure-time.patch

However, I'm having some problem when trying to build this new version:

cd scanner/ && ( test -e Makefile || 
/home/ldap/vriera/work/mips-buildroots/mips64_be_sf_n64/output/host/usr/bin/qmake 
/home/ldap/vriera/work/mips-buildroots/mips64_be_sf_n64/output/build/qt5connectivity-5.2.1/examples/bluetooth/scanner/scanner.pro 
-o Makefile ) && /usr/bin/make -f Makefile
Project ERROR: Unknown module(s) in QT: quick
make[3]: *** [sub-scanner-make_first] Error 3
make[3]: *** Waiting for unfinished jobs....

The package that fails in that log snipet is "qt5connectivity".

Here is the defconfig:

BR2_mips64=y
BR2_MIPS_NABI64=y
BR2_TOOLCHAIN_BUILDROOT_UCLIBC=y
BR2_TOOLCHAIN_BUILDROOT_LARGEFILE=y
BR2_TOOLCHAIN_BUILDROOT_INET_IPV6=y
BR2_TOOLCHAIN_BUILDROOT_INET_RPC=y
BR2_TOOLCHAIN_BUILDROOT_LOCALE=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_PACKAGE_QT5=y
BR2_PACKAGE_QT5BASE_LICENSE_APPROVED=y
BR2_PACKAGE_QT5BASE_EXAMPLES=y
BR2_PACKAGE_QT5BASE_SQL=y
BR2_PACKAGE_QT5BASE_MYSQL=y
BR2_PACKAGE_QT5BASE_SQLITE_QT=y
BR2_PACKAGE_QT5BASE_TEST=y
BR2_PACKAGE_QT5BASE_LINUXFB=y
BR2_PACKAGE_QT5BASE_DIRECTFB=y
BR2_PACKAGE_QT5BASE_XCB=y
BR2_PACKAGE_QT5BASE_PRINTSUPPORT=y
BR2_PACKAGE_QT5BASE_FONTCONFIG=y
BR2_PACKAGE_QT5BASE_GIF=y
BR2_PACKAGE_QT5BASE_JPEG=y
BR2_PACKAGE_QT5BASE_PNG=y
BR2_PACKAGE_QT5BASE_ICU=y
BR2_PACKAGE_QT5BASE_TSLIB=y
BR2_PACKAGE_QT5CONNECTIVITY=y
BR2_PACKAGE_QT5IMAGEFORMATS=y
BR2_PACKAGE_QT5SENSORS=y
BR2_PACKAGE_QT5SERIALPORT=y
BR2_PACKAGE_QT5SVG=y
BR2_PACKAGE_QT5X11EXTRAS=y
BR2_PACKAGE_QT5XMLPATTERNS=y
BR2_PACKAGE_XORG7=y
# BR2_TARGET_ROOTFS_TAR is not set

-- 
Vincent

[Buildroot] [Bug 6854] Update to Qt 5.2.1

[Peter Kuemmel]

> Von: "Vicente Olivert Riera" <Vincent.Riera@imgtec.com>
> 
> I was testing Qt-5.2.1. I agree with the removal of these patches:
> 
> qt5base-0001-Fix-build-MIPS64-bigendian.patch
> qt5base-0007-detect-posix_fallocate-at-configure-time.patch

These patches were merged into Qt 5.2.1.

> 
> -- 
> Vincent
> 

[Buildroot] [Bug 6854] Update to Qt 5.2.1

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6854

--- Comment #3 from syntheticpp at gmx.net 2014-02-06 13:50:50 UTC ---
Ah, yes.

But the ml has way to much traffic for me.
Ever thought about using gerrit?

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 6854] Update to Qt 5.2.1

[Vicente Olivert Riera]

On 02/06/2014 01:46 PM, Peter Kuemmel wrote:
>
>> Von: "Vicente Olivert Riera" <Vincent.Riera@imgtec.com>
>>
>> I was testing Qt-5.2.1. I agree with the removal of these patches:
>>
>> qt5base-0001-Fix-build-MIPS64-bigendian.patch
>> qt5base-0007-detect-posix_fallocate-at-configure-time.patch
>
> These patches were merged into Qt 5.2.1.
>
>>
>> --
>> Vincent
>>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>

I know, the qt5base-0001-Fix-build-MIPS64-bigendian.patch is mine. I 
said that I *agree* with the removal of these patches :)

However, you missed the removal of this one:

qt5webkit/qt5webkit-0002-Fix-QtWebKit-build-on-ARM-softfp.patch

-- 
Vincent

[Buildroot] [Bug 6854] Update to Qt 5.2.1

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6854

--- Comment #4 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2014-02-06 15:36:35 UTC ---
Yes, I believe we talked about Gerrit in the past, but the majority, if not all
of the core developers as well as the maintainer, very much prefer a mailing
list based review, rather than having to use a web-based tool to do reviews.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 6854] Update to Qt 5.2.1

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6854

--- Comment #5 from syntheticpp at gmx.net 2014-02-06 15:53:01 UTC ---
Yes, a web interface is a draw-back.
Maybe it is worth to create a buildroot-user ml.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 6854] Update to Qt 5.2.1

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6854

syntheticpp at gmx.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 6854] Update to Qt 5.2.1

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6854

--- Comment #6 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2014-02-06 16:14:30 UTC ---
We discussed about creating a user-oriented mailing list at one of the latest
Buildroot meeting. See
http://elinux.org/Buildroot:DeveloperDaysELCE2013#Community_organization.

The conclusion was: " We don't see a good way to split the lists at all,
because a basic user is very quickly a basic developer and forcing them to see
the patches is probably good."

Moreover, we are talking about submitting patches here, so even if a buildroot
user mailing list existed, you would have had to send your patches to the
developer mailing list.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.