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
[email protected]
