Age | Commit message (Collapse) | Author |
|
Update to libz-sys 1.1.0, which supports zlib-ng. Provide a feature
zlib-ng-compat to allow building with zlib-ng. Since doing so statically
links zlib-ng, ensure that this feature prevents using a system libssh2.
|
|
This caused fairly widespread problems and it seems that the original
issue that led to this change (https://github.com/rust-lang/rust/issues/69552)
should really be fixed by better defining the data exported from eg:
libz-sys rather than having downstream crates replicating the same logic
from inside that crate.
refs: https://github.com/alexcrichton/ssh2-rs/issues/174
refs: https://github.com/alexcrichton/ssh2-rs/pull/170
refs: https://github.com/alexcrichton/ssh2-rs/issues/169
refs: https://github.com/rust-lang/rust/issues/69552
|
|
This was primarily done to address issues from changing
LIBSSH_SYS_USE_PKG_CONFIG, but it's good build script practice to let
Cargo know of every used environment variable.
Closes: https://github.com/alexcrichton/ssh2-rs/issues/171
|
|
|
|
set in env
|
|
|
|
|
|
|
|
hopefully this will make the i686 build a little happier on appveyor
|
|
|
|
No functional changes, just formatting
|
|
Fixes #110
|
|
This change is required to compile session.c
|
|
When LIBSSH2_DH_GEX_NEW is not defined LIBSSH2 will use an old
diffie-hellman-group-exchange-sha1 syntax that has been removed from
newer versions of OpenSSH.
|
|
* Remove `cmake` dependency in favor of `cc`
This has been done in a few other projects and has made it lightyears easier to
compile native C code, so let's do it here!
More info at alexcrichton/curl-rust#225
|
|
I don't really want to futz with pkg-config, building on all platforms is a
nightmare.
|
|
|
|
The latest actual release of libssh2 is old and broken. This uses the submodule instead unless you set `LIBSSH2_SYS_USE_PKG_CONFIG`. The mechanism is copied from libgit2.
|
|
|
|
|
|
|
|
Help update for openssl-sys crate release
|
|
|
|
|
|
|
|
|
|
Seems to cause cmake to choke regardless unfortunately.
|
|
|
|
Helps with nonstandard install locations of openssl
|
|
Some CMake invocations will attempt to find libraries like OpenSSL through
pkg-config and these may have been built into a custom location, so be sure to
set up PKG_CONFIG_PATH to point to them.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Have an entirely separate path for windows builds
* Run `make install` on unix builds for libssh2
* On Windows, first detect whether `make` is available
* Use the specific `win32/GNUmakefile` for windows instead of the standard
configure/make procedure for unix.
* Continue doing a manual install on Windows, but don't rely on `pkg-config`
existing and don't emit a pkg-config file.
One day this may support MSVC-based builds, but support is not added at this
time.
|
|
It's not needed and sometimes the build can fail for obscure reason due to
building a staticlib on some platforms.
|
|
* Have an entirely separate path for windows builds
* Run `make install` on unix builds for libssh2
* On Windows, first detect whether `make` is available
* Use the specific `win32/GNUmakefile` for windows instead of the standard
configure/make procedure for unix.
* Continue doing a manual install on Windows, but don't rely on `pkg-config`
existing and don't emit a pkg-config file.
One day this may support MSVC-based builds, but support is not added at this
time.
|
|
|
|
Ends up causing havoc on OSX
|
|
|