On Mon, 10 Sep 2001, Stas Bekman wrote:
> But MODPERL_LIB will have .a extension if we make a static build. and
> $Config{dlext} "hardcodes" dynamic lib extension. Or we don't care now?
we should only install the .so, libmodperl.a is only useful when linked
into httpd.
> another thing I'm not quit about is using 'src/modules/perl' -- is it
> fine to hardcode this path (I know it's a source dir, so it should be
> the same all the time) and '/' -- shouldn't we use catfile everywhere?
not too worried about either. if catfile really needs to be used
everywhere, there's plenty of places that need to be changed, and should
be easy to change. and i'd like to keep it so that the libmodperl is
always built in the same place (unlike 1.x), so hardcoding the location is
fine. though it wouldn't hurt to be using a variable stashed in the
$build object.
> anyway, here is the new patch (I cannot reach cvs.apache.org now :( ) :
strange, i just made a commit no problems.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
