Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 20835 invoked by uid 500); 12 Aug 2002 20:04:17 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 20805 invoked from network); 12 Aug 2002 20:04:16 -0000 Message-ID: <3D5814C6.2040101@apache.org> Date: Mon, 12 Aug 2002 13:04:22 -0700 From: Ian Holsman User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020808 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: different module building semantics References: <3D57DADD.26882.A580193F@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Aryeh Katz wrote: > In order to build the non-standard modules, configure requires a command > line option of the form --enable-module-name. > The problem with this (other than being unable to use the --enable-module=) > syntax, is that you can't choose to build as a shared library. > This causes much work in order add a non-standard module, because you > have to rebuild the entire server just to get one more module enabled. > --- > Aryeh Katz > VASCO > www.vasco.com > Hi Aryeh. have a look at apxs. this might be a better approach for your development, as all you require are the header files and the libraries to create a module.