mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Dennis Miller <dennis.z.miller@outlook.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Qt 5.4.2: dev-package?
Date: Fri, 17 Jul 2015 12:48:25 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150717T141238-722@post.gmane.org> (raw)

Hi,

with PTXdist 2015.07.0 and Qt 5.4.2 there are steps in the qt5.install.post
step that setup qmake (+moc/uic/rcc/...) so I can cross-compile qmake projects.

I've found a few issues and please correct me if I'm wrong:
(I) "ptxdist newpackage src-qmake-prog" still references QT4 and not QT5 -
Fix it or leave it? At least a reminder would be nice ...

(II) If I try to work with QT5 as a developer package, I'm missing the
cross-compile tools I mentioned earlier, right?
I would love to have an archive of $(PTXDIST_SYSROOT_CROSS)/bin/qt5 and a
qt5.devpkg.post-install (?) or similar step so I could restore sysroot-cross. 
This would be great as a fully featured build takes hours on my i7 ...
Can this be done with the PTXdist as-is or would this be a new feature?

(III) As I said, qmake ends up in $(PTXDIST_SYSROOT_CROSS)/bin/qt5 - 
This is good as it separates qt5 stuff from everything else, but this is
also bad as $(PTXDIST_SYSROOT_CROSS)/bin/qt5 is not added to the $PATH.
Since $(PTXDIST_SYSROOT_CROSS)/bin is in $PATH the last step in
qt5.install.post should be adding some symbolic links - Otherwise building a
BSP with a new package (see (I)) actually fails building that package.
(Because qmake could not be found or the wrong qmake is used)


Thanks in advance.
Sincerely,

Dennis


-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2015-07-17 10:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17 12:48 Dennis Miller [this message]
2015-07-29  5:40 ` Dennis Miller
2015-07-29  6:10   ` Alexander Dahl
2015-08-11  5:24 ` Dennis Miller
2015-08-11 14:31   ` Robert Schwebel
2015-09-03  7:35     ` Dennis Miller
2015-09-04  5:39       ` Robert Schwebel

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=loom.20150717T141238-722@post.gmane.org \
    --to=dennis.z.miller@outlook.com \
    --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