mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ptx/image-install for older ptxdist releases
Date: Wed, 19 Apr 2023 09:19:58 +0200	[thread overview]
Message-ID: <20230419071958.GK22555@pengutronix.de> (raw)
In-Reply-To: <CABDcavaR8+Wt9pChfMeS6pQEEL_B+icc3oK_UrebG4i5SkTQFQ@mail.gmail.com>

Hi,

On Tue, Apr 18, 2023 at 04:39:54PM +0200, Guillermo Rodriguez Garcia wrote:
> I have an "image" package that generates more than one image file.
> 
> In the past I asked what would be the best way to handle this so that the
> clean target works correctly. Michael suggested to use ptx/image-install:
> 
> > You should be able to use ptx/image-install in the image rule. Just like
> > regular packages. File installed with this are recorded and later removed
> > in the clean stage.
> 
> I have found that ptx/image-install indeed solves the problem when
> available; however this was added relatively recently and does not exist
> for older ptxdist releases.
> 
> Is there a way to achieve similar functionality in ptxdist releases where
> ptx/image-install is not available ?

It should be possible to backport that feature. Take a look at the commit
that introduced the feature 3694633183ae70aeba062d53db3eeb4bf521d090. You
basically need to copy that stuff into your BSP in the same locations
(rules/post and scripts/lib).

Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



           reply	other threads:[~2023-04-19  7:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CABDcavaR8+Wt9pChfMeS6pQEEL_B+icc3oK_UrebG4i5SkTQFQ@mail.gmail.com>]

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=20230419071958.GK22555@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=guille.rodriguez@gmail.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