Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 25696 invoked by uid 500); 17 Apr 2000 20:51:57 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 25575 invoked from network); 17 Apr 2000 20:51:55 -0000 Message-Id: <4.3.1.2.20000417164018.00afa2c0@pop.ma.ultranet.com> X-Sender: gregmm@pop.ma.ultranet.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Mon, 17 Apr 2000 16:48:08 -0400 To: new-httpd@apache.org From: Greg Marr Subject: RE: Draft proposal: Win32 Compilation Environment Step 1 In-Reply-To: References: <000801bfa887$fd729720$345985d0@corecomm.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N At 04:31 PM 04/17/2000, Greg Stein wrote: >Forget delay loading and all that stuff. Statically link APR into >apache.exe and be done with it. > >APR will still build outside of Apache, but when we redistribute APR >as part of Apache, then we should do a static link. That solves the >path problem, the relocation problem, etc. It also increases the code size of any server that uses any DLL modules that use APR, since they'll have to statically link against APR as well. This can also cause no end of problems with static variables, if APR has any, since Apache itself, and every module that it loads, will have its own copy of the statics. Leaving APR as a DLL means that everything can use the same copy of the code, and there's only one of every static. This is the same reason that Apache and all the modules link against the DLL version of the C Runtime library. >I see no purpose served by having the Apache distribution be able to >build an APR DLL. When APR starts shipping standalone, then we can >possible update Apache to dynlink against it. I see no purpose served by having Apache link statically against APR. If the problem is with the programs in the support directory being able to find the APR dll, then put a copy of the APR dll in the support directory, put the support programs in the main directory, or have the support programs link to APR statically. -- Greg Marr gregm@alum.wpi.edu "We thought you were dead." "I was, but I'm better now." - Sheridan, "The Summoning"