On Sat, May 2, 2020 at 9:18 PM Junio C Hamano <gitster@xxxxxxxxx> wrote:
>
> Sibi Siddharthan <sibisiddharthan.github@xxxxxxxxx> writes:
>
> >> How about contrib/cmake/?
> >>
> >
> > The CMakeLists.txt will be non-functional if it in any other directory except
> > the root source directory. To help users we can,
> > add some instructions in INSTALL on how to use the script.
> > OR
> > create a dummy CMakeLists.txt in the root directory which just
> > says
> > `message("Copy and Replace the CMakeLists from `whatever-folder` to here")`
> > along with some instructions if necessary. This is what LLVM does for autoconf.
>
> Isn't there a corresponding feature to make's "-f" option to specify
> which file to read instructions from?
Sadly, CMake expects CMakeLists.txt only, nothing else.
>
> As you say, an extra instruction in INSTALL file to tell users to
> copy from contrib/cmake may workable, though it is unsatisfactory.
> But the other one will not simply work. If we need to have a new
> file with string "CMake" in its name at the top-level *anyway*, we
> should have the real thing to reduce one step from those who want to
> use it. Those who do not want to see "CMake" at the toplevel are
> already harmed either way, if is a dummy or if it is the real thing.
In your opinion, what would be the best way to communicate with users, there is
an optional CMake build system for git?
Thank You,
Sibi Siddharthan
>
> Thanks.
