[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apr-dev
Subject:    Re: Build of libapritil-1.lib failed on Windows using VS2008
From:       "William A. Rowe Jr." <wrowe () rowe-clan ! net>
Date:       2012-07-30 19:46:55
Message-ID: 5016E4AF.40307 () rowe-clan ! net
[Download RAW message or body]

On 7/26/2012 4:23 PM, Prakash Reddy Bande wrote:
> Hi,
> 
> If we are using apr in multi threaded environment, what is a better choice? Static libs or dlls?

Red herring.

If you are using apr from multiple invocations of a process, or from multiple
processes at once, a shared apr dll wins an advantage; the code/static data
is loaded once into memory for all consumers (provided it is the same file
at the same path).

If your application is a library that must coexist in another process space,
which also uses apr, you either need to use /their/ build of the .dll (e.g.
an identical build based on the same msvcrXXX version), or link statically.


[prev in list] [next in list] [prev in thread] [next in thread]