-
Notifications
You must be signed in to change notification settings - Fork 1
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
Path to zlib root should not be hard-coded #27
Comments
dzhoshkun
added a commit
that referenced
this issue
Mar 15, 2019
dzhoshkun
added a commit
that referenced
this issue
Mar 15, 2019
dzhoshkun
added a commit
that referenced
this issue
Mar 20, 2019
dzhoshkun
added a commit
that referenced
this issue
Mar 20, 2019
dzhoshkun
added a commit
that referenced
this issue
Mar 20, 2019
dzhoshkun
added a commit
that referenced
this issue
Mar 20, 2019
Related to #26 |
dzhoshkun
added a commit
that referenced
this issue
Apr 8, 2019
dzhoshkun
added a commit
that referenced
this issue
Apr 8, 2019
dzhoshkun
added a commit
that referenced
this issue
Apr 8, 2019
dzhoshkun
added a commit
that referenced
this issue
Apr 8, 2019
dzhoshkun
added a commit
that referenced
this issue
Apr 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For testing purposes,
ZLIB_ROOT
can be defined as an envvar in CI script. However that still doesn't solve the problem of distributing code.The text was updated successfully, but these errors were encountered: