mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
* [ptxdist] ptxdist commands
@ 2014-06-03 15:29 Sophie CARAYOL
  2014-06-04  6:56 ` Juergen Borleis
  0 siblings, 1 reply; 3+ messages in thread
From: Sophie CARAYOL @ 2014-06-03 15:29 UTC (permalink / raw)
  To: ptxdist

Hi,

I don't find some explanations about ptxdist in the developer's manual.
- What's the difference between 'ptxdist clean' 'ptxdist drop'
- If I made some modifications on files (for example in u-boot or kernel),
what is the right command to re-build the project.

Best regards,

Sophie


-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ptxdist] ptxdist commands
  2014-06-03 15:29 [ptxdist] ptxdist commands Sophie CARAYOL
@ 2014-06-04  6:56 ` Juergen Borleis
  2014-06-04  7:48   ` CARAYOL Sophie
  0 siblings, 1 reply; 3+ messages in thread
From: Juergen Borleis @ 2014-06-04  6:56 UTC (permalink / raw)
  To: ptxdist; +Cc: Sophie CARAYOL

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ptxdist] ptxdist commands
  2014-06-04  6:56 ` Juergen Borleis
@ 2014-06-04  7:48   ` CARAYOL Sophie
  0 siblings, 0 replies; 3+ messages in thread
From: CARAYOL Sophie @ 2014-06-04  7:48 UTC (permalink / raw)
  To: Juergen Borleis, ptxdist

Hi Juergen,

Thanks for your help.

Sophie


-----Message d'origine-----
De : Juergen Borleis [mailto:jbe@pengutronix.de]
Envoyé : mercredi 4 juin 2014 08:57
À : ptxdist@pengutronix.de
Cc : CARAYOL Sophie
Objet : Re: [ptxdist] ptxdist commands

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/  |
________________________________

[http://www.lacroix-electronics-solutions.com/sites/default/files/pictures/achievements/201401_MEDTECHPHARMA_LE_exhibit.png]

[http://www.lacroix-electronics.com/sites/default/files/pictures/Dossier_photos/Actualites_FR_UK_DE/Electronica.png]

Electronica in Munich (Germany), November 11-14, 2014
Join us at our stand A2 459
________________________________
 Pour des raisons légales et de sécurité, les informations contenues dans ce message ne sont pas juridiquement contraignantes. Sur demande, nous vous adresserons une confirmation écrite nous engageant. Les informations contenues dans ce message électronique ont un caractère strictement confidentiel et sont exclusivement destinées à la personne à laquelle il est adressé. Toute divulgation, utilisation, diffusion ou reproduction de tout ou partie de ce message, ou des informations qu'il contient, est interdite. Ce message est destiné exclusivement à la personne à laquelle il est adressé ou son représentant. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de détruire ce message.
For legal and security reasons the information provided in this e-mail is not legally binding. Upon request we would be pleased to provide you with a legally binding confirmation in written form. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer..
Aus gesetzlichen und Sicherheitsgründen sind die in dieser Nachricht enthaltenen Informationen rechtlich unverbindlich. Auf Anfrage senden wir Ihnen eine verbindliche, schriftliche Bestätigung. Die in dieser E-Mail enthaltenen Informationen sind streng vertraulich und ausschließlich für den Empfänger bestimmt. Jede vollständige oder teilweise Veröffentlichung, Verwendung, Verbreitung oder Vervielfältigung dieser Nachricht oder der darin enthaltenen Informationen ist untersagt. Diese Nachricht ist ausschließlich für die Person bestimmt, an die sie adressiert ist, oder für ihren Vertreter. Sollten Sie diese Nachricht versehentlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie die Nachricht..
Disclaimer Lacroix Electronics
-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-06-04  7:48 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-06-03 15:29 [ptxdist] ptxdist commands Sophie CARAYOL
2014-06-04  6:56 ` Juergen Borleis
2014-06-04  7:48   ` CARAYOL Sophie

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox