From: Ruben Louw <lfxciii@gmail.com>
To: Juergen Beisert <jbe@pengutronix.de>
Subject: Re: [ptxdist] tslib location compiled by PTxdist
Date: Wed, 9 Jan 2013 12:37:46 +0200 [thread overview]
Message-ID: <CAOP6b3hEr=-Rdq4=YwG-BR9TNGk76jfX+KPcX=+5ORk4W53i=Q@mail.gmail.com> (raw)
In-Reply-To: <201301091059.31941.jbe@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1455 bytes --]
Hi Juergen
Glad to hear I didnt make a mistake and good to know what targetinstall
means. The thing is, as far as I can see, is that I need to specify the lib
path to qmake.conf. But I'm not sure which qmake.conf will be used when
building my app, do you perhaps know?
Thanks for your help.
Ruben
On Wed, Jan 9, 2013 at 11:59 AM, Juergen Beisert <jbe@pengutronix.de> wrote:
> Hi Ruben,
>
> Ruben Louw wrote:
> > I think I made a mistake then, when building the BSP, I just used ptxdist
> > select configs/ptxconfig.qt, and ptxdist platform configs/platform...128
> > then ptxdist go. do I have to build qt amd the tslib seperately using
> > ptxdist targetinstall qt4?
>
> No, you didn't made a mistake. "ptxdist go" builds everything enabled in
> the
> menuconfig. "ptxdist targetinstall qt4" just compiles one of the enabled
> packages. I have used this command, to speed up my test, if the tslib is
> built correctly.
>
> So: also when you run "ptxdist go" with "configs/ptxconfig.qt" selected,
> the
> tslib should be at the same location like here on my host, when PTXdist
> finishes its work.
>
> > I'm still trying to figure out how ptxdist works, going through the doc
> you
> > sent and making sense of it.
> >
> > Please bare with me.
>
> You're welcome.
>
> Regards,
> Juergen
>
> --
> Pengutronix e.K. | Juergen Beisert
> |
> Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
>
[-- Attachment #1.2: Type: text/html, Size: 2080 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2013-01-09 10:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 8:45 Ruben Louw
2013-01-09 8:57 ` Tim Sander
2013-01-09 9:01 ` Ruben Louw
2013-01-09 9:03 ` Tim Sander
2013-01-09 13:00 ` Ruben Louw
2013-01-09 9:04 ` Ruben Louw
2013-01-09 9:08 ` dave festing
2013-01-09 9:11 ` Ruben Louw
2013-01-09 9:05 ` Tim Sander
2013-01-09 9:00 ` dave festing
2013-01-09 9:14 ` Juergen Beisert
[not found] ` <CAOP6b3jcefipmst5hCGsf8BOQYXnPQji75faz_h9OrpQe9heVA@mail.gmail.com>
2013-01-09 9:59 ` Juergen Beisert
2013-01-09 10:37 ` Ruben Louw [this message]
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='CAOP6b3hEr=-Rdq4=YwG-BR9TNGk76jfX+KPcX=+5ORk4W53i=Q@mail.gmail.com' \
--to=lfxciii@gmail.com \
--cc=jbe@pengutronix.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