Open gucio321 opened 4 months ago
also I suppose this might be related to #252
I've timed the total build of my program with clean cache (go build -a
)
Adding full build logs (-v -x
) to see what's being compiled from cimgui
cimgui-go: 13m52.693s log: cimgui-compile.log
inkyblackness: 10m17.397s log: inky-compile.log
Build with no imgui compiles in similar time as inkyblackness version
Full build script just in case: https://github.com/Wieku/danser-go/blob/dev/dist-win.sh
I'm wondering why, each change to cimgui-go code triggers build of the whole project that takes (on my machine) about 3 minutes (this is a bit long imo). In fact, because we build all shared libraries my question is: why it takes so long to build go project?
If I remember correctly after running go build with extra C flag for debugging it does many things with gcc. It looks that it compiles cimgui anyway?