From: antos@math.muni.cz (David Antos)
Cc: ntg-context@ntg.nl
Subject: Re: make files
Date: Sat, 9 Jun 2001 11:35:14 +0200 (CEST) [thread overview]
Message-ID: <20010609093514.0D5C852352@bart.math.muni.cz> (raw)
In-Reply-To: <3.0.6.32.20010608113628.00aab850@server-1> from Hans Hagen at "Jun 8, 2001 11:36:28 am"
> >The colon (:) *must* follow the target (e.g. no spaces), and the execution
> >line(s) must be preceeded by a tab (Ctrl+I, ASCII 9) character.
>
> That works, is this windows specific or does the linux make also need that
> <tab> char? [i hate tabs]
>
The <tab> syntax is make-specific. It is very very supid. The GNU make
only adds some types of rules to ``standard'' make (e.g., some kind of
`wildcards', more comfortable ways to handle filenames). Nevertheless
the <tab> syntax will survive everything.
D.A.
P.S.: Some `too-inteligent' text editors convert your tabs into spaces
(and the user doesn't know that option is set). If your Makefile doesn't
want to work and there is no reason why, check this.
It happened to me...
next prev parent reply other threads:[~2001-06-09 9:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-08 8:31 Hans Hagen
2001-06-08 8:53 ` Marc van Dongen
2001-06-08 9:00 ` Gilbert van den Dobbelsteen
2001-06-08 9:25 ` Taco Hoekwater
2001-06-08 9:38 ` Marc van Dongen
[not found] ` <Pine.LNX.4.30.0106081058490.20802-100000@panter.soci.aau.d k>
2001-06-08 9:36 ` Hans Hagen
2001-06-08 9:56 ` Marc van Dongen
2001-06-09 9:35 ` David Antos [this message]
2001-06-10 20:20 ` Hans Hagen
2001-06-11 5:53 ` Gilbert van den Dobbelsteen
2001-06-11 11:12 ` Marc van Dongen
2001-06-08 17:25 ` Berend de Boer
2001-06-09 9:34 ` Uwe Koloska
2001-06-10 20:10 ` Hans Hagen
2001-06-11 7:21 ` Berend de Boer
2001-06-11 11:09 ` Marc van Dongen
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=20010609093514.0D5C852352@bart.math.muni.cz \
--to=antos@math.muni.cz \
--cc=ntg-context@ntg.nl \
/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).