From: Kimmo Varis <kimmov@wi...> - 2008-05-26 19:01:38
I'm in process of preparing pcre update for WinMerge trunk. Our current
pcre version is pretty old 6.7 (one I found with Visual Studio project
files back then).
The tracker item for this is:
TODO: #1941779 Update PCRE to latest version
As Tim noted in the tracker item, latest 7.x pcre versions use CMake to
generate make/project files. That allows us to use CMake to generate
Visual Studio solution/project files and enjoy new version. Not quite:
1) folder structure has been changed quite a lot, as are file names
2) sub projects have been changed, as are built targets, and some build
If that wasn't enough, CMake isn't all that easy for us. It kind of
assumes every one wants to use CMake to configure the project and
generate project files. And it seems to make some assumptions about
folder structure too.
I don't want to add CMake as WinMerge development requirement, and I
really don't want to require all developers familiarizing themselves for
PCRE configuration. So I'm creating project/solution files for pcre and
adding them to WinMerge repository. So there is no visible change in
building WinMerge for most. I can't use files created by CMake because
there are absolute paths etc. So I'll fix (lots of) paths in them.
Two important things in this update:
1) I'll create project/solution files for VS2003. So good bye VC6 unless
somebody voluteers creating files for it.
2) If you have local changes to any file in Externals/pcre folder, be
sure to backup them before updating from SVN. Lots of files will be deleted!
There will be some hazzle in SVN for couple of days when I remove old
pcre and add new one. And probably need some fixes for building too...
Yes, we are deprecating our support for VC6. I've mentioned this few
times and this is first time it is really visible move. But again, I'll
commit VC6 fixes if somebody sents them and they don't break other