All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: David Lang <david@lang.hm>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Is there a way to have a local version of a header file?
Date: Sat, 18 Mar 2017 16:11:50 -0700	[thread overview]
Message-ID: <xmqqy3w2yybt.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <nycvar.QRO.7.75.62.1703181539310.3797@qynat-yncgbc> (David Lang's message of "Sat, 18 Mar 2017 15:40:08 -0700 (PDT)")

David Lang <david@lang.hm> writes:

>> Ship a config.h.sample file, have a Makefile rule that is forced to
>> run before any compilation happens that checks if config.h exists
>> and then created it if missing by copying config.h.sample over, and
>> then all other source files can include config.h without having to
>> know anything about config.h.sample's existence.
>>
>> Did I miss something?
>
> There is no makefile with the arduino IDE/build system :-(

How does "the build system" you want to make it work with actually
work?  Is it incapable of "compiling" a "source file" into an
"object file" that happens to be a text using an arbitrary
"compiler"?

I was hoping that readers are imaginative enough to replace Makefile
with whatever way things are normally built with when reading my
message, and the reader can just replace "source file" with
"config.h.sample", "compiler" with "test -f config.h || cat
config.h.sample >config.h" and "object file" with "config.h".

  reply	other threads:[~2017-03-18 23:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 14:29 Is there a way to have a local version of a header file? David Lang
2017-03-18 14:48 ` Ævar Arnfjörð Bjarmason
2017-03-18 14:58   ` David Lang
2017-03-18 17:08     ` Ævar Arnfjörð Bjarmason
2017-03-18 18:05       ` Junio C Hamano
2017-03-18 22:40         ` David Lang
2017-03-18 23:11           ` Junio C Hamano [this message]
2017-03-18 23:22             ` Samuel Lijin
2017-03-19 21:33               ` Johannes Sixt
2017-03-19  0:19             ` David Lang
2017-03-18 18:21       ` Jakub Narębski

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=xmqqy3w2yybt.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=david@lang.hm \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.