Roger Leigh
2015-06-23 15:08:03 UTC
Dear all,
Firstly, hello. I am Roger Leigh, a C++ developer currently working on
a project (Bio-Formats-C++) which makes use of Xerces-C++.
One of the parts of this role is integrating several upstream projects,
of which xerces is one, into a larger project which needs to build on
Unix/Linux/Windows. While the xerces-c project provides an
autotools-based build and several different visual studio solution
files, I was wondering if you had considered the use of a tool such as
CMake, which can generate solution files for all visual studio versions
(including 2015), Makefiles, and project files for a number of IDEs,
including Eclipse? This allows all the platforms to be supported well
from a common set of build rules, and means you don't need to maintain
separate solutions for each visual studio release.
The reason for asking is that over the course of the last few weeks,
I've converted several open source projects from autotools+separate msvc
builds to a unified cmake build and submitted these to their upstream
developers. If this is something you would find beneficial and useful,
then I would be happy to do the same for xerces-c. This can, of course,
co-exist with the existing build systems.
Kind regards,
Roger Leigh
Firstly, hello. I am Roger Leigh, a C++ developer currently working on
a project (Bio-Formats-C++) which makes use of Xerces-C++.
One of the parts of this role is integrating several upstream projects,
of which xerces is one, into a larger project which needs to build on
Unix/Linux/Windows. While the xerces-c project provides an
autotools-based build and several different visual studio solution
files, I was wondering if you had considered the use of a tool such as
CMake, which can generate solution files for all visual studio versions
(including 2015), Makefiles, and project files for a number of IDEs,
including Eclipse? This allows all the platforms to be supported well
from a common set of build rules, and means you don't need to maintain
separate solutions for each visual studio release.
The reason for asking is that over the course of the last few weeks,
I've converted several open source projects from autotools+separate msvc
builds to a unified cmake build and submitted these to their upstream
developers. If this is something you would find beneficial and useful,
then I would be happy to do the same for xerces-c. This can, of course,
co-exist with the existing build systems.
Kind regards,
Roger Leigh
--
Dr Roger Leigh -- Open Microscopy Environment
Wellcome Trust Centre for Gene Regulation and Expression,
College of Life Sciences, University of Dundee, Dow Street,
Dundee DD1 5EH Scotland UK Tel: (01382) 386364
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-***@xerces.apache.org
For additional commands, e-mail: c-dev-***@xerces.apache.org
Dr Roger Leigh -- Open Microscopy Environment
Wellcome Trust Centre for Gene Regulation and Expression,
College of Life Sciences, University of Dundee, Dow Street,
Dundee DD1 5EH Scotland UK Tel: (01382) 386364
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-***@xerces.apache.org
For additional commands, e-mail: c-dev-***@xerces.apache.org