d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
445b5554bf
freebsd-dev/tools/build/options/WITHOUT_CROSS_COMPILER

14 lines
503 B
Plaintext
Raw Normal View History

Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
.\" $FreeBSD$
Drop 'Set to' from most src.conf(5) knobs The description is clearly what effect the knob has when set, so the additional text was unnecessary. Reviewed by: jhb, se Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D29583
2021-04-10 02:23:03 +00:00
Do not build any cross compiler in the cross-tools stage of buildworld.
Clarify some option descriptions, add a line of text to makeman to add the slightest hint of a shade of a clue of what it does. Sponsored by: iXsystems
2017-02-03 19:09:46 +00:00
When compiling a different version of
Whitespace cleanup to fix rendering nits in src.conf(5). Sponsored by: The FreeBSD Foundation
2014-11-26 20:43:09 +00:00
.Fx
Clarify some option descriptions, add a line of text to makeman to add the slightest hint of a shade of a clue of what it does. Sponsored by: iXsystems
2017-02-03 19:09:46 +00:00
than what is installed on the system, provide an alternate
Separate out enabling building clang and/or gcc for the system and building clang and/or gcc as the bootstrap compiler. Normally, the default compiler is used. WITH_CLANG_BOOTSTRAP and/or WITH_GCC_BOOTSTRAP will enable building these compilers as part bootstrap phase. WITH/WITHOUT_CLANG_IS_CC controls which compiler is used by default for the bootstrap phase, as well as which compiler is installed as cc. buildworld now successfully completes building the cross compiler with WITHOUT_CLANG=t and WITHOUT_GCC=t and produces a built system with neither of these included. Similarlly, MK_BINUTILS_BOOTSTRAP controls whether binutils is built during this phase. WITHOUT_CROSS_COMPILER will now force MK_BINUTILS_BOOTSTRAP=no, MK_CLANG_BOOTSTRAP=no and MK_GCC_BOOTSTRAP=no. BOOTSTRAP_COMPILER was considered, but rejected, since pc98 needs both clang and gcc to bootstrap still. It should be revisisted in the future if this requirement goes away. Values should be gcc, clang or none. It could also be a list. The odd interaction with Xfoo cross/external tools needs work, but is beyond the scope of this change as well.
2014-04-18 17:03:58 +00:00
compiler with XCC to ensure success.
Clarify some option descriptions, add a line of text to makeman to add the slightest hint of a shade of a clue of what it does. Sponsored by: iXsystems
2017-02-03 19:09:46 +00:00
When compiling with an identical version of
Whitespace cleanup to fix rendering nits in src.conf(5). Sponsored by: The FreeBSD Foundation
2014-11-26 20:43:09 +00:00
.Fx
Separate out enabling building clang and/or gcc for the system and building clang and/or gcc as the bootstrap compiler. Normally, the default compiler is used. WITH_CLANG_BOOTSTRAP and/or WITH_GCC_BOOTSTRAP will enable building these compilers as part bootstrap phase. WITH/WITHOUT_CLANG_IS_CC controls which compiler is used by default for the bootstrap phase, as well as which compiler is installed as cc. buildworld now successfully completes building the cross compiler with WITHOUT_CLANG=t and WITHOUT_GCC=t and produces a built system with neither of these included. Similarlly, MK_BINUTILS_BOOTSTRAP controls whether binutils is built during this phase. WITHOUT_CROSS_COMPILER will now force MK_BINUTILS_BOOTSTRAP=no, MK_CLANG_BOOTSTRAP=no and MK_GCC_BOOTSTRAP=no. BOOTSTRAP_COMPILER was considered, but rejected, since pc98 needs both clang and gcc to bootstrap still. It should be revisisted in the future if this requirement goes away. Values should be gcc, clang or none. It could also be a list. The odd interaction with Xfoo cross/external tools needs work, but is beyond the scope of this change as well.
2014-04-18 17:03:58 +00:00
to the host, this option may be safely used.
This option may also be safe when the host version of
Whitespace cleanup to fix rendering nits in src.conf(5). Sponsored by: The FreeBSD Foundation
2014-11-26 20:43:09 +00:00
.Fx
Separate out enabling building clang and/or gcc for the system and building clang and/or gcc as the bootstrap compiler. Normally, the default compiler is used. WITH_CLANG_BOOTSTRAP and/or WITH_GCC_BOOTSTRAP will enable building these compilers as part bootstrap phase. WITH/WITHOUT_CLANG_IS_CC controls which compiler is used by default for the bootstrap phase, as well as which compiler is installed as cc. buildworld now successfully completes building the cross compiler with WITHOUT_CLANG=t and WITHOUT_GCC=t and produces a built system with neither of these included. Similarlly, MK_BINUTILS_BOOTSTRAP controls whether binutils is built during this phase. WITHOUT_CROSS_COMPILER will now force MK_BINUTILS_BOOTSTRAP=no, MK_CLANG_BOOTSTRAP=no and MK_GCC_BOOTSTRAP=no. BOOTSTRAP_COMPILER was considered, but rejected, since pc98 needs both clang and gcc to bootstrap still. It should be revisisted in the future if this requirement goes away. Values should be gcc, clang or none. It could also be a list. The odd interaction with Xfoo cross/external tools needs work, but is beyond the scope of this change as well.
2014-04-18 17:03:58 +00:00
is close to the sources being built, but all bets are off if there have
been any changes to the toolchain between the versions.
Reference in New Issue Copy Permalink