[Buildroot] Reviewing the Buildroot ELC presentation slides

[Buildroot] Reviewing the Buildroot ELC presentation slides

[Thomas Petazzoni]

Hello,

I have posted at http://free-electrons.com/~thomas/pub/buildroot.pdf
the current version of the slides I intend to present next week at the
ELC in San Francisco.

For the record, the conference abstract is:
https://events.linuxfoundation.org/events/embedded-linux-conference/petazzoni

I would be very interested in your comments and review, both on details
(typos, mistakes) but also on the overall contents of the slides.

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Reviewing the Buildroot ELC presentation slides

[Thomas De Schampheleire]

Hi Thomas,

On Tue, Feb 7, 2012 at 10:46 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> I have posted at http://free-electrons.com/~thomas/pub/buildroot.pdf
> the current version of the slides I intend to present next week at the
> ELC in San Francisco.
>
> For the record, the conference abstract is:
> https://events.linuxfoundation.org/events/embedded-linux-conference/petazzoni
>
> I would be very interested in your comments and review, both on details
> (typos, mistakes) but also on the overall contents of the slides.

slide 4: Complete rebuild -> rebuilds

slide 9: I find it a bit strange that the toolchain block is at the
bottom, since it is the first thing to be produced. But maybe you
intentionally put it there as most people would care more about the
other blocks...

slide 13: a SDK -> I think this should be 'an SDK' as this is how you
pronounce it.

slide 14: on the internal toolchain you write 'the historic one': I
feel it could be interpreted negatively and not as a viable
alternative.
slide 14: an uClibc --> here I think it should be 'a uClibc' as you
pronounce as 'you-see-libc'.

slide 18: is9660 -> iso9660

slide 23: I'd put a semicolon instead of comma between the toolchain
and library example
slide 23: all reverse dependencies needs to be rebuilt -> need

slide 25: a few stamps files -> stamp

slide 29: there should be a space after 'make' in
make<foo>-reconfigure and make<foo>-rebuild

slide 30: choosen -> chosen


>
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

[Buildroot] Reviewing the Buildroot ELC presentation slides

[Thomas De Schampheleire]

[sorry wasn't finished yet]

On Wed, Feb 8, 2012 at 8:02 AM, Thomas De Schampheleire
<patrickdepinguin+buildroot@gmail.com> wrote:
> Hi Thomas,
>
> On Tue, Feb 7, 2012 at 10:46 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Hello,
>>
>> I have posted at http://free-electrons.com/~thomas/pub/buildroot.pdf
>> the current version of the slides I intend to present next week at the
>> ELC in San Francisco.
>>
>> For the record, the conference abstract is:
>> https://events.linuxfoundation.org/events/embedded-linux-conference/petazzoni
>>
>> I would be very interested in your comments and review, both on details
>> (typos, mistakes) but also on the overall contents of the slides.
>
> slide 4: Complete rebuild -> rebuilds
>
> slide 9: I find it a bit strange that the toolchain block is at the
> bottom, since it is the first thing to be produced. But maybe you
> intentionally put it there as most people would care more about the
> other blocks...
>
> slide 13: a SDK -> I think this should be 'an SDK' as this is how you
> pronounce it.
>
> slide 14: on the internal toolchain you write 'the historic one': I
> feel it could be interpreted negatively and not as a viable
> alternative.
> slide 14: an uClibc --> here I think it should be 'a uClibc' as you
> pronounce as 'you-see-libc'.
>
> slide 18: is9660 -> iso9660
>
> slide 23: I'd put a semicolon instead of comma between the toolchain
> and library example
> slide 23: all reverse dependencies needs to be rebuilt -> need
>
> slide 25: a few stamps files -> stamp
>
> slide 29: there should be a space after 'make' in
> make<foo>-reconfigure and make<foo>-rebuild
>
> slide 30: choosen -> chosen
>

slide 38: needs to set --> need


General things:
- ordering of slides: I had a jump-around feeling around slide 20 and
a bit further:
20: building
21-22: examples
23: simplicity principle
24-25: build output
26 and further: overall logic

I would put the slides on build output after slide 20 about building.
And the simplicity slide seems a bit lost there in my opinion. I don't
directly see the relation with the surrounding slides. Maybe it can be
put further on, e.g. before the 'future directions' slide. But again,
this can be just me.

Are you still planning to add an agenda slide?

You haven't mentioned anything about recent features as source
directory override and local site method. Not sure if this becomes too
detailed, though.

But overall: nice job again for this presentation. Good luck with it!

Best regards,
Thomas

[Buildroot] Reviewing the Buildroot ELC presentation slides

[Peter Korsgaard]

>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> writes:

Hi,

 Thomas> slide 14: an uClibc --> here I think it should be 'a uClibc' as you
 Thomas> pronounce as 'you-see-libc'.

And there seems to be something missing in that line. I suggest using
'.. build a uClibc based toolchain'.

slide 27: (external) 'copies the original toolchain sysroot in the
host/usr'. I would use 'copy to' rather than 'copy in'.

slide 29: s/typle/tuple/. You use host/usr, but only target/ - Probably
drop "usr".

slide 38: maybe explain when you would want to autoreconfigure
(E.G. when patching auto* files).

Otherwise it looks good to me, thanks!

-- 
Bye, Peter Korsgaard

[Buildroot] Reviewing the Buildroot ELC presentation slides

[Samuel Martin]

Hi,

First, nice job!
It is a clear presentation about BR and and its innards.

Though the improving of the doc appears in the "Future directions"
section (slide 40),
I think it could interesting for new comers to have a link pointed to it anyway.

Regards,

Sam

[Buildroot] Reviewing the Buildroot ELC presentation slides

[Will Moore]

Hi Thomas,

Some typo etc suggestions:

Slide 2, "... and Android system development trainings, ...", trainings ->
training
Slide 4, "Those technologies are familiar ...", Those -> These
Slide 4, "... composed only of Busybox, ...", Busybox -> BusyBox or busybox (I
believe), this applies in other slides too.
Slide 7, "Increase of the number ...", of -> in
Slide 14, "... which allows to use existing ..." -> "... which allows use of
existing ..."
Slide 14, "Using this backend allows to completely skip the toolchain build
time." -> "Using an external toolchain removes the toolchain build time."
Slide 14, "This allows to benefit from all Crosstool-NG advantages..." -> "This
allows Buildroot to benefit from all Crosstool-NG's advantages ..."
Slide 15, "Allows to define ..." -> "Allows you to define ..."
Slide 15, "Some misc. other parameters" does not really add anything useful, can
you be more specific?
Slide 19, "Allows to build ..." -> "Allows you to build ..."
Slide 19, Capitalisation consistency: syslinux -> Syslinux
Slide 25, talking about an "internal backend" seems a little clumsy, perhaps
"internal toolchain" would be better.
Slide 29, "... allow to restart ..." -> "... allow you to restart ..."
Slide 31, "boot, bootloaders recipes" -> "boot, bootloader recipes"

To add my 2p to the discussion on "a" versus "an", I agree with Thomas De
Schampheleire and would use a uClibc (you-see-lib-see) and an SDK (ess-dee-kay).

Regards,


Will

> -----Original Message-----
> From: buildroot-bounces at busybox.net [mailto:buildroot-bounces at busybox.net] On
> Behalf Of Thomas Petazzoni
> Sent: 07 February 2012 21:46
> To: buildroot at uclibc.org
> Subject: [Buildroot] Reviewing the Buildroot ELC presentation slides
> 
> Hello,
> 
> I have posted at http://free-electrons.com/~thomas/pub/buildroot.pdf
> the current version of the slides I intend to present next week at the
> ELC in San Francisco.
> 
> For the record, the conference abstract is:
> https://events.linuxfoundation.org/events/embedded-linux-conference/petazzoni
> 
> I would be very interested in your comments and review, both on details
> (typos, mistakes) but also on the overall contents of the slides.
> 
> Thanks,
> 
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

[Buildroot] Reviewing the Buildroot ELC presentation slides

[Thomas Petazzoni]

Hello,

Le Tue, 7 Feb 2012 22:46:11 +0100,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :

> I would be very interested in your comments and review, both on
> details (typos, mistakes) but also on the overall contents of the
> slides.

Thanks for all the comments I received. I have taken into account these
comments, and I am also extending a bit the presentation. I will post
the final slides after the presentation.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com