Problem Specification :

Qt Embedded Version : 4.5.1
PowerPC : FreeScale's MPC 8640 BSP
Cross Compiler used : powerpc-linux-g++
OS : RHEL 5.x

Some problem in the core libraries are coming which are needed by Qt Embedded. Please comment on the below.
The log file is attached for information.

Regards

Digvijay Yadav
BEL ,Bangalore

> Hi Ravi,
>
> We tried QT on PPC with the solution as being provided by you.
> But still we have some issues when we are trying to implement.
> I am attaching the log file for your analysis.
>
> Please put comments/solutions on this error as soon as possible.
>
>
> Digvijay Yadav
> D&E SS/NS
>
>
>
> -------------------------------------------------- Original
>
>
> We tried the below solution provided on both QT-X11 and QT-embedded. We
> are able to configure the QT but during compilation we are getting some
> errors both QT-X11 and embedde. The errors are attached for your
> reference.<br>
> <br>
> Thanks and Regards<br>
> Haish Kumar.B<br>
> <br>
> <a class="moz-txt-link-abbreviated"
> href="mailto:digvijayyadav@bel.co.in">digvijayyadav@bel.co.in</a> wrote:
> <blockquote
> cite="mid:38880.59.163.88.129.1254738706.squirrel@mail.bel.co.in"
> type="cite">
> <pre wrap="">Hi harish,
>
> Please find the clarification as requested for nokia Qt for PPC.
>
>
> Regards
>
> Digvijay Yadav
> D&E SS/NS
>
>
> -------------------------------------------------- Original

>
> Hi Mr.Digvijay,
>
> As discussed FYI,
>
> Below are the answers regarding QtEmbedded Installation on PowerPC
> Arihtiectire queries :
>
> 1) Problem Specification :
>
> Qt Embedded Version : 4.5.1
>
> PowerPC : FreeScale's MPC 8640 BSP
> Cross Compiler used : powerpc-linux-g++
> OS : Fedora Core 10
>
>
> Please find the attached .qmake.cache when the target specific configure
> script is run.
>
> commands used :
>
> ./confiure -embedded powerpc -xplatform qws/linux-ppc-g++
>
> Cross Compiler path for the PowerPC Compiler is set properly.
>
> But when running the Configure is we get the error as qmake cannot execute
> binary files...
>
> Am using the correct command ? we have copied the qmake.conf of the arm
> acitecture and made the necessary changes as
> required for the PowerPC , is there any other additional changes we need
> to do?
>
>
> I suspect that if you are getting the "qmake cannot execute binary files"
> problem when you are cross compiling then
> there may be a problem where you have compiled qmake as a PPC executable
> that is not able to be run on your native
> platform. The first thing we do when you run the configure script is build
> qmake for your native system, so that it
> can be run on the project files in the Qt Source directory. When this is
> completed it will run qmake, and if it is
> unable to then the configuration script will error out.
>
> This could occur for a couple of reasons. I see that in your configure
> script you specify the platform you are
> compiling to, but not the platform your are compiling from. You can make
> this distinction by adding the argument
> "-platfrom

". For example:
>
> ./confiure -embedded powerpc -xplatform qws/linux-ppc-g++ -platform
>
> linux-g++-32
>
> That way you will make sure that you are building native qmake for linux
> x86.
>
> Another problem that this could be is that the qmake binary built be
> configure for some reason isn't make executable.
> You can check this by checking the [qtdir]/bin directory and makeing sure
> the qmake binary is
>
> executable: chmod +x bin/qmake
>
>
>
> 2) The PowerPC h/w is running with both X-Server and Framebuffer.
>
> We know that the PowerPC is not supported by Desktop version of Qt.
>
> Is there any way that I can build PowerPC for the Desktop version of Qt ?
>
>
> Yes, but as you said it is an unsupported platform. You would need to get
> the Qt for X11 package and configure like a
> desktop install, but cross compiled.
>
> Edit your mkspec just like you would for QWS for your platform. Then run
> your configure script like this:
>
> ./configure -xplatform linux-ppc-g++ -platform linux-g++-32
>
> without the -embedded argument.
>
> This may or may not work, as it is no longer tested(read unsupported), and
> may require some hacks to get it working
> again.
>
>
> Thanks and Regards,
> Ravikiran