-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
glib:x64-windows-static failing #3409
Comments
Seems to be due to commits 26fabaf ("Disable static builds") and 79a526a Same issue while trying to install
|
Had the same issue trying to use Fluidsynth statically. It says in the comments that Glib requires DLLMain to function so I guess that is the reason. |
I'm running into the same issue when trying to build qt5-base. This is kind of a problem, since Qt can be built statically. |
Is there any detailed explanations what it is all about? Why so many libraries stuck from being statically build because of some weirdness? |
This is a real pain point. Anybody with more information? |
Nothing really. I'll look into the build details when I have time and submit a PR for it |
The symbols: GLIB_STATIC_COMPILATION and GOBJECT_STATIC_COMPILATION seem to allow this? |
any news from anyone? i have tried and failed to fix this |
I have tried but entered an endless rabbit hole, too many dependencies. Also gave up because other builds broke randomly.
…On 22 October 2018 22:09:35 CEST, Oli Larkin ***@***.***> wrote:
any news from anyone? i have tried and failed to fix this
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#3409 (comment)
|
it definitely worked in the past |
GLib doesn't support static build for Windows. See more information here: |
Should it fail the build though? I've seen other times it will force dynamic linking instead and continue. For instance, if you want to build a static version of fluidsynth i.e. fluidsynth:x64-windows-static. Glib is a dependency so it will try to build statically but fail due to the error above. Should it not continue but use it dynamically and the rest statically? Otherwise you need to create a custom triplet, which is a bit of a pain. |
@stekyne To build glib as a static library and link using a static CRT, we will get a
So we need to solve this first. |
ping |
@proTerm Since the official does not provide a method to build static in windows, and function Note to me: glib and gobject should be installed to the |
I hope that a solution would be found. |
@JackBoosY and @NancyLi1013
|
This is not a bug, GLib doesn't support static linking on Windows yet. There's a merge request upstream but GLib doesn't have many Windows maintainers, so it's just sitting there going stale |
Its not a bug, its a feature ;) For a moment I had thought, this issue has been resolved ... (On the other hand, its such a pity that this issue is not being prioritized by the vcpkg team). Thanks for the answer! |
I mean, the vcpkg team can't do anything about this. GLib just doesn't work when linked statically, it has to be fixed upstream |
@JackBoosY Im surprised you closed the issue, although it would never be resolved ... ? |
actually trying to install cairo x64 static, which previously worked
-- CURRENT_PORT_DIR=C:/Users/oli/Dev/vcpkg/ports/glib/.
Glib relies on DllMain and therefore cannot be built statically
CMake Error at C:/Users/oli/Dev/vcpkg/ports/glib/portfile.cmake:13 (message):
Glib only supports dynamic library and crt linkage
Error: Building package glib:x64-windows-static failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with
.\vcpkg update
, thensubmit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: glib:x64-windows-static
Vcpkg version: 0.0.110-2018-05-02-1e41c4377f38512d1d6c0d65a2e7b9c7c8b03bea
The text was updated successfully, but these errors were encountered: