Mathis Logemann

I will look into it. But it will be at a later time as I first need to get all other things done. So currently only vs2019 and vs2022. But...

Just to note: The build isn't invoked with node-gyp. Instead it uses cmake. Any limitations related with node-gyp don't apply here. So the mapnik build error is related to mapnik...

@GimpMaster the quickest way would be to modify `vcpkg/ports/mapnik/portfile.cmake`. Just replace ``` vcpkg_from_github( OUT_SOURCE_PATH SOURCE_PATH REPO mapnik/mapnik REF 0edb018465790cd156d6849557fa7fd568755ebb SHA512 cd6180b96dbfbc1bafbc8f2a4ff2091a0e8c0c42b0569ef83640ad1f5766ff74ea95f8c6cef53f879396cbceebc6396c1a977676eca67c401b8e145a9ceae7e2 HEAD_REF master ) ``` with `set(SOURCE_PATH )` or if...

It looks like it is still not correctly wrapped. Have you wrapped them like this: `(std::min)(x, y);` ? so that the function-like macro won't be applied? ``` H:\Fast_Dev\imsar\mapnik\include\mapnik/util/char_array_buffer.hpp(74): error C2039:...

Yeah. I'm working on it. I have narrowed it down to libpq. Need to attach windbg to it. To get more infos, why it fails to load and which symbols...

I try to get it ready as fast as possible. But I don't know how long I need to debug. The pr is ready to distribute binaries (`npm run publish`)....

@GimpMaster https://github.com/microsoft/vcpkg/pull/20824 vcpkg will soon be updated and has your fix.

Yeah. I guess it is something with libpq. I haven't had so much time this weekend. hopefully I get some results in this week.

mapnik v3.7.2 looks quite old. the newest is 4.5.8

Either as a submodule or we add a correct installation cmake logic to the agg library. And then it can just be found with `find_package(agg CONFIG required)`.