MONSTA Posted May 23, 2010 Report Share Posted May 23, 2010 Hey everyone. I have a fully working Core with GM5, but I'd like to swap the GM5 to EEPROM mode so I can name the Midi Device and change it's I/Os to 1 (I know I can do this physically, but I'm going to be using two GM5's so want them named properly as well). I've installed GPUTILS and SDCC which both seem to be installed properly, but when I download the SVN of mbhp_usb_gm5_eeprom and try to run "make" in terminal, I get this error: Makefile:28: /include/makefile/common.mk: No such file or directory Makefile:31: /modules/app_lcd/dummy/app_lcd.mk: No such file or directory Makefile:34: /modules/iic_eeprom8/iic_eeprom8.mk: No such file or directory make: *** No rule to make target `/modules/iic_eeprom8/iic_eeprom8.mk'. Stop. Is the SVN thats up correct, or is my install borked? Thanks for any help Peeps Monsta Quote Link to comment Share on other sites More sharing options...
Janis1279 Posted May 23, 2010 Report Share Posted May 23, 2010 (edited) I found this info : Hint: it's possible to give each MIDI port it's own name by editing the [strings] section in the midibox.org_gm5.inf file. Example: WDM.MIDI_1.szPname="MIDIbox SID (1)" WDM.MIDI_2.szPname="MIDIbox FM (2)" WDM.MIDI_3.szPname="MIDIbox SEQ (3)" WDM.MIDI_4.szPname="MIDIbox Stribe (4)" WDM.MIDI_5.szPname="Keyboard (5)" <P class=INFO>This helps you to organize your MIDI ports, so that they are easier to find: Edited May 23, 2010 by Janis1279 Quote Link to comment Share on other sites More sharing options...
TK. Posted May 23, 2010 Report Share Posted May 23, 2010 Is the SVN thats up correct, or is my install borked? You have to set the following two environment variables to the path of your mios/trunk directory. Example: export MIOS_PATH=~/svn/mios/trunk export MIOS_BIN_PATH=$MIOS_PATH/bin [/code] (~ is a shortcut to your /Users/<your-login> directory) The export commands can be executed in the same shell where you will execute "make". Alternatively you can enter the commands into your ~/.bash_profile file, so that they will be executed whenever a new terminal is opened. Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
MONSTA Posted May 24, 2010 Author Report Share Posted May 24, 2010 Thanks Thorsten, I'll check that out tonight. Monsta Quote Link to comment Share on other sites More sharing options...
MONSTA Posted May 31, 2010 Author Report Share Posted May 31, 2010 Ok thanks TK, as usual! Adding those two lines to my bash_profile worked perfectly. I haven't tested the result on the Core/GM5 yet, hopefully I'll get the chance tonight/tomorrow, but the "make" works fine now. Monsta Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.