3 ms·
hehe, thx for the quick reply. Had some trouble with qtdeploy and since go build worked (and I prefer go build workflow wise) I assumed it would result in the s
by JepZ 10y ago
hehe, thx for the quick reply. Had some trouble with qtdeploy and since go build worked (and I prefer go build workflow wise) I assumed it would result in the same binary.
The demo application works without any of the libs from the deploy folder, but thats probably because it uses the system libs.
So cool:
- Option 1: 'go build' creates one large 50mb binary
- Option 2: 'qtdeploy' creates a bundle with a little more than whats required but you can remove what you dont need
- Option 3: just takes the binary and let the system provide the libs
Super cool would be, if that downsizing could be made automatically but since that icu stuff takes alone 24mb, that might be difficult. Anyway, great work. Spend half a day to get it working with system libs, but in the end I had to learn to just follow the tutorial and download qt again.
Great job :-)
- therecipe 10y agoThank you :) I should probably mention that Option 1 is still depending on all the system/dynamic libs. And therefore only usefull to save time during development or if you need more control about the build. If you want to get a smaller binary, run `qtminimal` and `go build/run -tags=minimal` to include only the necessary C++ code, but the binary will still depend on the dynamic/system libs. I will add full statically linking in the future, but probably only after Qt 5.8 is released.