From: Roland Hieber <r.hieber@pengutronix.de>
To: Michael Deiters <michael@deiters.net>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Newbie: Howto add luajit 2.x as a new package in ptxdist
Date: Mon, 19 Jun 2017 15:03:47 +0200 [thread overview]
Message-ID: <2059a671-e6e1-0aed-433c-2469c86cdacc@pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.11.1706180100110.1800@dl8obr.ampr.org>
Hi Michael,
there is no need to add a -dev package for luajit, at least not for
installing on the target. When crosscompiling, the install stage of your
rules/luajit.make effectively calls `make install` in the luajit source
folder, which should install the development headers to
<your-platform>/sysroot-target/. When other packages depend on luajit,
they will look there for the includes and libraries to link against.
What is installed into the target root file system is different from
that; your `targetinstall` stage is responsible for that and should copy
all the files needed on the target to <your-platform>/root (e.g. by
using $(call install_lib), $(call install_alternative) etc., see Section
5.2 in the PTXdist manual [1]).
Hope that helps!
- Roland
[1]:
http://www.pengutronix.de/software/ptxdist/appnotes/OSELAS.BSP-Pengutronix-Generic-arm-Quickstart.pdf
On 18.06.2017 01:10, Michael Deiters wrote:
> Hi,
>
> I'm a newbie on ptxdist. I successfully managed to build my 1st BSP
> based on Generic-arm recently.
>
> I'm getting lost on how to add luajit including the libluajit-5.1-dev as
> package to ptxdist. I understand the approach to add an autotoolized
> package, but for the desired luajit-5.1-dev, I can only find the apt-get
> source on my host.
>
> I'm wondering if there isn't an easy way to let ptxdisk know about the
> required package. I searched the web, but didn't found enlightenment...
>
> I would be grateful if somebody could point me the right direction.
>
> Many thanks in advance!
>
> Kind regards
> Michael
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
--
Pengutronix e.K. | Roland Hieber |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-06-19 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 23:10 Michael Deiters
2017-06-19 13:03 ` Roland Hieber [this message]
2017-06-19 15:53 ` Michael Deiters
2017-06-19 16:12 ` Guillermo Rodriguez Garcia
2017-06-19 17:02 ` Clemens Gruber
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=2059a671-e6e1-0aed-433c-2469c86cdacc@pengutronix.de \
--to=r.hieber@pengutronix.de \
--cc=michael@deiters.net \
--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