[1] https://ccache.samba.org/
Quote
ccache is a compiler cache. It speeds up recompilation by caching previous compilations and detecting when the same compilation is being done again. Supported languages are C, C++, Objective-C and Objective-C++.
Topic: Do I need to compile a wallet each time I do changes to it? (Read 281 times)
There is a tool called Ccache[1] to make the recompiling process faster, It is work to cache a compilation process. If you recompile a program the tool detects if some file has been changed or not, and then reuse the cached file for the unchanged one then recompile the process if changed file found. The first compilation time might run as usual, after the first compilation, the recompilation process will speeds up. CMIIW.
[1] https://ccache.samba.org/
[1] https://ccache.samba.org/
Hi. I was wondering if there's any faster way to see how the wallet is looking like / functioning, than compiling it each time after changes?
Depends on what platform you develop, there are packages where you see live upgrade without the need to compile all packages again, like in xcode
/KX
Yes, you need to always compile it. A lot of things are set dynamically through code and not through the UI forms.
Hi. I was wondering if there's any faster way to see how the wallet is looking like / functioning, than compiling it each time after changes?
Hi,after changes to what ? If you make some changes to the code then you need to recompile in order to apply them to the binary you execute (the software).
I'm talking more of a graphical changes, such as changed icons, font change, icon placements and etc. As I understand that should be possible to do with QT Creator, but I'm unable to load the project somewhy.
Hi. I was wondering if there's any faster way to see how the wallet is looking like / functioning, than compiling it each time after changes?
Hi,after changes to what ? If you make some changes to the code then you need to recompile in order to apply them to the binary you execute (the software).
Hi. I was wondering if there's any faster way to see how the wallet is looking like / functioning, than compiling it each time after changes?
Jump to: