Yes, this is intentional.
We don't have a strategy yet for dealing with package-specific individual
compilation flags like this.
In the meantime, you can try using a system module package instead, and
manually defining OPENSSL_LOAD_CONF inside a header within the system module
package before you import the actual OpenSSL headers.
- Daniel
> On Sep 20, 2016, at 1:35 PM, Raminder Sodhi via swift-dev
> <swift-dev@swift.org> wrote:
>
> Hi,
>
> The swift package manger seems consider the -DOPENSSL_LOAD_CONF as a
> non-whitelisted flag.
> As a result, I get
> nonWhitelistedFlags("Non whitelisted flags found: [\"-DOPENSSL_LOAD_CONF\"]
> in pc file openssl")
>
> Is this flag supposed to be non whitelisted ?
>
> Seems relevant to be by reading upon this:
> https://wiki.openssl.org/index.php/Library_Initialization#OPENSSL_config
> <https://wiki.openssl.org/index.php/Library_Initialization#OPENSSL_config>
>
>
> Raminder Sodhi
> E-mail: sodra...@ca.ibm.com <mailto:sodra...@ca.ibm.com>
> _______________________________________________
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev
