Ben Schmidt wrote:
> >> Another thing that's causing a bit of trouble is src/auto/config.mk. A
> >> 'stub file' is in version control, but it gets regenerated during the
> >> build, so always shows up as a modified file. Then it has to be avoided
> >> when commiting changes locally or updating to different points in
> >> history, etc.. Could we perhaps remove it from version control?
> >> Actually, probably better is to rename it, and include a command in
> >> whatever script is used to prepare distributions to copy it into place
> >> for inclusion in those. Then it wouldn't get in the way and make it
> >> difficult to prepare patches, etc..
> >
> > Problem is that when typing "make" that file is needed. It must exist,
> > even if it's only an empty file. Thus "hg pull" must obtain it.
> > Since preparing patches is not a common operation, it's better to put
> > the work there.
>
> Is this because Vim needs to build with make without first doing
> ./configure? In that case, doesn't ./configure regenerate the Makefiles
> anyway, so the default Makefiles could reference a different file, but
> when ./configure generates new ones, they could reference the
> ./configure-generated config.mk?
Configure is run by make, and configure generates auto/config.mk.
The other Makefiles are not changed by configure.
--
"A clear conscience is usually the sign of a bad memory."
-- Steven Wright
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
