pcbatterij Posted December 26, 2014 Report Share Posted December 26, 2014 Hey all, Has anybody had a problem compiling the seq V4 firmware with the ui_store_file_required ? I keep having "UNDIFINED REFERENCE TO 'ui_store_file_required' I am using the latest files on the SVN? does anybody have an idea what this might couse? cheers, Jef Quote Link to comment Share on other sites More sharing options...
pcbatterij Posted December 26, 2014 Author Report Share Posted December 26, 2014 I have looked further and my guess is that in ui.c there should also be: u8 ui_store_file_required; cheers, Quote Link to comment Share on other sites More sharing options...
kpete Posted December 26, 2014 Report Share Posted December 26, 2014 Jef - I don't know whats going on with this but I find the define located in "seq_ui.c" file with a reference in "seq_ui.h". The revision header for seq_ui.c is: // $Id: seq_ui.c 2102 2014-12-15 17:40:04Z tk $ I got this information directly from the SVN.MIOS32 repositories on line. Are you using version 2102 for that file which was changed on 15-Dec? Pete Quote Link to comment Share on other sites More sharing options...
pcbatterij Posted December 26, 2014 Author Report Share Posted December 26, 2014 Pete, thx for the reply. I have been having a few problems with SVN, but I can see the latest version now, and you are right it was already in there. my bad cheers, Jef Quote Link to comment Share on other sites More sharing options...
kpete Posted December 27, 2014 Report Share Posted December 27, 2014 (edited) I understand about your problems with the SVN. I just don't have enough experience in using it. The most I have done is do diff's between the original version that is stored on my PC. I'm too afraid to try to do an update in my sandbox for fear that I will have problems with merging changes in the same files that others have changed. From my previous knowledge with version control systems I know it can be done but I just don't need it for what I am doing. It is nice that TK has used a naming convention that helps pin point where the variable or function is located. Pete Edited December 27, 2014 by kpete Quote Link to comment Share on other sites More sharing options...
TK. Posted December 30, 2014 Report Share Posted December 30, 2014 Here a hint how you can retrieve the changes from an "official place" in order to get an impression about possible reasons for such issues. Go to http://svnmios.midibox.org Select the MIOS32 repository, and then click on the "View logs" button. Check the comments, they are sometimes helpful. Select the potential problematic version with a "known good" one, or whatever you want to compare. Then click on the "show changed files" button: This gives you a nice looking diff over all changes: And with some luck you will find out quickly, that the variable has been declared in seq_ui.c :) I'm using this web based method as well whenever somebody reports a problem after firmware changes in order to find out what I did ;-) Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
pcbatterij Posted January 2, 2015 Author Report Share Posted January 2, 2015 thx Thorsten, Happy New year Jef 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.