From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Thomas Walter <thomas.walter@csc-online.eu>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] gpsd library
Date: Wed, 18 Sep 2013 17:14:52 +0200 [thread overview]
Message-ID: <20130918151452.GP24802@pengutronix.de> (raw)
In-Reply-To: <002c01ceb45a$b9ed0e20$2dc72a60$@csc-online.eu>
Hello Thomas,
On Wed, Sep 18, 2013 at 12:34:58PM +0200, Thomas Walter wrote:
> What I did is the following:
>
> I cross-compiled the gpsd3.9 version using the Toolchain 2011.11.1, because
> this is the one which comes with my PhyCORE-AM335. Phytec does not yet use
> Toolchain 2012.12.1.
>
> The build uses the make-successor scons and not the usual way via
huh, "make-successor". There are definitly enough people in the open
source world that think that scons is worse than make, so I doubt they
will take over.
> ./configure and make. I am not the expert in creating python scripts and
> just started with ptxdist ... However, after some treatment of the gpds
> cross-compile scons configuration files I got a compiled gpsd binary and
> libgsps of version 3.9, which runs with my target and the Toolchain
> 2011.11.1. I did not build gpsmon, because ncurses is not part of the
> toolchain (couldn't find header files). Furthermore I disabled Bluetooth due
That should be possible to add when enabling ncurses in your ptxconfig.
Don't know about bluetooth.
> the same issue.
>
> I added a "file" packages to ptxdist in order to get them installed (simply
> copied) to /usr. I just flashed the generated image and it works. This
> concept works so far for me ... but I think it would be better to compile
> the gps library during the "go"-process. But as I said I am not the python
> expert and ... in addition still on a Linux learning curve by jumping
> directly into an embedded use of it.
Definitly. Maybe someone can point another scons package that is good
enough to copy the ptxdist rules from?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2013-09-18 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 9:29 Thomas Walter
2013-09-13 10:39 ` Jürgen Beisert
2013-09-13 10:46 ` Alexander Dahl
2013-09-13 10:58 ` Thomas Walter
2013-09-13 11:27 ` Alexander Dahl
2013-09-13 12:32 ` Thomas Walter
2013-09-16 8:39 ` Uwe Kleine-König
[not found] ` <001501ceb37a$ced0b750$6c7225f0$@csc-online.eu>
[not found] ` <20130917175138.GM24802@pengutronix.de>
[not found] ` <002c01ceb45a$b9ed0e20$2dc72a60$@csc-online.eu>
2013-09-18 15:14 ` Uwe Kleine-König [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=20130918151452.GP24802@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=thomas.walter@csc-online.eu \
/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