Fix Qtopia Core 4 compile and installtion and bump to version 4.4.0 snapshot
PATCH 1/1 Fix Qtopia Core 4 compile and installtion and bump to version 4.4.0 snapshot
Hi,
I have attached a patch which fixes compiling (and actually using) Qtopia Core. Qtopia Core is now renamed to Qt Embedded by Trolltech.
I have also bumped the version to the latest snapshot, which has support for AVR32 upstream. I.e. no more need for patches.
As Qtopia Core 4 is now in Buildroot, it is not usable by any Qt applications.
Signature · 9 lines
With kind regards, Hans-Christian Egtvedt, Applications Engineer -------------- next part -------------- A non-text attachment was scrubbed... Name: qtopia4-fix-single-compile-and-update-to-snapshot.patch Type: text/x-patch Size: 15593 bytes Desc: not available Url : http://busybox.net/lists/buildroot/attachments/20080312/c133f41b/attachment-0001.bin
PATCH 1/1 Fix Qtopia Core 4 compile and installtion and bump to version 4.4.0 snapshot
Hi,
How does qmake knows where the cross-compiler is now? Those sed
lines you removed were fixing the path so that makefiles generated by qmake would use the same compiler as buildroot, it would just not work without it in previous versions. Did Trolltech fix the issue?
Regards,
Thiago A. Correa
Quoted 20 lines · Hans-Christian Egtvedt
Hi,
I have attached a patch which fixes compiling (and actually using) Qtopia Core. Qtopia Core is now renamed to Qt Embedded by Trolltech.
I have also bumped the version to the latest snapshot, which has support for AVR32 upstream. I.e. no more need for patches.
As Qtopia Core 4 is now in Buildroot, it is not usable by any Qt applications.
--
With kind regards,
Hans-Christian Egtvedt, Applications Engineer_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot
PATCH 1/1 Fix Qtopia Core 4 compile and installtion and bump to version 4.4.0 snapshot
Quoted 7 lines · Thiago A. Corr?a
Hi,
How does qmake knows where the cross-compiler is now? Those sed
lines you removed were fixing the path so that makefiles generated by qmake would use the same compiler as buildroot, it would just not work without it in previous versions. Did Trolltech fix the issue?
Like all other packages, set the PATH variable correct, which is done by TARGET_CONFIGURE_OPTS.
With the old Makefile for Qtopia Core non of the executables made were executable on target because of weird paths used.
Works for me as it is now, I use the TARGET_CONFIGURE_OPTS and do qmake.
I guess it would be possible to change the installed mkspecs files, but I do not see the need.
Signature · 2 lines
With kind regards, Hans-Christian Egtvedt, Applications Engineer
PATCH 1/1 Fix Qtopia Core 4 compile and installtion and bump to version 4.4.0 snapshot
Quoted 3 lines
Like all other packages, set the PATH variable correct, which is done by
TARGET_CONFIGURE_OPTS.
How exactly? I have a .mk with:
$(MYPACKAGE_DIR)/.configured: $(MYPACKAGE_DIR)/.unpacked
(cd $(MYPACKAGE_DIR); rm -rf Makefile; \
$(QTOPIA4_QMAKE) -spec
qws/linux-$(BR2_PACKAGE_QTOPIA4_EMB_PLATFORM)-g++ \
)
touch $@What should I change?
Quoted 4 lines
With the old
Makefilefor Qtopia Core non of the executables made were executable on target because of weird paths used.Works for me as it is now, I use the
TARGET_CONFIGURE_OPTSand do qmake.
It worked for me as it was then. The executable on the target ran just fine.
Quoted 2 lines
I guess it would be possible to change the installed mkspecs files, but I do not see the need.
AFAIK, makes the life of users of the lib easier, so they can call qmake without having to know buildroot specific issues.
Cheers,
Thiago A. Correa
PATCH 1/1 Fix Qtopia Core 4 compile and installtion and bump to version 4.4.0 snapshot
Quoted 8 lines · Thiago A. Corr?a
Quoted 3 lines
Like all other packages, set the PATH variable correct, which is done by
TARGET_CONFIGURE_OPTS.How exactly? I have a .mk with:
$(MYPACKAGE_DIR)/.configured: $(MYPACKAGE_DIR)/.unpacked(cd $(MYPACKAGE_DIR); rm -rf Makefile; \ $(QTOPIA4_QMAKE) -spec
Change to
$(TARGET_CONFIGURE_OPTS) qmake -spec
Quoted 4 lines
qws/linux-$(BR2_PACKAGE_QTOPIA4_EMB_PLATFORM)-g++ \
)
touch $@Quoted 9 lines
What should I change?
Quoted 4 lines
With the old
Makefilefor Qtopia Core non of the executables made were executable on target because of weird paths used.Works for me as it is now, I use the
TARGET_CONFIGURE_OPTSand do qmake.It worked for me as it was then. The executable on the target ran just fine.
I find that weird, since the libraries had a path issue depending on the directory you built Qtopia Core.
Quoted 6 lines
Quoted 2 lines
I guess it would be possible to change the installed mkspecs files, but I do not see the need.
AFAIK, makes the life of users of the lib easier, so they can call qmake without having to know buildroot specific issues.
Well, when I use the toolchain in Buildroot by placing it first in my PATH it works strait forward; qmake&&make
When you make a package you must look into how Buildroot does this anyway.
Signature · 2 lines
With kind regards, Hans-Christian Egtvedt, Applications Engineer