Could qt4.8 build on mips 64 bits platform?
Hi All,
Could qt4.8 build on mips 64 bits platform?
I searched qt-project.org and no such related information.
And then grep the source codethat no such mips64 keyword in file qmake.conf under directory mkspecs. In contrast there are mips32 related flags in mkspecs/qws/linux-mips-g++/qmake.conf.
Does that mean we still can't build qt 4.8 on mips64?
Thanks a lot.
Signature · 2 lines
Regards, Neil | Kai Kang
Quoted 8 lines · On Tuesday 25 June 2013 17:32:48 Kang Kai wrote:
Could qt4.8 build on mips 64 bits platform?
I searched qt-project.org and no such related information. And then grep the source codethat no such mips64 keyword in file qmake.conf under directory mkspecs. In contrast there are mips32 related flags in
mkspecs/qws/linux-mips-g++/qmake.conf.Does that mean we still can't build qt 4.8 on mips64?
I don't have any specific knowledge here; I'd suggest trying it. If additional patches are needed the best thing would be to try and get those merged upstream.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 8 lines · Paul Eggleton
Quoted 7 lines · On Tuesday 25 June 2013 17:32:48 Kang Kai wrote:
Could qt4.8 build on mips 64 bits platform?
I searched qt-project.org and no such related information. And then grep the source codethat no such mips64 keyword in file qmake.conf under directory mkspecs. In contrast there are mips32 related flags in
mkspecs/qws/linux-mips-g++/qmake.conf.
Quoted 4 lines
Quoted 1 line
Does that mean we still can't build qt 4.8 on mips64?
I don't have any specific knowledge here; I'd suggest trying it. If additional patches are needed the best thing would be to try and get those merged upstream.
Thanks a lot. I'll try to build it on mips 64.
Regards,
Kai
Quoted 4 lines
Cheers,
Paul
Signature · 2 lines
Regards, Neil | Kai Kang
Quoted 9 lines · Kang Kai
Quoted 8 lines · Paul Eggleton
Quoted 7 lines · On Tuesday 25 June 2013 17:32:48 Kang Kai wrote:
Could qt4.8 build on mips 64 bits platform?
I searched qt-project.org and no such related information. And then grep the source codethat no such mips64 keyword in file qmake.conf under directory mkspecs. In contrast there are mips32 related flags in
mkspecs/qws/linux-mips-g++/qmake.conf.
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Does that mean we still can't build qt 4.8 on mips64?
I don't have any specific knowledge here; I'd suggest trying it. If additional
patches are needed the best thing would be to try and get those merged upstream.Thanks a lot. I'll try to build it on mips 64.
The background here is that we encountered many painful build problems with qt-4.7 on mips64 in oe-core-1.2. We tried to fix them initially but investigations from 6 months ago indicated that the qt upstream did not support mips64. Kai will dig into the current situation but I expect that little will have changed.
We ended up with horrid bbapends such as:
---
#Valid for all arches except mips64 with 64bit userspace
# mips64 with n32 has host: mips64-wrs-linux-gnun32 # mips64 with n64 has host: mips64-wrsmllib64-linux # qemumips has host: mips-wrs-linux # qemumips-64 has host: mips64-wrs-linux COMPATIBLE_HOST = '((x86_64.*|i.86.*|powerpc.*|arm.*|mips-.*|mips32.*)-linux|mips64.*-linux-gnun32)' ---
so we'll likely need a clue on how to declare a host as incompatible or introduce an INCOMPATIBLE_HOST variable.
// Randy
Quoted 10 lines
Regards,
KaiQuoted 4 lines
Cheers,
Paul
Signature · 2 lines
# Randy MacLeod. SMTS, Linux, Wind River Direct: 613.963.1350
Quoted 11 lines · Randy MacLeod
We ended up with horrid bbapends such as:
---
#Valid for all arches except mips64 with 64bit userspace# mips64 with n32 has host: mips64-wrs-linux-gnun32 # mips64 with n64 has host: mips64-wrsmllib64-linux # qemumips has host: mips-wrs-linux # qemumips-64 has host: mips64-wrs-linux COMPATIBLE_HOST = '((x86_64.*|i.86.*|powerpc.*|arm.*|mips-.*|mips32.*)-linux|mips64.*-linux-gnun32)' ---
Quoted 2 lines
so we'll likely need a clue on how to declare a host as incompatible or introduce an
INCOMPATIBLE_HOSTvariable.
I suspect something like this should work:
COMPATIBLE_HOST_mips64 = ""
Cheers,
Richard
Quoted 12 lines · Richard Purdie
Quoted 11 lines · Randy MacLeod
We ended up with horrid bbapends such as:
---
#Valid for all arches except mips64 with 64bit userspace# mips64 with n32 has host: mips64-wrs-linux-gnun32 # mips64 with n64 has host: mips64-wrsmllib64-linux # qemumips has host: mips-wrs-linux # qemumips-64 has host: mips64-wrs-linux COMPATIBLE_HOST = '((x86_64.*|i.86.*|powerpc.*|arm.*|mips-.*|mips32.*)-linux|mips64.*-linux-gnun32)' ---
Quoted 5 lines
Quoted 2 lines
so we'll likely need a clue on how to declare a host as incompatible or introduce an
INCOMPATIBLE_HOSTvariable.I suspect something like this should work:
COMPATIBLE_HOST_mips64= ""
Thanks.
We still need include such packages on mips64 with 32 bits filesystem. So the following is needed:
COMPATIBLE_HOST_mips64 = "mips64.*-linux-gnun32"
I am little worried that "-gnun32" is a standard name then I'll figure it out.
Regards,
Kai
Quoted 6 lines
Cheers,
Richard
Signature · 2 lines
Regards, Neil | Kai Kang