> I updated geos to latest trunk, and indeed now it used CMake and builds the
> geos lib as dll. It is called geos.dll.
> But it also has geos_static project, so I used that for linking.
You mean that you "are using" it for linking? For that I guess we have to ask
on the list what is the choice between static linking and a DLL.
> I had to fix the build with the new code.
Does this mean you committed some code? What, where?
> You can leave FIND_PACKAGE_DLLS_WIN32 with geos.dll, it only raises a warning
> if it doesn't find it.
> One new issue I had is that now geos library has two include dirs: one in the
> source dir and one in the build directory. I had to add manualy the one from
> the build dir because it cannot be discovered.
To build with geos you only need the "install" dir. That is after you call
"nmake install". No build, no source. Once built, you can delete them like I
did (unless you keep them for debugging reasons)
Your team Zorba Coders is subscribed to branch lp:zorba/geo-module.
Mailing list: https://launchpad.net/~zorba-coders
Post to : email@example.com
Unsubscribe : https://launchpad.net/~zorba-coders
More help : https://help.launchpad.net/ListHelp