Peter Lindener Posted July 6, 2011 Report Share Posted July 6, 2011 Sorry for being a newbie...and thus needing to ask questions that might sound dumb for know there way around the MidiBox sight.... can someone clue me in..? 1. I'm trying to understand the details of how MIOS32 is linked into an application binary... 2. Is there a description of how to do software development using the preferred software tool chain(s). 3. How does one go about extending the MIOS32 library's functionality...is there a GIT hub, for submission of code that one might propose could go into the more formal MIOS32 release ?... 4. Does MIOS32 currently have a version numbering system, how does the community handle experimental branching of the source tree. 5. Is the idea that more than one MIOS App may be supported to run concurrently (dynamically scheduled, both in memory), with shared Midi-stream routing, under consideration? 6. Has there been any entertainment of taking MISO towards dynamically linked shared librarys? Quote Link to comment Share on other sites More sharing options...
TK. Posted July 6, 2011 Report Share Posted July 6, 2011 Sorry for being a newbie...and thus needing to ask questions that might sound dumb for know there way around the MidiBox sight.... can someone clue me in..? 1. I'm trying to understand the details of how MIOS32 is linked into an application binary... 2. Is there a description of how to do software development using the preferred software tool chain(s). 3. How does one go about extending the MIOS32 library's functionality...is there a GIT hub, for submission of code that one might propose could go into the more formal MIOS32 release ?... See http://www.ucapps.de/mios32_c.html Each tutorial contains a README which describes some details - step by step The complete code is available on our subversion server If you are missing details in the Wiki, help to improve it! 4. Does MIOS32 currently have a version numbering system, how does the community handle experimental branching of the source tree. MIOS32 is very modular, changes in my own sources are aligned with me, experimental changes can be done in separate directories or svn branches (if really required) 5. Is the idea that more than one MIOS App may be supported to run concurrently (dynamically scheduled, both in memory), with shared Midi-stream routing, under consideration? It's possible at application level, especially if the C++ flow is used. I for myself don't plan to do this work due to other plans. 6. Has there been any entertainment of taking MISO towards dynamically linked shared librarys? Not required, as the compile flow is very fast, and sources are sometimes using hardcoded parameters selected via #ifdef/#if to simplify customizations. Creating libraries would lead to higher RAM consumption and too many variations - no real advantage. Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
Peter Lindener Posted July 6, 2011 Author Report Share Posted July 6, 2011 Hi Thorsten - Maybe you should have linked me to Here: http://www.midibox.org/dokuwiki/windows_toolchain_svn or http://www.midibox.org/dokuwiki/doku.php?id=windows_mios32_toolchain_core&s I had already looked where you suggested: See http://www.ucapps.de/mios32_c.html...'>http://www.ucapps.de/mios32_c.html... It could be clearer at the top level web page where to look....maybe this is just about newbie usability... I did mange to find these other links via other peoples posting on the MidiBox form.... so the docs are there...Just not so clearly visible when navigating from the root web pages. Looking real good! all the best -Peter See http://www.ucapps.de/mios32_c.html Each tutorial contains a README which describes some details - step by step The complete code is available on our subversion server If you are missing details in the Wiki, help to improve it! MIOS32 is very modular, changes in my own sources are aligned with me, experimental changes can be done in separate directories or svn branches (if really required) It's possible at application level, especially if the C++ flow is used. I for myself don't plan to do this work due to other plans. Not required, as the compile flow is very fast, and sources are sometimes using hardcoded parameters selected via #ifdef/#if to simplify customizations. Creating libraries would lead to higher RAM consumption and too many variations - no real advantage. Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
TK. Posted July 6, 2011 Report Share Posted July 6, 2011 Maybe you should have linked me to Here: http://www.midibox.org/dokuwiki/windows_toolchain_svn or http://www.midibox.org/dokuwiki/doku.php?id=windows_mios32_toolchain_core&s I could have linked you there if you would have told me that you are a Windows user. A linux or MacOS user would be confused, or would think that Windows is required to run the toolchain, which isn't true. I had already looked where you suggested: See http://www.ucapps.de/mios32_c.html... It could be clearer at the top level web page where to look....maybe this is just about newbie usability... I did mange to find these other links via other peoples posting on the MidiBox form.... so the docs are there...Just not so clearly visible when navigating from the root web pages. Since MIDIbox is a long-term project, we've all time of the world to improve the docs ;) But thanks for the suggestions (of course) Best Regards, Thorsten. 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.