From: "Matthias Klein" <matthias.klein@optimeas.de>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] Porting rule file from qt4 to qt5
Date: Wed, 04 Nov 2015 10:49:05 +0000 [thread overview]
Message-ID: <emb6b20772-fea3-4f31-a627-bb618b32eb3d@nb-mak> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1243 bytes --]
Hello,
I tried to move from qt4 to qt5. Building the library was no problem,
but I don't get a qt project inside the local_src to compile.
Basically the rule file looks like what I get from "ptxdist newpackage
src-qmake-prog".
#
----------------------------------------------------------------------------
# Prepare
#
----------------------------------------------------------------------------
#SCPICMD_CONF_ENV := $(CROSS_ENV)
#
# qmake
#
SCPICMD_CONF_TOOL := qmake
SCPICMD_CONF_OPT := $(CROSS_QMAKE_OPT) PREFIX=/usr
The prepare steps runs, but the resulting Makefile shows the wrong qmake
command:
# Command: /usr/lib/x86_64-linux-gnu/qt5/bin/qmake CONFIG+=silent
PREFIX=/usr -o Makefile ../../../local_src/scpicmd/world.pro
Instead of something like this (at the old qt4 call):
# Command:
/home/user/bsp/platform-tx53-3.12-rt/sysroot-cross/bin/qmake-cross
CONFIG+=silent PREFIX=/usr -o Makefile
../../../local_src/scpicmd/world.pro
ptxdist calls qmake from the host instead of using the local qmake
inside the bsp.
Does anyone have a tip what wrong in my rule file or what I should
change?
Or is a local_src qt5 project not supported at the moment?
Best regards,
Matthias
[-- Attachment #1.2: Type: text/html, Size: 2759 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2015-11-04 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 10:49 Matthias Klein [this message]
2015-11-06 11:25 ` Michael Olbrich
2015-11-09 8:15 ` Matthias Klein
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=emb6b20772-fea3-4f31-a627-bb618b32eb3d@nb-mak \
--to=matthias.klein@optimeas.de \
--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