git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Giuseppe Crino' <giuscri@gmail.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Giuseppe Crino' <giuscri@gmail.com>, Johannes Sixt <j6t@kdbg.org>,
	git@vger.kernel.org
Subject: Re: How to build to debug with gdb?
Date: Wed, 28 Aug 2019 11:00:46 +0000	[thread overview]
Message-ID: <20190828110046.GB4450@instance-template-2.europe-west6-a.c.vaulted-journal-250706.internal> (raw)
In-Reply-To: <20190828103217.GA6400@szeder.dev>

On Wed, Aug 28, 2019 at 12:32:17PM +0200, SZEDER Gábor wrote:
> I don't think it's unusual at all that the 'install' target depends on
> 'all'.  A quick and incomprehensive survey of Makefiles from a few
> open source projects that I happen to have lying around seems to
> confirm this.
> 
> What might be unusual (but is rather convenient for developers) is
> that Git's build process checks the build flags, and rebuilds the
> whole thing after the flags changed.

Maybe I'm biased by my incompetence with Makefile's but since rebuilding
the project with `install` but different flags from the first make is
unusual this is worth mentioning to developers.

  reply	other threads:[~2019-08-28 11:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27 16:27 How to build to debug with gdb? Giuseppe Crino'
2019-08-27 17:55 ` Matheus Tavares Bernardino
2019-08-27 18:07   ` Randall S. Becker
2019-08-27 18:34 ` Johannes Sixt
2019-08-27 18:36 ` SZEDER Gábor
2019-08-28  8:15   ` Giuseppe Crino'
2019-08-28 10:32     ` SZEDER Gábor
2019-08-28 11:00       ` Giuseppe Crino' [this message]
2019-08-28 12:43         ` Giuseppe Crino'

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190828110046.GB4450@instance-template-2.europe-west6-a.c.vaulted-journal-250706.internal \
    --to=giuscri@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    --cc=szeder.dev@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).