MIDIbox

User Tools

Site Tools

Trace:
installing_gnu_on_osx

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
installing_gnu_on_osx [2009/11/03 10:03] – baptistouinstalling_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 54: Line 54:
 Your compiler also uses the shell to access to the different files involved. Thus, it has to know where to find these files.  For this, we set up variables in the shell. For example, we will put the path of your mios32 folder in the variable "MIOS32_PATH" so that when the compiler will want to check inside your "mios32" folder, it will just call this variable. Your compiler also uses the shell to access to the different files involved. Thus, it has to know where to find these files.  For this, we set up variables in the shell. For example, we will put the path of your mios32 folder in the variable "MIOS32_PATH" so that when the compiler will want to check inside your "mios32" folder, it will just call this variable.
  
-Setting up path variables in the shell is quite easy: in a terminal window just type "export VARIABLE_NAME=something"+Setting up path variables in the shell is quite easy: in a terminal window just type\\  
 +''export VARIABLE_NAME=something''\\ 
 and if you want to check to what the variable has been assigned, type:\\  and if you want to check to what the variable has been assigned, type:\\ 
 ''echo $VARIABLE_NAME''\\  ''echo $VARIABLE_NAME''\\ 
Line 66: 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 100: 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\\ 
Line 107: Line 108:
 export MIOS32_PROCESSOR=STM32F103RE\\  export MIOS32_PROCESSOR=STM32F103RE\\ 
 export MIOS32_BOARD=MBHP_CORE_STM32\\  export MIOS32_BOARD=MBHP_CORE_STM32\\ 
-export MIOS32_LCD=clcd''\\ +export MIOS32_LCD=clcd\\ 
 +echo MIOS32 variables initialized.''\\ 
  
 do "ctrl-O" to save the file\\  do "ctrl-O" to save the file\\ 
 do "ctrl-X" to exit\\  do "ctrl-X" to exit\\ 
  
-log off or shut down your computer\\  +Once you open a new terminal, the variables will be set automatically, and you should see the "MIOS32 variables initialized" message.\\ 
-login of start up the computer\\  +It isn't required to log off or shut down your computer to test this.\\  
-open a terminal window and check if the variables are all set up:\\  +Open a terminal window and check if the variables are all set up by typing:\\  
-''echo MIOS32_PATH'' for example\\  +''echo $MIOS32_PATH'' for example.\\  
-if they are not, that's probably another file you need to edit.\\ +If you don't see the messages (and MIOS32 variables don't exist), that's probably because a .bash_login or .bash_profile already exists (edit only an already existing file - of none exists, use .profile).\\ 
 Useful info about bash and initialisation files here:\\  Useful info about bash and initialisation files here:\\ 
 [[http://johnnywey.wordpress.com/2008/04/17/fixing-bash-profile-in-os-x/|http://johnnywey.wordpress.com/2008/04/17/fixing-bash-profile-in-os-x/]]\\  [[http://johnnywey.wordpress.com/2008/04/17/fixing-bash-profile-in-os-x/|http://johnnywey.wordpress.com/2008/04/17/fixing-bash-profile-in-os-x/]]\\ 
installing_gnu_on_osx.txt · Last modified: 2011/05/21 20:52 by admin