From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Question to BUILDTIME
Date: Fri, 28 Jun 2019 16:23:51 +0200 [thread overview]
Message-ID: <20190628142351.c65ztqmdt7zqtvby@pengutronix.de> (raw)
In-Reply-To: <1561709649.6672.6.camel@diehl.com>
Hi,
On Fri, Jun 28, 2019 at 08:14:09AM +0000, Denis OSTERLAND wrote:
> Am Freitag, den 28.06.2019, 09:12 +0200 schrieb Michael Olbrich:
> > On Thu, Jun 27, 2019 at 01:25:50PM +0000, Denis OSTERLAND wrote:
> > >
> > > select <pkg> if BUILDTIME
> > >
> > > works only if <pkg> has no prompt, correct?
> > No, 'if BUILDTIME' can be used with any package. It just means, that The
> > packages will be ordered accordingly at build-time but no dependency will
> > be added to the resulting .ipk File.
> This was how I understand it two.
> The last time I used this feature is to long ago, to be sure ;-)
> With recent release (ptxdist-2019.06.0) the package gets installed until I remove prompt line.
>
> I try to pin my problem down.
> Where is the post processing which removes the dependencies with BUILDTIME?
> I mean, in 'scripts/lib/ptxd_lib_dgen.sh' there is 'PTXDIST_DEP_TARGET="run" ptxd_kconfig_dep_all "${config[@]}"',
> but the automatically selected package will stick if it has a prompt.
I think I understand way you're trying to do. Consider this example:
config FOO
tristate
select BAR if BUILDTIME
prompt "foo"
If 'foo' is enabled, then so is 'bar'. This means both symbols are enabled
in the ptxconfig. This also means that both packages will be in the default
package ist for the rootfs. That cannot be changed.
What 'if BUILDTIME' means is, that
1. The make dependencies are a bit more relaxed, which can improve the
build time.
2. There is no dependency for this in the ipkg. So you could remove the
package 'bar' at runtime without removing 'foo'.
Creating an image with 'foo' but without 'bar' is not easily done. I
suppose you could create your own image with:
IMAGE_BLA_PKGS := $(filter-out bar,$(PTX_PACKAGES_INSTALL))
Regards,
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:[~2019-06-28 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 13:25 Denis OSTERLAND
2019-06-28 7:12 ` Michael Olbrich
2019-06-28 8:14 ` Denis OSTERLAND
2019-06-28 14:23 ` Michael Olbrich [this message]
2019-06-28 15:04 ` Denis OSTERLAND
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=20190628142351.c65ztqmdt7zqtvby@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