On Jan 28, 2009, at 1:42 AM, Jeff King wrote:
On Tue, Jan 27, 2009 at 11:37:21PM -0800, Junio C Hamano wrote:
Just to be sure we are on the same page. My directory structure
has a
top/src/git-1.6.1 and top/build/git.1.6.1. The src/git-1.6.1 is
the
tar ball. The build/git-1.6.1 starts out empty. I cd into it and
then do: ../../src/git-1.6.1/configure <options> After this
completes, you can do "make".
I don't see how this would work without automake support, which
git does
not have.
... nor want to have ;-).
Heh. Yes, in case there was any confusion: I don't want my statement
in
any way to be construed as a suggestion to support automake.
I would not be opposed to it if it somehow enhanced some users'
experience without bothering people who didn't want to touch it (like
the way that autoconf support is implemented). But I don't see how
that
would be possible.
Thats fine. I didn't know if this was a "known" situation or not so I
just mentioned it.
As I mentioned, most open source code supports this style of build. I
have no idea
what it would take to get it to work.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
