-
Notifications
You must be signed in to change notification settings - Fork 78
fix(linux): Standardize CC ENV setup instructions #617
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jmenti
wants to merge
1
commit into
TexasInstruments:master
Choose a base branch
from
jmenti:toolchain-updates
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
New warnings found with rstcheck: |
7e69b87 to
eba21cd
Compare
|
New warnings found with rstcheck: |
StaticRocket
requested changes
Jan 14, 2026
Cross compile environment is similar across u-boot, TF-A, OPTEE, and Linux builds. Move step by step instructions into GCC_ToolChain RST and reference from other build guides using include directive. Since the CC ENV instructions export CC path using $CROSS_COMPILE_32 and $CROSS_COMPILE_64, use these in legacy build guides as well. Signed-off-by: Judith Mendez <[email protected]>
eba21cd to
d90ac80
Compare
|
New warnings found with rstcheck: |
StaticRocket
requested changes
Jan 15, 2026
Comment on lines
+51
to
+52
| .. important:: | ||
| When using the GCC toolchain provided with the SDK or stand alone from TI that you do |
Member
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
| .. important:: | |
| When using the GCC toolchain provided with the SDK or stand alone from TI that you do | |
| .. important:: | |
| When using the GCC toolchain provided with the SDK or stand alone from TI that you do |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cross compile environment is similar across u-boot, TF-A, OPTEE, and Linux builds. Move step by step instructions into GCC_ToolChain RST and reference from other build guides using include directive.
Since the CC ENV instructions export CC path using $CROSS_COMPILE_32 and $CROSS_COMPILE_64, use these in legacy build guides as well.