Closed ikrivosheev closed 1 year ago
LGTM!
Did you consider to use a cargo feature for the YARA_STATIC
and YARA_OPENSSL_STATIC
? Is that something we want?
LGTM! Did you consider to use a cargo feature for the
YARA_STATIC
andYARA_OPENSSL_STATIC
? Is that something we want?
Yes! It makes sense! Done)
@ikrivosheev I added them to mimic rust-openssl
, so that setting the env can work for both.
I'm not sure why the collision would be a bad thing, unless you want to use different versions of openssl for both.
But splitting them is fine too, just a bit more annoying when both OPENSSL_*
and YARA_OPENSSL_*
have to be set instead of just the OPENSSL_*
one
@Hugal31 do we want to add support both envs: OPENSSL_*
and YARA_OPENSSL_*
?
YARA_OPENSSL_STATIC
env for static linking withopenssl
OPENSSL_DIR
toYARA_OPENSSL_DIR
- remove name conflict withrust-openssl
OPENSSL_LIB_DIR
toYARA_OPENSSL_LIB_DIR
- remove name conflict withrust-openssl
OPENSSL_INCLUDE_DIR
toYARA_OPENSSL_INCLUDE_DIR
- remove name conflict withrust-openssl
LIBYARA_STATIC
toYARA_STATIC
- for uniform with other envs@vthib you added envs for
openssl
, can you look at the PR? My thought was: remove name conflict withrust-openssl
, maybe I am not right and it's ok.