mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Baeuerle, Florian" <Florian.Baeuerle@allegion.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] PTXdist usescases
Date: Fri, 31 Aug 2018 12:03:46 +0000	[thread overview]
Message-ID: <b387e87a384e2669611a90184882213c1fec6d5c.camel@allegion.com> (raw)
In-Reply-To: <20180831101728.jmr5iz74ss6n7sjz@pengutronix.de>

Am Freitag, den 31.08.2018, 12:17 +0200 schrieb Michael Olbrich:
> You need:
> $platform_a/rules/platform-opengl.in with no dependencies
> 
> $platform_a/platforms/platform-opengl.in that depends on ti-sgx-drivers
> $platform_a/platforms/*.in for ti-sgx-drivers
> 
> These must have a section that exists for the platformconfig, e.g.
> 'architecture_options'. Don't use prompts and set 'default y' for
> platform-opengl here.

It feels overall hacky and it does not seem to work for dependencies of the
ti-sgx-packages. So my options are:

- managing the ti-sgx- dependencies in the ptxconfig/or a collection manually.
- define dependant symbols the same way (including the symbols the dependencies
  depend on...), so they end up in the platformconfig

One more thing that I missed pointing out is that this combination should
(ideally) work as well:

ptxconfig without dependency on platform-opengl + platform a
 -> installs no ti-sgx-drivers
> 
> Then the symbols will be in the platformconfig.
> 
> Do the samge for platform b.
> 
> At build-time it does not matter if the package is selected in the
> ptxconfig or the platformconfig.


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2018-08-31 12:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13  7:28 Erwin Rol
2018-08-13 10:19 ` Robert Schwebel
2018-08-13 12:16   ` Erwin Rol
2018-08-13 12:40     ` Robert Schwebel
2018-08-27 16:40       ` Michael Olbrich
2018-08-28 15:27         ` Erwin Rol
2018-08-29  8:14           ` Baeuerle, Florian
2018-08-29 14:30             ` Michael Olbrich
2018-08-28 10:07 ` Baeuerle, Florian
2018-08-29 14:48   ` Michael Olbrich
2018-08-30  8:05     ` Baeuerle, Florian
2018-08-30  9:41       ` Michael Olbrich
2018-08-30 13:06         ` Baeuerle, Florian
2018-08-30 13:41           ` Michael Olbrich
2018-08-31  8:41         ` Baeuerle, Florian
2018-08-31 10:17           ` Michael Olbrich
2018-08-31 12:03             ` Baeuerle, Florian [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=b387e87a384e2669611a90184882213c1fec6d5c.camel@allegion.com \
    --to=florian.baeuerle@allegion.com \
    --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