mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Sophie CARAYOL <s.carayol@lacroix-electronics.com>
Subject: Re: [ptxdist] ptxdist commands
Date: Wed, 4 Jun 2014 08:56:48 +0200	[thread overview]
Message-ID: <201406040856.49010.jbe@pengutronix.de> (raw)
In-Reply-To: <loom.20140603T171248-308@post.gmane.org>

Hi Sophie,

On Tuesday 03 June 2014 17:29:03 Sophie CARAYOL wrote:
> I don't find some explanations about ptxdist in the developer's manual.
> - What's the difference between 'ptxdist clean' 'ptxdist drop'

"clean" removes files, while "drop" only remove state information.

> - If I made some modifications on files (for example in u-boot or kernel),
> what is the right command to re-build the project.

PTXdist works with states for every single package. It walks through the main 
states in the following order:

 - get: get package sources
 - extract: extract package (its archive for example)
 - prepare: run configure stages for this package
 - compile: compile the sources of this package
 - install: install the results into the corresponding sysroot/
 - targetinstall: create the content for the ipkg and install files for target
                  into root/

So it depends on what you want PTXdist to do again. If you have modified 
sources in the build directory of a package and you want to force PTXdist to 
re-compile this changes again, just drop the package's "compile" stage. In the 
case of the kernel:

  ptxdist targetinstall kernel
  do {
      <running the kernel, it does not work, change some code in the kernel
       source tree>
      ptxdist drop kernel.compile
      ptxdist targetinstall kernel
  } while (!does_work_now)

Maybe the section "Using an External Kernel Source Tree" in the manual can help 
you.

Regards,
Jürgen

-- 
Pengutronix e.K.                              | Juergen Borleis             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-06-04  6:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 15:29 Sophie CARAYOL
2014-06-04  6:56 ` Juergen Borleis [this message]
2014-06-04  7:48   ` CARAYOL Sophie

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=201406040856.49010.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=s.carayol@lacroix-electronics.com \
    /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