Wolfram Sang wrote: > On Tue, Nov 11, 2008 at 07:40:58AM -0700, Gary Thomas wrote: > >> Close, but I'm still fuzzy on a couple of details. >> >> * Why not just specify the whole kernel source path, rather than >> the [obscure in my mind] prefix + version. I have kernel source >> trees all over the place and having to rerun 'setup' to build >> seems problematic. > > It is problematic and it is not finished yet. What I would like to have > is to have access to my own git-repository with lots of branches (like > one for every ptxdist-project). The time I added this feature, I thought > it might be a good way to have all of my branches checked out as > seperate trees. This is why there is a prefix and the version (=branch). > But I am not quite sure about this approach, as I'm also still not quite > sure of my git-workflow managing BSPs and upstream at the same time. > > It might be an idea to be able to specify a path as a version. Hmmm.... > >> * How do I specify a particular kernel configuration? Currently, > > In the above approach you can use 'ptxdist kernelconfig'. That means it > will work with $PLATFORM_CONFIGDIR/kernelconfig-<version> and put it > into the kernel-dir as .config. > >> I will build my kernel like this: >> % mkdir /work/new_kernel >> % make -C /work/kernel_source O=/work/new_kernel platform_defconfig >> % make O=/work/new_kernel oldconfig >> % make O=/work/new_kernel zImage > > Looks like you want to build a number of kernels from one tree?
Yes. Is there any way to just use a pre-built tree? -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ -- ptxdist mailing list ptxdist@pengutronix.de
