Jan,

That is correct. The .dsp is wired to interrelated projects via the .dsw
file.  Exporting the projects into .mak files causes all the 'depends upon'
libs to be added. See any other such as mod_status. If we were building
brotli in-tree you would add the libbrotli .dsp and it would resolve that
lib.

Which is why my product build (not /dist/httpd/ win32 binary) differed for
a decade+... My clone of Apache.dsw has no apr, therefore I used the
cvtdsp.pl logic to put in all the required libapr-1.lib dependencies. A
real PITA.

They simply go away after httpd-2.4.x as no longer supported. CMake just
works and eliminates a ton of ASF and external maintenance.



On Apr 28, 2017 9:19 AM, "Jan Ehrhardt" <php...@ehrhardt.nl> wrote:

> Hi Gregg,
>
> Gregg Smith in gmane.comp.apache.devel (Tue, 25 Apr 2017 18:23:50
> -0700):
> >Actually, I'll test here in a while and commit tomorrow.
>
> Quote from modules/filters/mod_brotli.dsp
>
> > +# ADD LINK32 kernel32.lib brotlicommon.lib brotlienc.lib /nologo
> /subsystem:windows /dll /incremental:no /debug
> /out:".\Release\mod_brotli.so" /libpath:"../../srclib/brotli" /base:@
> ..\..\os\win32\BaseAddr.ref,mod_brotli.so /opt:ref
>
> The dsp seems to be missing a reference to libapr-1.lib,
> libaprutil-1.lib and libhttpd.lib, which is present in the
> mod_brotli.mak:
>
> +LINK32=link.exe
> +LINK32_FLAGS=kernel32.lib brotlicommon.lib brotlienc.lib /nologo
> /subsystem:windows /dll /incremental:no /pdb:"$(OUTDIR)\mod_brotli.pdb"
> /libpath="../../srclib/brotli" /debug /out:"$(OUTDIR)\mod_brotli.so"
> /implib:"$(OUTDIR)\mod_brotli.lib"
> /base:@..\..\os\win32\BaseAddr.ref,mod_brotli.so /opt:ref
> +LINK32_OBJS= \
> +       "$(INTDIR)\mod_brotli.obj" \
> +       "$(INTDIR)\mod_brotli.res" \
> +       "..\..\srclib\apr\Release\libapr-1.lib" \
> +       "..\..\srclib\apr-util\Release\libaprutil-1.lib" \
> +       "..\..\Release\libhttpd.lib"
>
> When I converted the dsp to mod_brotli.vcxproj it did not compile
> because of missing symbols like __imp__apr_bucket* or something like
> that..
> --
> Jan
>
>

Reply via email to