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

build-openssl.bat dont have option for custom path for VS and perl #2430

Closed
patelvivekv1993 opened this Issue Mar 26, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@patelvivekv1993
Contributor

patelvivekv1993 commented Mar 26, 2018

I did this

I was trying to use the .bat file to build openssl but it was saying visual studio not found even if it was installed. On inspecting i found visual studio was installed on a different path in my PC. Similarly for the perl library no custom path can be set if user is having portable library.

I expected the following

.bat file should be able to provide multiple options to the user.

curl/libcurl version

v1.3
[curl -V output]

operating system

Windows

@patelvivekv1993

This comment has been minimized.

Show comment
Hide comment
@patelvivekv1993

patelvivekv1993 Mar 26, 2018

Contributor

I would like to contribute and make the .bat file more generalized. Let me know if this issue is accepted.

Contributor

patelvivekv1993 commented Mar 26, 2018

I would like to contribute and make the .bat file more generalized. Let me know if this issue is accepted.

@bagder

This comment has been minimized.

Show comment
Hide comment
@bagder

bagder Mar 26, 2018

Member

Please go ahead, I'm sure it'll be appreciated!

Member

bagder commented Mar 26, 2018

Please go ahead, I'm sure it'll be appreciated!

@bagder bagder added the build label Mar 26, 2018

@bagder

This comment has been minimized.

Show comment
Hide comment
@bagder

bagder Mar 26, 2018

Member

See also #2189

Member

bagder commented Mar 26, 2018

See also #2189

@bagder bagder closed this in a65a75e Apr 6, 2018

@lock lock bot locked as resolved and limited conversation to collaborators Jul 5, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.