-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build time #261
Comments
also I suppose this might be related to #252 |
I've timed the total build of my program with clean cache ( cimgui-go: 13m52.693s inkyblackness: 10m17.397s 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 |
|
here is a command that takes so many time: TERM='dumb' CGO_LDFLAGS='' /usr/local/go/pkg/tool/linux_amd64/cgo -objdir $WORK/b056/ -importpath github.com/AllenDang/cimgui-go/imgui "-ldflags=\"-O2\" \"-g\" \"/home/me/git/cimgui-go/imgui/../lib/linux/x64/cimgui.a\"" -- -DCIMGUI_DEFINE_ENUMS_AND_STRUCTS -I $WORK/b056/ -O2 -g ./assert.go ./cflags.go ./cimgui_funcs.go ./cimgui_typedefs.go ./clipboard.go ./extra_types.go ./input_text.go ./type_accessor.go ./util.go so this seems to be a |
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?
The text was updated successfully, but these errors were encountered: