git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Bito <jwbito@gmail.com>
To: git@vger.kernel.org
Subject: Re: integrating make and git
Date: Wed, 15 Apr 2009 14:34:33 -0700	[thread overview]
Message-ID: <3ae83b000904151434t5c3c85ebvec391ec29981ff79@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0904151654330.10753@iabervon.org>

If you're not already using make for a project, think before you
start.  If you're building something that will go into distribution in
source form, you probably should need to use it (via automake &
autoconf).  For the stuff that I'm doing in a more focused
environment, I use boost-build/bjam
(http://www.boost.org/users/download/boost_jam_3_1_17).  This provides
very clean organization of release/debug builds as well as a much more
expressive language than make.

It's easy to create makefiles that are quite brittle and the plumbing
to establish portable builds is really complex.  I was away from make
working on Java & Ruby for almost ten years.  Though I have more than
10 years of experience with make, I'm very happy to have replaced gobs
of makefile code with the boost-build package and a few, short
Jamfiles.

YMMV
John

  reply	other threads:[~2009-04-15 21:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 15:19 integrating make and git E R
2009-04-15 15:41 ` Matthieu Moy
2009-04-15 16:20 ` Daniel Barkalow
2009-04-15 16:47   ` E R
2009-04-15 17:30     ` Robin Rosenberg
2009-04-16  8:26       ` Jeff King
2009-04-16  9:55         ` Matthieu Moy
2009-04-16 12:50           ` Nguyen Thai Ngoc Duy
2009-04-15 21:01     ` Daniel Barkalow
2009-04-15 21:34       ` John Bito [this message]
2009-04-16  3:50 ` Ben Jackson
2009-04-16  8:05   ` David Kågedal
2009-04-17 17:24     ` Dmitry Potapov
2009-04-18  7:03 ` Ealdwulf Wuffinga

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=3ae83b000904151434t5c3c85ebvec391ec29981ff79@mail.gmail.com \
    --to=jwbito@gmail.com \
    --cc=git@vger.kernel.org \
    /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).