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

Don't require a custom .cargo/config to build #204

Closed
Diggsey opened this issue Mar 29, 2016 · 0 comments · Fixed by #400
Closed

Don't require a custom .cargo/config to build #204

Diggsey opened this issue Mar 29, 2016 · 0 comments · Fixed by #400

Comments

@Diggsey
Copy link
Contributor

Diggsey commented Mar 29, 2016

The dependency issue with openssl (previously missing dependencies on user32-sys and gdi32-sys) has been fixed, and yet multirust still requires a custom cargo config to build.

For some reason, the dylib dependency from gdi32-sys does not get passed to the linker, despite it being present in the build-script output.

To reproduce this issue, install the openssl binaries exactly as the appveyor script does, and set these environment variables (assuming 64-bit):

DEP_OPENSSL_INCLUDE=C:\OpenSSL\openssl-1.0.2d-vs2015\include64
OPENSSL_INCLUDE_DIR=C:\OpenSSL\openssl-1.0.2d-vs2015\include64
OPENSSL_LIB_DIR=C:\OpenSSL\openssl-1.0.2d-vs2015\lib64
OPENSSL_LIBS=libeay32MT:ssleay32MT

Then do a clean cargo build. The expected result is a ton of warnings about missing pdb files, followed by the relevent error, a missing symbol from gdi32.lib.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant