From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 0/1] doc: Documenting PKGDIR and friends
Date: Mon, 17 Sep 2018 10:50:43 +0200 [thread overview]
Message-ID: <20180917085043.v5ujq2w4shjh64ln@pengutronix.de> (raw)
In-Reply-To: <20180913092629.jufs4zs5cmnk7mzk@pengutronix.de>
On Thu, Sep 13, 2018 at 11:26:29AM +0200, Roland Hieber wrote:
> 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.
It's install.post not targetinstall that copies the files to the correct
sysroot.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-09-17 8:50 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 ` [ptxdist] [PATCH 0/1] doc: Documenting PKGDIR and friends Roland Hieber
2018-09-17 8:50 ` Michael Olbrich [this message]
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=20180917085043.v5ujq2w4shjh64ln@pengutronix.de \
--to=m.olbrich@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