From: Roland Hieber <r.hieber@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 0/1] doc: Documenting PKGDIR and friends
Date: Thu, 13 Sep 2018 11:26:29 +0200 [thread overview]
Message-ID: <20180913092629.jufs4zs5cmnk7mzk@pengutronix.de> (raw)
In-Reply-To: <20180913072258.31199-1-ada@thorsis.com>
On Thu, Sep 13, 2018 at 09:22:57AM +0200, Alexander Dahl wrote:
> Hei hei,
>
> I'm currently writing package rules for some ugly Make only based
> sources. I could sort out my questions about how to use $(SYSROOT) and
> $(FOO_PKGDIR) in compile and install stages by looking at other
> packages, but I would say that part is missing in the documentation.
> My assumption so far is: the default install stage installs to
> $(FOO_PKGDIR) and that content is magically copied to $(SYSROOT) then?
As far as I remember, the install stage installs to FOO_PKGDIR, and the
targetinstall stage then installs from FOO_PKGDIR to SYSROOT.
I guess there is the need to document the interface between the single
stages somehow, what each stage expects and what it is supposed to do.
- Roland
--
Roland Hieber | r.hieber@pengutronix.de |
Pengutronix e.K. | https://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:[~2018-09-13 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 7:22 Alexander Dahl
2018-09-13 7:22 ` [ptxdist] [PATCH 1/1] doc: Fix wrong use of PKGDIR Alexander Dahl
2018-09-13 9:26 ` Roland Hieber [this message]
2018-09-17 8:50 ` [ptxdist] [PATCH 0/1] doc: Documenting PKGDIR and friends Michael Olbrich
2018-10-08 6:35 ` Alexander Dahl
2018-10-09 7:21 ` Michael Olbrich
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=20180913092629.jufs4zs5cmnk7mzk@pengutronix.de \
--to=r.hieber@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