[Buildroot] Crosstool/Buildroot integration issue

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Thu Jul 8 07:34:56 UTC 2010

On Wed, 7 Jul 2010 19:19:28 +0200
"Yann E. MORIN" <yann.morin.1998 at anciens.enib.fr> wrote:

> Well, I'd rather we had something like:
> - in menuconfig:
>     () Additional dirs to copy from sysroot
>       Help:
>         This is a space-separated list of paths that you want to copy
>         from the sysroot to the target. Make the paths relative to the
>         sysroot. Example:
>           /usr/lib/gconv /usr/include
> - and in ext-tool.mk (to replace your changes, above):
>   $(Q)for d in $(BR_EXT_TOOL_DIRS_EXTRA); do \
>         if [ -d "$(ARCH_SYSROOT_DIR)$${d}" ]; then
>           mkdir -p "$(TARGET_DIR)$${d}"
>           cp -a "$${d}/." "$(TARGET_DIR)${d}/."
>         else
>           echo "No such directory '$${d}' whiel trying to copy from sysroot"
>         fi
>       done
> But that's just my 2-cent advice...

At first look, I'm not a big fan of this solution, as it requires a lot
of knowledge from the Buildroot user about dependency details that
precisely Buildroot is supposed to handle.

I'd prefer to understand why and when these gconv files are needed, and
depending on that, see how it should fit in our configuration system.

Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.

More information about the buildroot mailing list