Build failure

[TheGingerNut]

For a long time Now I've been having problems trying to build dolphin from the source on github. I can't find the issue on google or anywhere. anyone got a clue whats going on?

/home/pi/Downloads/dolphin/Source/Core/Core/ConfigManager.cpp: In member function ‘void SConfig::LoadAutoUpdateSettings(IniFile&)’:
/home/pi/Downloads/dolphin/Source/Core/Core/ConfigManager.cpp:670:53: error: ‘SCM_UPDATE_TRACK_STR’ was not declared in this scope
section->Get("UpdateTrack", &m_auto_update_track, SCM_UPDATE_TRACK_STR);
^~~~~~~~~~~~~~~~~~~~
/home/pi/Downloads/dolphin/Source/Core/Core/ConfigManager.cpp:670:53: note: suggested alternative: ‘SCM_DESC_STR’
section->Get("UpdateTrack", &m_auto_update_track, SCM_UPDATE_TRACK_STR);
^~~~~~~~~~~~~~~~~~~~
SCM_DESC_STR

[JonnyH]

This symbol should be provided by a cmake-generated file - if you're doing an incremental build (IE from a non-empty build directory) it may not be correctly be tracking dependencies - maybe completely remove the current build directory and rebuild from scratch?

[TheGingerNut]

(06-29-2018, 09:25 AM)JonnyH Wrote: This symbol should be provided by a cmake-generated file - if you're doing an incremental build (IE from a non-empty build directory) it may not be correctly be tracking dependencies - maybe completely remove the current build directory and rebuild from scratch?

I do that literally every time I build. To the point where I just put my build directory on a ram file system. It solved an issue of some sort in times gone by. can't remember why I do it anymore.

[JonnyH]

Ok, after running cmake is there a "scmrev.h" file in the build directory, under Source/Core/Common/scmrev.h? Does it contain a "#define SCM_UPDATE_TRACK_STR" line?

If not - make sure your git repo is up to date, and you don't have any outstanding changes (IE run "git status").

If the file does exist and there is that line, then there's likely a conflicting "scmrev.h" somewhere in one of your systems include path - it may be in the dolphin git tree (again, "git status" will tell you of any untracked files), or you've somehow ended up with one in your system include path. Which would be pretty weird.

[TheGingerNut]

(06-29-2018, 09:31 AM)JonnyH Wrote: Ok, after running cmake is there a "scmrev.h" file in the build directory, under Source/Core/Common/scmrev.h? Does it contain a "#define SCM_UPDATE_TRACK_STR" line?

If not - make sure your git repo is up to date, and you don't have any outstanding changes (IE run "git status").

If the file does exist and there is that line, then there's likely a conflicting "scmrev.h" somewhere in one of your systems include path - it may be in the dolphin git tree (again, "git status" will tell you of any untracked files), or you've somehow ended up with one in your system include path. Which would be pretty weird.

Yes. #define SCM_UPDATE_TRACK_STR "" to be precise.

[TheGingerNut]

So I just had my first successful build in about six months (I think), and in part thanks to this thread. I did two things differently. firstly, there was a pre existing version of scmrev.h in the git tree. I deleted that. secondly, the file generated contained a space on the line before #define SCM_UPDATE_TRACK_STR "". that got deleted also. not sure which fixed the problem. thanks for your help though.

Edit: Okay I just ran builds without both of these changes and both times it compiled just fine. Guess what made the difference is the git pull before I started. kudos to the dolphin developers for the bugfix.