-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Boost: Broken detection when cross compiling to Windows hosts #2631
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
Comments
@NickeZ, could you look into this and also add more debug logging with mlog.debug()? |
I never tried cross compiling with boost. I probably won't set this up and try it.. |
I never tried cross compiling with boost. I probably won't set this up and
try it..
This should be quite easy with mxe.
Basically, Meson’s Boost detection assumes that Windows == MSVC, and lifting
that assumption would most likely fix this issue.
|
On Debian a cross build involved installing Probably most of the occurrences of is_windows() and is_linux() need to be changed to for_windows( ) and for_darwin( ). Specifically,
Maybe we should add methods self.for_windows() and self.for_darwin() to ExternalDependency or Dependency? |
I can confirm the issue exists on Fedora 27 cross-compiling using mingw32 -- and using precompiled boost packages (mingw32-boost, mingw32-boost-static). Hopefully, there is a workaround, as mentioned at https://unix.stackexchange.com/questions/408963/meson-doesnt-find-the-boost-libraries:
(that is particular case for boost asio using Windows sockets for TCP) |
See also #2990 |
@lachs0r I think this is fixed now in current master. Can you try it out? |
Sorry about the late response. Seems to work now. Thanks! |
Python system: Linux
Version: 0.43.0
When cross compiling to Windows using a mingw-w64 toolchain, the Boost dependency detection is broken and can’t find the libraries.
Problem is probably right here:
meson/mesonbuild/dependencies/misc.py
Lines 230 to 233 in e51da1a
Also, this needs more logging. Can’t even tell what it’s looking for.
The text was updated successfully, but these errors were encountered: