From: barhoumi mohtadi <mohtadi_barhoumi@hotmail.fr>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Error during compiling qt projects
Date: Wed, 1 Feb 2012 15:06:18 +0100 [thread overview]
Message-ID: <SNT145-W4579E2682E7F61989F7C7490730@phx.gbl> (raw)
In-Reply-To: <20120201132448.GI32382@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 2479 bytes --]
Hello,
I tested this , running qmake wich is in /sys-cross/bin/qmake for one of the plugins ( i disabled the others):
../../../qmake -o Makefile pluginCorsair.pro
make
but still got the same error : Plugin uses incompatible Qt library
expected build key "i386 linux ptx-g++ full-config" , got "i386 linux g++-4 full-config"
:\
Thanks
Regards
> Date: Wed, 1 Feb 2012 14:24:48 +0100
> From: m.olbrich@pengutronix.de
> To: ptxdist@pengutronix.de
> Subject: Re: [ptxdist] Error during compiling qt projects
>
> On Wed, Feb 01, 2012 at 12:50:08PM +0100, barhoumi mohtadi wrote:
> > I am trying to compile execute a qt proejct (that i have built in my development machine) on the target machine ( the embedded one).
> > The project load normaly dynamic libraries (*.so) to run normally.
> >
> > But , when executing the project on the development machine, the .so are not loaded.
> > in fact , the debugging output indicates ; Plugin uses incompatible Qt Library : expected build key "i386 linux ptx-g++ full-config,' , got "i486 linux g++-4 full-config".
> >
> >
> > I must precise, that i didn't create packages for my project, because , it is kind of impossible due to architecture i've adopted for the application. So i'm executing the application "normally" from the terminal ( xinit path_to_app/appname).
> >
> > For loading the plugins, i use QPluginLoader
> >
> > So , i'm wondering, if there anyway to encounter this problem?? ( differnt buildkeys) . otherwise, is there anyway to compile the sources with the same version of compiler that is on my target machine ( embedded)... ( can i compile them directly there? or can i add the target machine compiler and debugger in the host development machine, so i can compile them there ???))
> >
> > Your help is much appreciated.
>
> If you're using qmake, then just use
> <BSP>/platform-<some-plat>/sysroot-cross/bin/qmake and make sure the
> toolchain for the BSP is in PATH. Then you're project should be built with
> the correct toolchain and qt version.
>
> Michael
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
[-- Attachment #1.2: Type: text/html, Size: 3012 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-02-01 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 11:50 barhoumi mohtadi
2012-02-01 13:24 ` Michael Olbrich
2012-02-01 14:06 ` barhoumi mohtadi [this message]
2012-02-01 14:13 ` [ptxdist] Error during compiling qt projects - Erratum barhoumi mohtadi
2012-02-01 15:13 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SNT145-W4579E2682E7F61989F7C7490730@phx.gbl \
--to=mohtadi_barhoumi@hotmail.fr \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox