The reason is quite simple - there are so many different ways to build -
and reconfiguring takes a lot of time.
cmake supports out of source builds - thus you can build mutliple
configurations at the same time easily.
Marc Weber
--
--
You received this message from the vim_dev maillist.
Do
Vim-Cocoa, for OSX system, https://code.google.com/p/vim-cocoa/ has a cmake
file. But I think,it is not a good idea to change to.
The old make or nmake doesn't change frequently, and it's working well.
Also, you can take a look of scons, this page with a list of projects using
this building
Excerpts from Zulox4's message of Sun May 26 23:54:33 +0200 2013:
The old make or nmake doesn't change frequently, and it's working well.
1) configure is slow, if you need to run it once only it doesn't matter.
If you have to test multiple cases:
If you want to test 4 cases:
- no python
-
On Mon, May 27, 2013 at 12:38:09AM +0200, Marc Weber wrote:
Excerpts from Zulox4's message of Sun May 26 23:54:33 +0200 2013:
The old make or nmake doesn't change frequently, and it's working well.
1) configure is slow, if you need to run it once only it doesn't matter.
If you have to test
On Monday, May 27, 2013 12:38:09 AM UTC+2, MarcWeber wrote:
Excerpts from Zulox4's message of Sun May 26 23:54:33 +0200 2013:
The old make or nmake doesn't change frequently, and it's working well.
1) configure is slow, if you need to run it once only it doesn't matter.
If you have
