From: Vincent van Ravesteijn <vfr@lyx.org>
To: jupiter.hce@gmail.com
Cc: git@vger.kernel.org
Subject: Re: 1.7.10.3 configure does not generate Makefiles
Date: Mon, 04 Jun 2012 14:14:37 +0200 [thread overview]
Message-ID: <4FCCA6AD.7030202@lyx.org> (raw)
In-Reply-To: <20120603233420.GA3002@gmail.com>
> In reply to this post by Erik Faye-Lund-2
> I thought I've sent the comments, but did not see on the forum, sorry
> if it is duplicated.
> Thanks for all response. The Makefile is included in the source
> directory, but I'd like to build the git in a separated build
> directory, not the source directory. Is it possible to build the
> git in a separated build directory? Or if there is any way to
> geneerate a Makeifle in a separaed build directory?
I've written some CMake files to generate Makefiles and/or MSVC project
files. It is still experimental, but it supports i18n, and building and
running the test suite (also for MSVC).
Vincent
next prev parent reply other threads:[~2012-06-04 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 23:32 1.7.10.3 configure does not generate Makefiles jupiter.hce
2012-05-30 11:38 ` Erik Faye-Lund
2012-06-01 11:48 ` hce
2012-06-03 23:34 ` jupiter.hce
2012-06-04 12:14 ` Vincent van Ravesteijn [this message]
2012-05-30 11:38 ` David Michael Barr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FCCA6AD.7030202@lyx.org \
--to=vfr@lyx.org \
--cc=git@vger.kernel.org \
--cc=jupiter.hce@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).