httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject RE: Draft proposal: Win32 Compilation Environment Step 1
Date Mon, 17 Apr 2000 05:26:45 GMT
> From: William A. Rowe, Jr. []
> Sent: Saturday, April 15, 2000 8:56 PM
> Step 2 will build an apr.lib from the apr.dsp/apr.mak project files 
> which mirrors the aprlib.  But it will become a STATIC library, 
> for those applications that call for it. Namely, support applications.
> Here's where I am absolutely jammed.  Now I know why I created
> that apr.dsp 4 project library...
> We don't want aprlib.dll in winnt/system32 since it's a moving
> target.  So what do we want?
> ??? A second copy of aprlib.dll in support?
>     That's rather sad.
> ??? Continue to compile the apr sources within support apps?
>     That's just nuts.
> ??? Have both apr and aprlib declare all the sources?  This
>     looks like a headache.
> ??? Have apr build a lib with the export symbols defined,
>     have aprlib turn that lib into a dll, and continue
>     to use the apr.lib with symbols to link to static exe's?
>     Just some wasted space, if I am correct, or perhaps I
>     can throw away the export table from the linker.

As another option along the same lines, 

  ??? add a lib as a post build step to build the very same
      .obj files into a library.  Don't know if this would
      be clean and easy, but it would roll it all into one

> ??? Go to the idea of "Win32 Static" projects, as I've
>     proposed once before?  
>     I sort of junked that idea since I'm not certain the
>     dependencies of VC5 will call the right mate from the
>     master InstallBin project (InstallBin Win32 Debug
>     invokes htdigest - Static ... how reliably will
>     it choose htdigest - Static Debug?  I KNOW that VC6
>     will handle it... and again I'm not ready to toss
>     the VB5 users of the world over make file issues!)
> Preferences anyone?

View raw message