Hi Claudio,
On Tue, Jan 06, 2009 at 05:12:55PM -0200, Claudio Leonel wrote:
> I have two projects using PTXDIST 1.0.2. I would like start a new
> project with the latest development version because of the new
> packages available.
Great! Unfortunately, things are quite heavily in flow recently, because
we are hunting towards a new stable 2.0.0 release. So testers are very
welcome at this moment (for trunk even more than for 1.99.10).
> I downloaded version 1.99.10 (main archive and
> patches) and I am trying to create a new project from
> scratch.
>
> I created an empty ptxconfig with only the
> version number, and selected it with:
>
> ptxdist --force select <ptxconfig>
>
> I tried to 'ptxdist menuconfig' but ptxdist complained
> that 'selected_platformconfig' is missing.
You should be able to create it the same way:
touch selected_platformconfig
ptxdist oldconfig platform
> I didn't find any documentation regarding this platformconfig
> file. What should be the contents of this file?
We have separated all platform dependend config from the software
configuration; it is now possible to build the same BSP for different
hardware platforms; the simplest usage of this new feature is that you
build your ARM or PowerPC BSP for i586 and run it in qemu.
Platforms can be selected by
ptxdist platform configs/my_platform_name/platformconfig
which links that file to selected_platformconfig in the workspace. This
is the preferred directory layout for project that contain more than one
platform. If you have only one, do it like I described above.
If you need a real-world example, the unified phyCORE BSP (8.0) will be
available very soon (this week) and contains support for phyCORE-i.MX27
and phyCORE-i.MX31, all in the same BSP.
> I also saw a reference in the help to a 'collection'.
> What is this ?
It is now possible to select packages with the "tristate" feature. That
means that packages can now be deselected, "yes" or "module". If you
ignore the "collection" feature, everything is like you are used to: all
packages that are "yes" or "module" will be built.
Collections can be used to build a subset of your BSP. If you have
switched some packages to "module", you can run 'ptxdist menuconfig
collection' and build "subsets". That way you can for example build a
BSP containing almost everything, then make a minimal set of packages
"yes", just enough to get the box up and running with kernel, glibc and
network. Then make a flash image from this minimal collection and push
it into your devices on production time. If you additionally have for
example another collection containing everything, you can build all ipkg
packages, put them on a server and install them later in binary form.
What's still missing in this scenario is a magic that adds our auto
generated dependencies to the ipkg dependencies. If that's finished, it
should in theory be possible to do somehting like "ipkg install kde" -
taken that somebody sends patches for kde packages :)
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
[email protected]
