From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] multiple cmake build setups in one package?
Date: Thu, 21 Jul 2016 07:18:40 +0200 [thread overview]
Message-ID: <20160721051840.GS12229@pengutronix.de> (raw)
In-Reply-To: <2054156.DWQXkAmxG4@ws-stein>
Hi,
On Tue, Jul 19, 2016 at 10:41:00AM +0200, Alexander Stein wrote:
> is it possible to generate several build setups, e.g. multiple software
> components, which requires individual cmake calls, within one ptxdist package?
> What would be a workaround if I can't do that?
Why don't you create multiple ptxdist packages with the same source
archive?
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:[~2016-07-21 5:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 8:41 Alexander Stein
2016-07-19 11:28 ` Ladislav Michl
2016-07-19 11:36 ` Alexander Stein
2016-07-21 5:18 ` Michael Olbrich [this message]
2016-07-26 7:55 ` Alexander Stein
2016-07-27 6:59 ` 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=20160721051840.GS12229@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