[Buildroot] [patch] Fix Qtopia Core 4 compile and installtion and bump to version 4.4.0 snapshot

[Buildroot] [patch] Fix Qtopia Core 4 compile and installtion and bump to version 4.4.0 snapshot

[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
-------------- 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 

[Buildroot] [patch] Fix Qtopia Core 4 compile and installtion and bump to version 4.4.0 snapshot

[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?

Regards,
   Thiago A. Correa

On Wed, Mar 12, 2008 at 7:07 AM, Hans-Christian Egtvedt
<hans-christian.egtvedt@atmel.com> wrote:
> 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
>

[Buildroot] [patch] Fix Qtopia Core 4 compile and installtion and bump to version 4.4.0 snapshot

[Hans-Christian Egtvedt]

On Wed, 2008-03-12 at 09:16 -0300, Thiago A. Corr?a wrote:
> 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.

-- 
With kind regards,
Hans-Christian Egtvedt, Applications Engineer

[Buildroot] [patch] Fix Qtopia Core 4 compile and installtion and bump to version 4.4.0 snapshot

[Thiago A. Corrêa]

>
>  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?

>  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.

It worked for me as it was then. The executable on the target ran just fine.

>  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

[Buildroot] [patch] Fix Qtopia Core 4 compile and installtion and bump to version 4.4.0 snapshot

[Hans-Christian Egtvedt]

On Wed, 2008-03-12 at 09:50 -0300, Thiago A. Corr?a wrote:
> >
> >  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

> qws/linux-$(BR2_PACKAGE_QTOPIA4_EMB_PLATFORM)-g++ \
>         )
>         touch $@
> 
> What should I change?
> 
> >  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.
> 
> 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.

> >  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.

-- 
With kind regards,
Hans-Christian Egtvedt, Applications Engineer