Just two small general NITs (Sort of off-topic, as the OP seems
to know this):
On 10/17/2012 2:53 AM, Dave Thompson wrote:
...
- "implicit" dynamic linking, with .lib on Windows containing stubs
that point to code (and sometimes data, but that's usually poor
practice) in a .dll. This type of .l
OK. Misunderstood the earlier answer.
Charles
-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Dave Thompson
Sent: Thursday, October 18, 2012 12:26 AM
To: openssl-users@openssl.org
Subject: RE: Building an "exportable&quo
> From: owner-openssl-us...@openssl.org On Behalf Of Charles Mills
> Sent: Wednesday, 17 October, 2012 09:47
[Using ShiningLight Windows build]
> > If you link with lib/VC/* (or lib/MinGW/*) you get
> > implicit dynamic linking. If you link with
> > lib/VC/static/* you get static linking.
>
> T
org
Subject: RE: Building an "exportable" OpenSSL application
> From: owner-openssl-us...@openssl.org On Behalf Of Charles Mills
> Sent: Tuesday, 16 October, 2012 11:41
> > If you are linking to OpenSSL DLLs, then your application
> isn't statically
> > linked agains
> From: owner-openssl-us...@openssl.org On Behalf Of Charles Mills
> Sent: Tuesday, 16 October, 2012 11:41
> > If you are linking to OpenSSL DLLs, then your application
> isn't statically
> > linked against OpenSSL. .lib files can simply be
> references to exports in .dll files.
>
> This is an
penssl-users@openssl.org
Subject: Re: Building an "exportable" OpenSSL application
On 10/16/2012 7:25 AM, Charles Mills wrote:
> I have a Windows-only OpenSSL application developed in VS 2010. I have
> now been tasked with creating parallel "regular" and "exportable"
On 10/16/2012 7:25 AM, Charles Mills wrote:
I have a Windows-only OpenSSL application developed in VS 2010. I have now
been tasked with creating parallel "regular" and "exportable" (from the US)
distributions of the application.
I UNDERSTAND YOU CAN'T GIVE LEGAL ADVICE. I'M ONLY LOOKING FOR TECH
On Tue, Oct 16, 2012 at 10:25 AM, Charles Mills wrote:
> I have a Windows-only OpenSSL application developed in VS 2010. I have now
> been tasked with creating parallel "regular" and "exportable" (from the US)
> distributions of the application.
There's no need for two versions. Its all exportable
I have a Windows-only OpenSSL application developed in VS 2010. I have now
been tasked with creating parallel "regular" and "exportable" (from the US)
distributions of the application.
I UNDERSTAND YOU CAN'T GIVE LEGAL ADVICE. I'M ONLY LOOKING FOR TECHNICAL
INPUT HERE.
The application statically
