Am 17.10.2014 20:50, schrieb Greg Bullock:
On 10/17/2014 4:38 AM, Andre Fischer wrote:
On 17.10.2014 13:21, Regina Henschel wrote:
Hi Andre,
will these in the long term lead to a system, where AOO can be build
directly in MS Visual Studio without need of cygwin?
Hi Regina,
this is not a direct goal but could become possible as a side effect.
One of the key ideas of the proposed approach is to further separate
between dependencies and build logic and have scripts/programs
transform the dependencies into actual make files. Once the
dependencies are present as uniform XML files we can more easily
write a transformation into Visual Studio solution files. But this
will still not be a trivial task.
It would help me if you or somebody else could provide a description
or even a specification of Visual Studio solution/project files.
-Andre
Hi Andre.
With other projects, I've had generally good success using CMake,
which can generate Visual Studio solution/project files of various VS
versions (as well as makefiles and other types of "project" files).
Even if the team prefers not to standardize on CMake for the entire
build process (although, that may be a worthy option), the
dependencies and build logic from the XML files could be used to
generate a set of CMakeList.txt files, and with those at hand, CMake
can then take over and generate the Visual Studio solution/project files.
Hi Greg,
as you already hinted at, I intend the XML files to be an intermediate
file format. Easy to read so that we can write translations into actual
build systems like CMake.
-Andre
Regards.
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
