RE: Static libcurl size under Windows

2017-04-21 Thread Rod Widdowson 
> Does anyone know why we're rolling all dependencies into static libcurl lib?

I looked and timed out.  I don't speak nmake too good but thus far it looks 
like an artefact of the way the dll is built "Put in appropriate references for 
everything".  Also I cannot get over this suspicion that the build is using the 
linker to create the archive ("you are in a maze of nested symbol indirection, 
all alike").

I'll look a bit more this weekend but thusfar I'm coming up dry I'm hoping 
someone with stronger nmake-fu than I will dive it.

/Rod


---
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html

Re: Static libcurl size under Windows

2017-04-21 Thread Ray Satiro via curl-library 
On 4/20/2017 10:57 AM, Konstantin Vlasov wrote:
> I need static libcurl.lib which uses static OpenSSL but does NOT contain it as
> part of itself. Otherwise I would get link errors (symbol conflicts) when
> building VirtualBox with both libcurl AND openssl. The first scenario gave me
> exactly what I needed, but now in 7.54.0 it is deprecated. How do I get that
> type of libcurl.lib now?

Does anyone know why we're rolling all dependencies into static libcurl lib?
---
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html

Re: Static libcurl size under Windows

2017-04-20 Thread Marcus Hoffmann 
Hey Konstantin,

On 20.04.2017 16:57, Konstantin Vlasov wrote:
> I need static libcurl.lib which uses static OpenSSL but does NOT contain it as
> part of itself. Otherwise I would get link errors (symbol conflicts) when
> building VirtualBox with both libcurl AND openssl. The first scenario gave me
> exactly what I needed, but now in 7.54.0 it is deprecated. How do I get that
> type of libcurl.lib now?

I'm mostly familiar with the linking process on Linux but it shouldn't
conceptually be much different on Windows.

When statically linking to some libraries the linker only picks the
object files that are needed by the final program out of every static
library it encounters. [1]

So it shouldn't matter at all how big your intermediate .lib files are.

Best wishes,
Marcus

[1] i.e.:
http://eli.thegreenplace.net/2013/07/09/library-order-in-static-linking
---
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html

Re: Static libcurl size under Windows

2017-04-19 Thread Jan Ehrhardt 
Konstantin Vlasov in gmane.comp.web.curl.library (Wed, 19 Apr 2017
21:38:45 +0300):
>nmake /f Makefile.vc mode=static WITH_SSL=static DEBUG=no MACHINE=x86 
>WITH_DEVEL=C:\Programs\OpenSSL\x32 ENABLE_SSPI=no ENABLE_WINSSL=no
>
>It produced libcurl_a.lib with size of 21 Mb! I tried the same with 7.52.1 
>(the 
>last version with lib/Makefile.vc* so that I could compare), and it produced 
>the 
>same huge file, so it's not the difference between 7.52.1/7.54.0, but some 
>difference in build procedures.
>
>So, my questions are:
>1. Why are the resultant files so hugely different?

What is the size of your libeay32.lib & ssleay32.lib files?
-- 
Jan

---
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html