You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is probably an incredibly difficult topic. There are several places with references with the name Bitcoin Core, links to bitcoin.org, file names, images, ... which are not fully rebranded.
Simply renaming everything could have very significant consequences, for example QT uses the application and organization names to write and read settings, stored in the system registry on Windows, in XML preferences files on Mac OS X and usually somewhere in INI files on Unix systems. There are also installation and deinstallation routines, icons, start menu entries ...
Some, and likely not all, files or even whole locations involved here:
d9f6269 Log additional information during startup and shutdown (dexX7)
46383c5 Rename log function file_log() to PrintToLog() (dexX7)
435c8d2 Support user defined log file via "--omnilogfile" (dexX7)
7b5049e Initialize Omni Core debug log levels explicitly (dexX7)
2ef69b6 Print error message, if creating the debug log file failed (dexX7)
7a78b01 LOG: Move --omnidebug startup option to log.cpp and add all/none options (zathras-crypto)
8a9b3ff DEBUG: Allow debug levels to be specified without needing to recompile (zathras-crypto)
This is probably an incredibly difficult topic. There are several places with references with the name Bitcoin Core, links to bitcoin.org, file names, images, ... which are not fully rebranded.
Simply renaming everything could have very significant consequences, for example QT uses the application and organization names to write and read settings, stored in the system registry on Windows, in XML preferences files on Mac OS X and usually somewhere in INI files on Unix systems. There are also installation and deinstallation routines, icons, start menu entries ...
Some, and likely not all, files or even whole locations involved here:
I seriously have no idea how to handle this. especially because it could turn into a nightmare when migrating to another code base.
The text was updated successfully, but these errors were encountered: