Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
2
22f330471-1
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Summer2022
22f330471-1
Commits
45b1fc13
Commit
45b1fc13
authored
2 years ago
by
guozhanxin
Browse files
Options
Downloads
Patches
Plain Diff
fixed smart-env.bat on win10
parent
cfb6b2b8
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
smart-env.bat
+2
-2
2 additions, 2 deletions
smart-env.bat
with
2 additions
and
2 deletions
smart-env.bat
+
2
−
2
View file @
45b1fc13
...
...
@@ -9,19 +9,19 @@
@set
RTT_CC
=
gcc
@set
RTT_EXEC_PATH
=
%cd%
\tools\gnu_gcc\arm
-linux-musleabi
_for_i686
-w
64
-mingw
32
\bin
@set
RTT_CC_PREFIX
=
arm
-linux-musleabi
-
@set
PATH
=
%RTT_EXEC_PATH%
;
%PATH%
@copy
configs
\def_config_arm .config
)
else
if
%def_arch%
==
riscv64
(
@set
RTT_CC
=
gcc
@set
RTT_EXEC_PATH
=
%cd%
\tools\gnu_gcc\riscv64
-linux-musleabi
_for_i686
-w
64
-mingw
32
\bin
@set
RTT_CC_PREFIX
=
riscv64
-unknown-linux-musl
-
@set
PATH
=
%RTT_EXEC_PATH%
;
%PATH%
@copy
configs
\def_config_riscv64 .config
)
else
(
@echo
"ERROR:supported_arch=arm riscv64
!
"
@goto
EXIT
)
@set
PATH
=
%RTT_EXEC_PATH%
;
%PATH%
@echo
"Arch =>
%def_arch%
"
@echo
"CC =>
%RTT_CC%
"
@echo
"PREFIX =>
%RTT_CC_PREFIX%
"
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment