mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Denis Osterland-Heim <denis.osterland@diehl.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Ptxdist lightweight packaging usecase.
Date: Thu, 21 Jan 2021 06:38:35 +0000	[thread overview]
Message-ID: <49d41e07934ac89cf3ef63d1dc3b38116d141ef6.camel@diehl.com> (raw)
In-Reply-To: <b376da73-dcbf-6a37-62ce-0cae13429e5d@t2data.com>

Hi,

I am not 100% if I got your point.

If you want to speed-up the ptxdist build you may have a look at https://www.ptxdist.org/doc/daily_work_section.html#using-pre-built-archives

If you want to create an environment for application developers where they can compile the application without ptxdist,
you just need to provide the `platform-XXX/sysroot-target` and a bunch of variables depending on the build-system.

Regards, Denis

Am Mittwoch, den 20.01.2021, 18:39 +0100 schrieb Christian Melki:
> Hi.
>
> I'd like to package (docker) a complete ptxdist build environment for a
> target platform but as light as possible. Since most application
> developers do not care about platform stuff, but still need to build
> images from time to time.
>
> So now I have this question: Can I purge build and still produce results?
>
> If I build a platform and remove src, platform-X/build-target,
> platform-X/build-host the actual storage requirements for a docker
> becomes _far_ less. All state are kept so I'd want the user to be able
> to do clean && compile for his rules. Also I'd like to be able to do a
> complete go && images.
>
> The major caveat seems to be the sources directory. If I whipe the
> sources, ptxdist tries to rebuild stuff, even if there is no file (not
> changed, missing) and all states are completed. Get, prepare, compile,
> install etc.
>
> Is there a proper way ptxdist can accomodate this usecase? I don't find
> it unresonable. There is little point in keeping everything or every
> user producing every bit of the result.
> Storage requirements is only like 10% of the original. Far easier to
> keep complete states of releases as fast checkpoints for minor corrections.
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
Diehl Connectivity Solutions GmbH
Geschäftsführung: Horst Leonberger
Sitz der Gesellschaft: Nürnberg - Registergericht: Amtsgericht
Nürnberg: HRB 32315

________________________________

Der Inhalt der vorstehenden E-Mail ist nicht rechtlich bindend. Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Informieren Sie uns bitte, wenn Sie diese E-Mail faelschlicherweise erhalten haben. Bitte loeschen Sie in diesem Fall die Nachricht.
Jede unerlaubte Form der Reproduktion, Bekanntgabe, Aenderung, Verteilung und/oder Publikation dieser E-Mail ist strengstens untersagt.

- Informationen zum Datenschutz, insbesondere zu Ihren Rechten, erhalten Sie unter:

https://www.diehl.com/group/de/transparenz-und-informationspflichten/

The contents of the above mentioned e-mail is not legally binding. This e-mail contains confidential and/or legally protected information. Please inform us if you have received this e-mail by
mistake and delete it in such a case. Each unauthorized reproduction, disclosure, alteration, distribution and/or publication of this e-mail is strictly prohibited.

- For general information on data protection and your respective rights please visit:

https://www.diehl.com/group/en/transparency-and-information-obligations/


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

  reply	other threads:[~2021-01-21  6:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 17:39 Christian Melki
2021-01-21  6:38 ` Denis Osterland-Heim [this message]
2021-01-21 12:07 ` 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=49d41e07934ac89cf3ef63d1dc3b38116d141ef6.camel@diehl.com \
    --to=denis.osterland@diehl.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