Daniel, I was just reviewing the Kitware CMake website and blog information.
The Xerces-C project is mature and operates in maintenance mode with few patches being applied. Xerces is already configured for a UNIX build track and a WINDOWS build track. I am unsure how "CMake" can fit into the mix without extensive committer support. There are not enough Xerces committers with CMake experience to handle on-going support. We currently use the GNU autotools (automake, autoconfig) for UNIX platforms. We currently let Microsoft Visual Studio upgrade scripts help with VS migrations. FYI: UNIX makefiles The UNIX side of Xerces builds is configured using the GNU autotools (autoconfig, automake) for a wide variety of platform specific C/C++ compilers and make libraries. After source code changes are made, a platform independent (configure, make) toolkit is created. The "configure" script determines the platform and prepares "make" to perform the build and install the product artifacts. FYI: Windows - Cygwin and MinGW These systems are deprecated. Their support is with makefiles in the manner of UNIX systems. FYI: Windows Visual Studio These system builds are not configured to use UNIX makefiles or "make" builds. They are configured as Visual Studio "solutions" and "projects" for the specific version of Visual Studio. We usually start with the earliest supported MS Visual Studio version, then incrementally apply the Microsoft Visual Studio platform updates, and apply the necessary fixups so as to make for a clean build experience. Sincerely, Steven J. Hathaway > Any reason why Xerces doesn't use CMake (http://www.cmake.org/ )? I > believe it will save the team a ton of time. > > > > I am a cmake novice but for 3.1.1 I created the attached CMakeLists.txt > file and have successful generated Visual Studio 2005, 2008, 2010, and > 2012 solution and project files for Xerces-3.1.1 with the following CMake > command line command. > > > > cmake -g "Visual Studio 8 2005" <path to xerces-c-3.1.1> > > > > It is recommended that CMake generated project and solution files be > generated "out of source". So in my case I was in a directory one level > up named Solution_CMake and so my path to xerces-c-3.1.1 was > './xerces-c-3.11' but that will vary depending on where you call cmake > from. Additionally by just typing 'cmake' with no arguments at the > command line you'll get a list of generators and the exact syntax need for > all the various generators available. The VS2012 generated string is > "Visual Studio 11" for Win32, "Visual Studio 11 ARM" for ARM Project > files, and "Visual Studio 11 Win64" for 64bit files. > > > > You'll quickly note that my CMakeLists.txt file only generates the Xerces > Library itself and not all the various examples. So there is more work to > be done but I'm thinking this is a good start and will got those wanting > to go to VS2012 today there just without examples. Just my $0.02... > > > > Thanks to the Xerces Project team for all their work! > > > > Dan > > > Daniel F. Huantes, PMP > Senior Software Engineer > [cid:image001.png@01CE05F3.557250B0] > > > > > > -----Original Message----- > From: shath...@e-z.net [mailto:shath...@e-z.net] > Sent: Thursday, February 07, 2013 7:11 PM > To: c-dev@xerces.apache.org > Subject: Xerces_C - Microsoft Upgrade > > > > FYI. > > > > As I work on getting Xalan-C ready for Microsoft Studio 2012, > > > > I plan to provide the necessary files to build Xerces-C for Microsoft > Studio 2012. I hope to use the trunk codebase. > > > > Sincerely, > > Steven J. Hathaway > > Xalan Project > > --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
