Skip to content
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] build failure #41205

Open
wmjb opened this issue Sep 26, 2024 · 5 comments
Open

[glib] build failure #41205

wmjb opened this issue Sep 26, 2024 · 5 comments
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@wmjb
Copy link

wmjb commented Sep 26, 2024

Operating system

windows-arm

Compiler

msvc

Steps to reproduce the behavior

vcpkg install glib --triplet=arm-windows

Failure logs

missing linking with three libraries - advapi32.lib, shell32.lib ole32.lib.

Additional context

manually adding these link arguments to the ninja build file results in success. how can the port files be modified to include these? so when a glib is built as part of another package it can succeed?

@wmjb wmjb added the category:port-bug The issue is with a library, which is something the port should already support label Sep 26, 2024
@wmjb
Copy link
Author

wmjb commented Sep 26, 2024

also package cairo is missing ole32.lib for arm-windows

@wmjb
Copy link
Author

wmjb commented Sep 26, 2024

also package pango is missing advapi32.lib for arm-windows

@wmjb
Copy link
Author

wmjb commented Sep 26, 2024

also sassc missing shell32.lib for arm-windows

@wmjb
Copy link
Author

wmjb commented Sep 26, 2024

also gtk3 missing Gdi32.lib shell32.lib ole32.lib advapi32.lib comdlg32.lib Winspool.lib for arm-windows

is there some global settings for vcpkg on a per triplet basis?

@LilyWangLL LilyWangLL self-assigned this Sep 27, 2024
@dg0yt
Copy link
Contributor

dg0yt commented Sep 27, 2024

Do you really want to target 32-bit arm instead of arm64?

Please show proper error logs.
glib is built with meson.
For windows, vcpkg normally passes implicit link libraries as initialized in CMake to meson, via a generated "machine file".
(And meson doesn't use that list for configuration tests...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

No branches or pull requests

3 participants