Hi Andrew;
well done - a first test compiles and builded image boots.
I have to confess, I do not understand your thoughts below :)
Instead a few comments/questions:
1) I saw that there is a new buildtool.pl option ("buildtool.pl
headers"), but it's not mentioned if I run "buildtool.pl help". Also, is
it possible, for conistency, to run that as a "build" target:
"buildtool.pl build headers"? And probably also a "clean" target for
headers?
2) Before we move it to master, there's need for a new target/script
that removes everything except toolchain and headers (similar to
cleanall.sh), otherwise there will be no time saving.
3) You started with a genheaders.sh script, but removed it later.
Instead you've added repo/toolcahin/linux-headers.tar.bz2. A script to
build a new headers file anytime in the future could be helpful.
Maybe I have some more, while working with the stuff - anyway it will be
helpful if you can add some documenation to the Developer Guide in the
wiki - e.g I saw that you made changes to make/toolchain/*.mk, I guess
there might be more that needs documentation - can be a section
"upcoming changes" at tis time.
If you agree, we should first release a 5.0 version based on master, and
merge your branch for 5.1 - what do you think?
To me 5.0 looks pretty stable and I think a release candidate can be
done soon, and a final version two or three weeks later.
Btw: AFAIK the kernel patches for the raspberry pi will be included in
the 3.10 linux kernel. I'll give it a try once the kernel maintainers
provide a first version to test.
kp
Am 06.05.2013 15:28, schrieb Andrew:
> Done, distro is still compiled (I'll try to run it when compilation will
> be finished), but it seems like all is OK.
> I added target 'headers' to build linux headers for platform (this is
> development thing), and it looks like there are a lot of redundant code.
> Also target plugins loading can be simplified (now it should be
> mentioned in buildtool.pl in 'use' and in code, and in
> Object.pm/InstalledFile.pm as target), IMHO it'll be good to simplify
> adding of targets (make 'targets' config or even load all content of
> Make folder and dynamically fill targets array in plugins init code).
> And move targets dependency resolving (for ex., 'build' target now is
> dependent from 'source') to plugins.
> Also I noticed that some packages are dependent of 'kernel' package (I'm
> not sure if this dependency is actual), and some packages are dependent
> of 'linux' package. It'll be good to try to assemble them w/o
> kernel/linux to look if dependencies are required.
>
>
> 02.05.2013 20:59, KP Kirchdoerfer пишет:
>> Hi Andrew;
>>
>> Am 29.04.2013 14:21, schrieb Andrew:
>>> Hi.
>>> It looks like there will be a three steps that I described, except order
>>> - 2nd and 1st step should be exchanged. So 1) add linux headers (and
>>> look if headers for different archs differs - AFAIK some of headers will
>>> be different); 2) add separate targets and 3) add choose for target
>>> kernel (and list of available kernels for arch/subarch with possibility
>>> to build all in list).
>> Will you give a try for first step in a new branch (or next branch, if
>> merged with master)?
>>
>> kp
>> (I'll be offline for a week)
>>
>>
>>> 28.04.2013 17:16, KP Kirchdoerfer пишет:
>>>> Hi Andrew;
>>>>
>>>> is there a possibilty to divide the proposal below in two or more steps,
>>>> so we can test, work with and get more experienced?
>>>>
>>>> Like 1) add three targets, including cleaning each target (and it's
>>>> dependencies) 2) add building different kernel and modules
>>>>
>>>>
>>>> kp
>>>>
>>>>
>>>> Am 23.04.2013 21:59, schrieb Andrew:
>>>>> Hi all.
>>>>>
>>>>> Now we have building of toolchain, userlevel apps and kernel (with
>>>>> modules) as similar targets, with same logic. But for future embedded
>>>>> platforms with same/similar CPU arch (but with multiple kernels - for
>>>>> each SoC required separate kernel, possible even with different versions
>>>>> - like rpi case) it causes some troubles. Also rebuilding from scratch
>>>>> taints also toolchain - ~20-30% of rebuilding time.
>>>>>
>>>>> I think that it'll be good if we'll separate building of toolchain,
>>>>> kernel(+modules) and userland into 3 different procedures. For this, I
>>>>> propose to do next things:
>>>>>
>>>>> 1) Add 3 targets - 'build-toolchain', 'build-userspace', 'build-kernel'
>>>>> instead of single 'build'; for toolchain - 'build-userspace' will just
>>>>> install libs'headers from toolchain dir into staging dir. This should
>>>>> allow to quickly rebuild only userspace soft, or only kernel, or all
>>>>> except toolchain.
>>>>>
>>>>> 2) Add tarball with kernel headers into toolchain instead of headers
>>>>> generation from linux source (it shouldn't produce any pbs - at least
>>>>> for some years of Gentoo usage I didn't saw pbs if headers were older
>>>>> than kernel sources or packages were built with older headers; and more
>>>>> - it's usual situation in Gentoo). This will remove pain of multiple
>>>>> kernel versions into single tree and remove toolchain dependency from
>>>>> linux kernel.
>>>>>
>>>>> 3) Add possibility to specify arch/version of kernel to build via
>>>>> cmdline, and specify list of available major versions (for ex., 3.4, 3.6
>>>>> and so on) with default one in platform makefile (currently I don't know
>>>>> optimal method to do this). Also this should affect buildpackage.pl.
>>>>>
>>>>> I'll be glad to hear your ideas about this.
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Try New Relic Now & We'll Send You this Cool Shirt
>>>>> New Relic is the only SaaS-based application performance monitoring
>>>>> service
>>>>> that delivers powerful full stack analytics. Optimize and monitor your
>>>>> browser, app, & servers with just a few lines of code. Try New Relic
>>>>> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
>>>>>
>>>>> _______________________________________________
>>>>> leaf-devel mailing list
>>>>> leaf-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/leaf-devel
>>>>>
>>>> ------------------------------------------------------------------------------
>>>> Try New Relic Now & We'll Send You this Cool Shirt
>>>> New Relic is the only SaaS-based application performance monitoring service
>>>> that delivers powerful full stack analytics. Optimize and monitor your
>>>> browser, app, & servers with just a few lines of code. Try New Relic
>>>> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
>>>>
>>>> _______________________________________________
>>>> leaf-devel mailing list
>>>> leaf-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/leaf-devel
>>>
>>> ------------------------------------------------------------------------------
>>> Try New Relic Now & We'll Send You this Cool Shirt
>>> New Relic is the only SaaS-based application performance monitoring service
>>> that delivers powerful full stack analytics. Optimize and monitor your
>>> browser, app, & servers with just a few lines of code. Try New Relic
>>> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
>>>
>>> _______________________________________________
>>> leaf-devel mailing list
>>> leaf-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/leaf-devel
>>>
>> ------------------------------------------------------------------------------
>> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
>> Get 100% visibility into your production application - at no cost.
>> Code-level diagnostics for performance bottlenecks with <2% overhead
>> Download for free and get started troubleshooting in minutes.
>> http://p.sf.net/sfu/appdyn_d2d_ap1
>>
>> _______________________________________________
>> leaf-devel mailing list
>> leaf-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/leaf-devel
>
>
> ------------------------------------------------------------------------------
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
>
> _______________________________________________
> leaf-devel mailing list
> leaf-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/leaf-devel
>
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
