diff options
author | patacongo <patacongo@7fd9a85b-ad96-42d3-883c-3090e2eb8679> | 2012-06-22 18:58:24 +0000 |
---|---|---|
committer | patacongo <patacongo@7fd9a85b-ad96-42d3-883c-3090e2eb8679> | 2012-06-22 18:58:24 +0000 |
commit | 781b6644f9f46c979bf36dfecd8c69546513da12 (patch) | |
tree | 08f291a3ee94a94aa3bdef50c85a4d671083a199 /nuttx/configs/sure-pic32mx | |
parent | 2de97769f836de2f163158570858505d46023b2b (diff) |
Add support for the microchipOpen toolchain
git-svn-id: https://nuttx.svn.sourceforge.net/svnroot/nuttx/trunk@4864 7fd9a85b-ad96-42d3-883c-3090e2eb8679
Diffstat (limited to 'nuttx/configs/sure-pic32mx')
-rw-r--r-- | nuttx/configs/sure-pic32mx/README.txt | 16 |
1 files changed, 14 insertions, 2 deletions
diff --git a/nuttx/configs/sure-pic32mx/README.txt b/nuttx/configs/sure-pic32mx/README.txt index 594dad59b3..32f93ba00a 100644 --- a/nuttx/configs/sure-pic32mx/README.txt +++ b/nuttx/configs/sure-pic32mx/README.txt @@ -261,9 +261,21 @@ Toolchains Building MicrochipOpen (on Linux) 1) Get the build script from this location: - http://microchipopen.svn.sourceforge.net/viewvc/microchipopen/ccompiler4pic32/buildscripts/trunk/ + + http://microchipopen.svn.sourceforge.net/viewvc/microchipopen/ccompiler4pic32/buildscripts/trunk/ + 2) Build the code using the build script, for example: - ./build.sh -b v105_freeze + + ./build.sh -b v105_freeze + + This will check out the selected branch and build the tools. + + 3) Binaries will then be available in a subdirectory with a name something like + pic32-v105-freeze-20120622/install-image/bin (depending on the current data + and the branch that you selected. + + Note that the tools will have the prefix, mypic32- so, for example, the + compiler will be called mypic32-gcc. This will check out the selected branch and build the tools. |