Skip to content

RFC Convert toolchain backends to packages to fix source/external-deps/legal-info

Thomas Petazzoni buildroot 1 version New

Get series with b4
b4 am 20130906103847.662e1463@skate

Versions newest first

  1. v1 RFC Latest0 of 11 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 11 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Buildroot] [RFCv1 00/11] Convert toolchain backends to packages to fix source/external-deps/legal-info

Dear J?r?me Pouiller,

Quoted 6 lines · J?r?me Pouiller
Quoted 4 lines

To do so, the idea of this patch is to:

(1) Create a 'toolchain' virtual package, which will depend on the particular toolchain backend depending on the configuration.

Is it too early to move toolchain/ to package/? Or there is a reason to keep toolchain/ out of package/?

Well, we do have packages outside of package/, such as the kernel and bootloaders. I believe it makes sense to keep the toolchain backends in toolchain/. Besides, the toolchain-buildroot/ package is really just an indirection for host-gcc-final. Only the toolchain-external/ package really contains some real stuff.

Best regards,

Thomas

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