[Buildroot] [PATCH V2 1/2] tcl: add support for static builds

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Sat Mar 7 15:35:01 UTC 2015

Dear Vicente Olivert Riera,

On Sat, 7 Mar 2015 16:05:17 +0100, Vicente Olivert Riera wrote:

> If you have a package that depends on tcl (it links against libtcl8.6.a,
> for instance), then you will need the target tcl (actually the staging
> one), which has the right architecture for your target, no? The host tcl
> would have the same architecture as the host machine which may not be
> the same as the target one.
> Am I missing anything?

Yes: you still haven't answered whether the 'packages' thing in TCL is
important or not. Yes, your tcl static linking thing is *building*
properly. But does it work? Does the result actually make sense? You've
solved the static linking case by simply not building everything. What
guarantees you that the result is something that works?

Since it seems you actually don't know what TCL is and how it works
(and neither do I), I'd prefer to mark it !BR2_STATIC_LIBS, and let
someone actually interested in using TCL in a statically linked
scenario take care of implementing this.


Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering

More information about the buildroot mailing list