See CHANGES, which points you to the contents of Makefile.win which documents a new variable pointed out in CHANGES, XML_PARSER, which is the name of whatever library you like.
As documented everywhere, if you want to use dbm or dbd or openssl linkages, you add these to the INCLUDE and LIB paths for any microsoft toolchain component, this hasn't changed in 30 years. For the cmake build specifically, we do try to add the expat path, we will simply trust cmake. See your FindEXPAT.* files in your cmake tree on that feature set and detection options. On Wed, Oct 18, 2017 at 4:13 PM, Gregg Smith <g...@gknw.net> wrote: > On 10/18/2017 7:58 AM, William A Rowe Jr wrote: >> >> Please cast your votes on the following candidate packages; > > > I'm not there to vote yet, my question is how did you expect us to build APU > with a precompiled lib and this lib put where? > > Looking at both makafile.win and libaprutil.mak I see not much for pointers > here. I see an include of ./xml/expat/lib in libaprutil.mak so do I really > have to put expat in the xml folder? Seem it should be outside the apr-util > folder so the include would be like /I ../expat/lib > > Further, no /libpath: pointing to where libexpat.lib is grabbed from at > apu's linking. I don't remember vc ever being that smart to just find it, it > knew it was in ./xml/libR because that's where it put xml.lib, which we > don't have anymore. > > cmake -G "NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_shared=OFF > gives me an expat.lib, not libexpat.lib, so unless I'm missing something > really obvious that's right under my nose, I don't get it :) >
