diff options
author | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2010-11-06 23:41:08 +0000 |
---|---|---|
committer | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2010-11-06 23:41:08 +0000 |
commit | 3edff1ad69048b7624d4c6958574cc61dca0fdfa (patch) | |
tree | 99d2e4f16cccfec2bb054ca2c89592434ee3fb8d /nuttx/configs/avr32dev1 | |
parent | 8d211855925c1300513dc0e022981c4cd4cb256b (diff) | |
download | px4-nuttx-3edff1ad69048b7624d4c6958574cc61dca0fdfa.tar.gz px4-nuttx-3edff1ad69048b7624d4c6958574cc61dca0fdfa.tar.bz2 px4-nuttx-3edff1ad69048b7624d4c6958574cc61dca0fdfa.zip |
README update
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@3087 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/configs/avr32dev1')
-rwxr-xr-x | nuttx/configs/avr32dev1/README.txt | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/nuttx/configs/avr32dev1/README.txt b/nuttx/configs/avr32dev1/README.txt index 8b3cc271a..209ec4f68 100755 --- a/nuttx/configs/avr32dev1/README.txt +++ b/nuttx/configs/avr32dev1/README.txt @@ -297,13 +297,15 @@ Make Tip ^^^^^^^^
Because this build uses a native Windows toolchain and the native Windows
- does not understand Cygwin/POSIX paths, the NuttX make sysem does something
- weird: It copies the configuration directories instead of simply linking
- to them (it could, perhaps, use the NTFS mklink command, but it doesn't).
-
- A consequence of this is that you can easily get confused and get editting
- a file in one of the linked directories, re-build, and not see your changes.
- To work around this annoying behavior, I also do the following when I make:
+ tools do not understand Cygwin's symbolic links, the NuttX make system does
+ something weird: It copies the configuration directories instead of linking
+ to them (it could, perhaps, use the NTFS 'mklink' command, but it doesn't).
+
+ A consequence of this is that you can easily get confused when you edit
+ a file in one of the "linked" directories, re-build NuttX, and then not see your
+ changes when you run the program. That is because build is still using the
+ version of the file in the copied directory, not your modified file! To work
+ around this annoying behavior, do the following when you re-build:
make clean_context all <-- Remove and re-copy all of the directories, then make all
doisp.sh <-- Load the code onto the board.
|