Guenter Knauf wrote:
Bill,
William A. Rowe, Jr. schrieb:
Guenter, I really missed nothing. My point was that it consumes
process resources to load an ldap support library, which are not
needed by all apr consuming applications (in fact, needed only
by a tiny minority of applications.)
I
Guenter Knauf wrote:
Bill,
William A. Rowe, Jr. schrieb:
Right, and there is a solution for that (although the win32 build system
isn't rich enough right now to offer a 'toggle' of this.)
wrong - there's no solution, and no platform can just 'toggle' - see my
other post.
Unix ./configure
William A. Rowe, Jr. schrieb:
Guenter Knauf wrote:
Bill,
William A. Rowe, Jr. schrieb:
Unix ./configure users have no trouble toggling features. Win32 and Netware
currently don't have a command line configuration tool.
maybe they can toggle APU_DSO_BUILD via configure which again results in
Mladen Turk wrote:
On 09/08/09 03:56, Guenter Knauf wrote:
so this means for the NetWare build: either have set APU_DSO_BUILD=0 in
order to build LDAP static and then no DBD driver at all, or have set
APU_DSO_BUILD=1 and be forced to build LDAP as DSO.
If we have already an own define
Hi Bill,
William A. Rowe, Jr. schrieb:
-1... yes it might be present, but it is a waste of process resource
to have a fixed binding for the 90% of apr apps that don't make ldap
queries. The idea is to pull in only the bindings used and save
a bunch of effort in the run time linker resolution
On 10/08/09 17:15, William A. Rowe, Jr. wrote:
Mladen Turk wrote:
IMHO every module should have an configure option to either
build statically or as DSO, not as right now (all or none)
-1... yes it might be present, but it is a waste of process resource
to have a fixed binding for the 90% of
Guenter, I really missed nothing. My point was that it consumes
process resources to load an ldap support library, which are not
needed by all apr consuming applications (in fact, needed only
by a tiny minority of applications.) Thanks for reminding us of
the Novell SDK as well :)
...
#if
Mladen Turk wrote:
On 10/08/09 17:15, William A. Rowe, Jr. wrote:
Mladen Turk wrote:
IMHO every module should have an configure option to either
build statically or as DSO, not as right now (all or none)
-1... yes it might be present, but it is a waste of process resource
to have a fixed
Bill,
William A. Rowe, Jr. schrieb:
see APU_DSO_LDAP_BUILD before building out new things?
I dont care much how we finally name it - functionality counts for me;
APU_DSO_LDAP_BUILD is an uncompleted attempt perhaps, but does not work
at all for two reasons:
- as I wrote already previously we have
Bill,
William A. Rowe, Jr. schrieb:
Guenter, I really missed nothing. My point was that it consumes
process resources to load an ldap support library, which are not
needed by all apr consuming applications (in fact, needed only
by a tiny minority of applications.)
I cant resist to think that
Bill,
William A. Rowe, Jr. schrieb:
Right, and there is a solution for that (although the win32 build system
isn't rich enough right now to offer a 'toggle' of this.)
wrong - there's no solution, and no platform can just 'toggle' - see my
other post.
Gün.
On Mon, 2009-08-10 at 10:15 -0500, William A. Rowe, Jr. wrote:
The idea is to pull in only the bindings used
Yeah, I thought so too. I kinda remember a discussion along those lines
on the list...
--
Bojan
Hi,
Bojan Smojver schrieb:
On Mon, 2009-08-10 at 10:15 -0500, William A. Rowe, Jr. wrote:
The idea is to pull in only the bindings used
Yeah, I thought so too. I kinda remember a discussion along those lines
on the list...
I'm perfectly fine, and even agree with your both ideas and thoughts
On Tue, 2009-08-11 at 01:22 +0200, Guenter Knauf wrote:
I'm perfectly fine, and even agree with your both ideas and thoughts
as long as you dont force every developer to adopt them! Why dont you
want to allow developers to choose what's best for their
application/platform? Is that too much
On 09/08/09 03:56, Guenter Knauf wrote:
so this means for the NetWare build: either have set APU_DSO_BUILD=0 in
order to build LDAP static and then no DBD driver at all, or have set
APU_DSO_BUILD=1 and be forced to build LDAP as DSO.
If we have already an own define APU_DSO_LDAP_BUILD - why
All,
I have the this issue:
if I define APU_DSO_BUILD=1 then that means that we're forced to build
every driver as DSO. On NetWare though we dont want to do so: we have
always LDAP available and installed - there's no NetWare installation
without LDAP, while MySQL and all other DBs are optional -
16 matches
Mail list logo
