-
Notifications
You must be signed in to change notification settings - Fork 284
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
Linking error with LDC on Win64 due to strange subpackage libs-ldc #1629
Comments
kinke
changed the title
Linking error with LDC on Win64 due to strange subpackage ldc-libs
Linking error with LDC on Win64 due to strange subpackage libs-ldc
Nov 20, 2016
This was referenced Nov 20, 2016
It did. So your suggested fix makes sense, although zlib should be part of libphobos2-ldc for quite a while now. |
Okay, I'll change it like that then. Based on the context of my commit, I guess that LDC 1.0.0 was still affected by this, which is still the latest stable release, so I'd like to keep the workaround for a while still. |
s-ludwig
added a commit
that referenced
this issue
Dec 19, 2016
LDC on Windows chokes on the library dependency and the latest LDC releases already include libz in libphobos. Conflicts: stream/dub.sdl
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Testing dub (v1.1) and vibe.d (v0.7.30) with an early LDC 1.1 (ldc-developers/ldc#1891), a project template cannot be linked on Win64 due to missing
z.lib
. This seems to come in via vibe.d's subpackages in%AppData%\dub\packages\vibe-d-0.7.30\vibe-d\dub.json
, where there's a"libs-ldc": [ "z" ]
item. Removing it gets the project to compile, link and run successfully, with both LDC2 and LDMD2.I did a quick test on Ubuntu 16.04 (x86_64), removed the subpackage as well (and worked around #1611 with a manually added OpenSSL dependency), and it's also working. So this LDC-specific dependency (on zlib apparently) may not be required after all (isn't it part of
druntimePhobos?) and only causes trouble on Windows.The text was updated successfully, but these errors were encountered: