summaryrefslogtreecommitdiff
path: root/nuttx/configs/ez80f910200kitg/README.txt
diff options
context:
space:
mode:
Diffstat (limited to 'nuttx/configs/ez80f910200kitg/README.txt')
-rw-r--r--nuttx/configs/ez80f910200kitg/README.txt18
1 files changed, 15 insertions, 3 deletions
diff --git a/nuttx/configs/ez80f910200kitg/README.txt b/nuttx/configs/ez80f910200kitg/README.txt
index 222a25db1..004f607d4 100644
--- a/nuttx/configs/ez80f910200kitg/README.txt
+++ b/nuttx/configs/ez80f910200kitg/README.txt
@@ -107,8 +107,20 @@ available:
CONFIG_APPS_DIR="..\apps"
- NOTE: If you need to change the toolchain path used in Make.defs,
- you will need to use the short 8.3 filenames to avoid spaces. On
- my change C:\PROGRA~1\ is C:\PROGRA~2\ is C:\Program Files (x86)\
+ NOTES:
+
+ a. If you need to change the toolchain path used in Make.defs, you
+ will need to use the short 8.3 filenames to avoid spaces. On my
+ PC, C:\PROGRA~1\ is is C:\Program Files\ and C:\PROGRA~2\ is
+ C:\Program Files (x86)\
+ b. You can't use setenv.sh in the native Windows environment. Try
+ scripts/setenv.bat instead.
+ c. At present, the native Windows build fails at the final link stages.
+ The failure is due to problems in arch/z80/src/nuttx/linkcmd that
+ is autogenerated by arch/z80/src/Makefile.zdsii. The basic program
+ is the spurious spaces and and carrirage returns are generated at
+ the end of the lines after a line continuation (\ ^M). If these
+ trailing bad characters are manually eliminated, then the build
+ will succeed on the next try.
Check out any README.txt files in these <sub-directory>s.