Steps to use precompiled toolchain instead of compiling one for every fresh build

[Dharanee]

I want to use precompiled toolchain, instead for building it from scratch for every clean (targetclean/distclean) build. I want to optimize the compile time. Please help

[egc]

You do not have to compile the toolchain for each build, at least I do not do that.

[RuralRoots]

Only targetclean, distclean, and dirclean should clear the directories /build_dir/toolchain* and /staging_dir/toolchain*.

[Dante]

Perhaps you can describe in a bit more detail what you're trying to do and where the recompilation is kicking in?

[Dharanee]

For the first time I compile the code, toolchain is getting compiled. Or if I do targetclean/distclean. The thing is I want to commit the compiled toolchain to keep it remain static and do not want it to get compiled again, even with targetclean.
Do we have any better way to do this ?

[RuralRoots]

@Dharanee

I want to commit the compiled toolchain to keep it remain static and do not want it to get compiled again, even with targetclean.
Do we have any better way to do this ?

You can look in make menuconfig/nconfig Advanced configuration options (for developers) and see if Use external toolchain might be of use to you.

Package the OpenWrt-based Toolchain

CONFIG_MAKE_TOOLCHAIN:

Package the created toolchain as a tarball under the bin/ directory as
OpenWrt-Toolchain-$(BOARD)-for-$(ARCH)$(ARCH_SUFFIX)-gcc-$(GCCV)$(DIR_SUFFIX).
For example, a toolchain for the MIPS architecture might be named
OpenWrt-Toolchain-malta-for-mipsel_mips32-gcc-4.8-linaro_uClibc-0.9.33.2.tar.bz2.

Symbol: MAKE_TOOLCHAIN [=n]
Type : bool
Defined at target/toolchain/Config.in:1
Prompt: Package the OpenWrt-based Toolchain
Depends on: !EXTERNAL_TOOLCHAIN [=n]
Location:
-> Package the OpenWrt-based Toolchain (MAKE_TOOLCHAIN [=n])