Re: Add scripts to generate projects for other buildsystems (MSVC vcproj, QMake)
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Sep 23, 2009, 20:37 UTC
- Message-ID
- <alpine.DEB.1.00.0909232236490.4985@pacific.mpi-cbg.de>
- In-Reply-To
- <72888219-5bab-4964-9faf-0d40b4770e2c@o35g2000vbi.googlegroups.com>
Hi,
On Wed, 23 Sep 2009, Sebastian Schuberth wrote:
Show 19 quoted lines
> On Sep 16, 10:20 am, Marius Storm-Olsen <mstormo@gmail.com> wrote: > > > These scripts generate projects for the MSVC IDE (.vcproj files) or > > QMake (.pro files), based on the output of a 'make -n MSVC=1 V=1' run. > > > > This enables us to simply do the necesarry changes in the Makefile, and you > > can update the other buildsystems by regenerating the files. Keeping the > > other buildsystems up-to-date with main development. > > I know I'm a little late with my comments as this patch set has > already been merged to master. However, for future reference I'd like > to point out that something similar could be archived by using e.g. > CMake, and only maintaining the CMake project file. I'm not suggesting > to actually switch to CMake at this time, but I wanted to point out > that a guy called Pau Garcia i Quiles already seems to have created a > preliminary CMakeLists.txt file for Git [1], and also tried to build > Git for Windows using his CMake-generated MSVC project files. > > [1] "CMake-ifying git", http://www.elpauer.org/?p=324
We actually discussed this, and I challenged Pau to provide a recipe (a la /src/openssl/release.sh) that builds, installs and commits CMake.
There was no response after that challenge.
Ciao, Dscho