installing_gnu_on_osx
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
installing_gnu_on_osx [2009/11/03 22:17] admin |
installing_gnu_on_osx [2010/11/30 20:10] philetaylor |
||
|---|---|---|---|
| Line 38: | Line 38: | ||
| ===2- install the STM32 toolchain=== | ===2- install the STM32 toolchain=== | ||
| - | A nice pre-built binaries archive can be found at this page: "www.paintyourdragon.com/uc/osxstm32/index.html".\\ | + | The MIDIbox community have created a modified GNU Compiler Collection, ready for use with the ARM Cortex M3 platform. The toolchain contains all of the tools required to build MIOS32 applications including GCC and NEWLIB. |
| - | You don't need to do everything written on this page as we won't use Circle OS and FatFryer.\\ | + | |
| - | Just download the pre-built binaries in the section "acquiring the software". These will work on OS X 10.5, for earlier OS version you'll probably have to download the source files and compile them, I haven't checked how you do that.\\ | + | |
| - | Expand the archive, you will then have a "stm32-bin" folder containing another archive file and a "README" file. Follow the instructions given in the "README" file to set up the toolchain.\\ | + | |
| - | Check that all the files expanded properly in your /usr folder.\\ | + | |
| - | The trick is that the /usr folder is hidden by the finder so if you want to open it, in the finder's menu click on "go" -> "go to folder" and just type "/usr" in the pop up window, your "/usr" folder will open and you'll be able to check the files. You should have a folder called "stm32" inside the "local" folder. | + | |
| - | Personally I tried to expand the files with the terminal as said in the "README" but it didn't work, don't know why. I just double clicked the archive and it all expanded in a new "usr" directory made in the same folder as the archive. I then opened this folder and its "local" subfolder, copied the "stm32" subfolder inside the real "/usr/local" folder of my computer and it worked fine. | + | The Toolchain has currently been compiled for Windows (2000+), Mac OS X (Leopard or newer) and Linux x86 (built on Ubuntu 10.10). |
| - | You now need to set the path variable for the toolchain, see the next section about this | + | |
| + | The download directory for the toolchain is ftp://ftp.lansystems.co.uk/pub/midibox | ||
| + | |||
| + | Download the latest "macos" file and unzip into your favorite directory, If you unzip into /usr/local the toolchain will create /usr/local/mios32_toolchain and various sub-directories containing the toolchain files. | ||
| + | |||
| + | You now need to set the path variable for the toolchain bin directory (/usr/local/mios32_toolchain/bin), see the next section about this | ||
| ===3- set up the paths variables=== | ===3- set up the paths variables=== | ||
| Line 67: | Line 67: | ||
| In our case, we need to set up the path variable for the STM32 toolchain: | In our case, we need to set up the path variable for the STM32 toolchain: | ||
| type in the terminal\\ | type in the terminal\\ | ||
| - | ''export PATH=$PATH:/usr/local/stm32/bin''\\ | + | ''export PATH=$PATH:/usr/local/mios32_toolchain/bin''\\ |
| and then we need to set up variables for mios32 itself:\\ | and then we need to set up variables for mios32 itself:\\ | ||
| ''export MIOS32_PATH=~/svn/mios32/trunk\\ | ''export MIOS32_PATH=~/svn/mios32/trunk\\ | ||
| Line 101: | Line 101: | ||
| then copy and paste these lines inside the pico editor:\\ | then copy and paste these lines inside the pico editor:\\ | ||
| - | ''export PATH=$PATH:/usr/local/stm32/bin\\ | + | ''export PATH=$PATH:/usr/local/mios32_toolchain/bin\\ |
| export MIOS32_PATH=~/svn/mios32/trunk\\ | export MIOS32_PATH=~/svn/mios32/trunk\\ | ||
| export MIOS32_BIN_PATH=$MIOS32_PATH/bin\\ | export MIOS32_BIN_PATH=$MIOS32_PATH/bin\\ | ||
installing_gnu_on_osx.txt · Last modified: 2011/05/21 20:52 by admin
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
