1) Even if you build the whole thing, only the pieces used will be pulled
into the application linking against APRUTIL. It is exactly this behavior
that we're trying to avoid with the whole exports.c hack (we're trying
to force a reference to everything in APR to ensure that it all
On Wed, Dec 06, 2000 at 04:05:12PM -0800, [EMAIL PROTECTED] wrote:
1) Even if you build the whole thing, only the pieces used will be pulled
into the application linking against APRUTIL. It is exactly this behavior
that we're trying to avoid with the whole exports.c hack (we're trying
How much complexity are we willing to trade off for the minority position?
I consider this an important issue, so I am willing to trade a bit of
complexity for this feature. I don't want to add a lot of complexity, but
a bit.
Plus, as apr-util grows, Apache will not want some of the functions
On Wed, Dec 06, 2000 at 09:19:07PM -0600, William A. Rowe, Jr. wrote:
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 06, 2000 9:01 PM
Just a footnote... what is in misc/ could just as easily live in a
helpers or
build directory, it's nothing but an
From: Greg Stein [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 07, 2000 2:01 AM
I'm actually contemplating building both the .lib and .dll as two full
compiles.
The benefit, when called for, is that users of the .lib won't have dangling
exported symbols. I refused so far because
On Thu, Dec 07, 2000 at 07:26:05AM -0600, William A. Rowe, Jr. wrote:
From: Greg Stein [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 07, 2000 2:01 AM
I'm actually contemplating building both the .lib and .dll as two full
compiles.
The benefit, when called for, is that users
From: Greg Stein [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 07, 2000 7:38 AM
On Thu, Dec 07, 2000 at 07:26:05AM -0600, William A. Rowe, Jr. wrote:
the only way the MSVC 5.0 .dsp files may depend on one another are
on the same - Win32 Debug tag ... only when you get into 6.0
