Path: csiph.com!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: Effect of CPP tags
Date: Thu, 11 Jan 2024 12:16:13 -0800
Organization: None to speak of
Lines: 26
Message-ID: <87wmsfmxrm.fsf@nosuchdomain.example.com>
References: <umet9d$3hir9$1@dont-email.me> <8734v6p5s1.fsf@nosuchdomain.example.com> <unke3h$25ia0$1@dont-email.me> <unkhql$25uof$1@dont-email.me> <unkkp3$26g9o$1@dont-email.me> <87ttnmnjdb.fsf@nosuchdomain.example.com> <unkp1b$270v8$1@dont-email.me> <ZSmnN.151217$c3Ea.70659@fx10.iad> <unkuhp$27i0v$2@dont-email.me> <unlqqa$2eqts$2@dont-email.me> <U7ynN.143065$Wp_8.30410@fx17.iad> <unmmnd$2jair$1@dont-email.me> <87edepnich.fsf@nosuchdomain.example.com> <unmqsg$2jvva$1@dont-email.me> <unmu6b$2kh81$1@dont-email.me> <20240110133135.834@kylheku.com> <unn65q$2lr2i$1@dont-email.me> <20240110182957.444@kylheku.com> <unokb1$2vmkh$1@dont-email.me> <20240111081109.274@kylheku.com> <unpd89$33jlu$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Info: dont-email.me; posting-host="44c5271f25a14e9fb71ab01150cdf04f"; logging-data="3289240"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19TSyKfMA/LQkNztoFTaSsi"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Cancel-Lock: sha1:Jxj8riMFUC624clubpLjY0d/cbA= sha1:ixPcQDD7qEKcvJBUg8IJE7OSVgc=
Xref: csiph.com comp.lang.c:380044

bart <bc@freeuk.com> writes:
[...]
> 'make' looks like it wants to be similarly informal, but there there
> is no strong environment, only the name of the current directory,
> which might contain /anything/. There is no real context.

No real context??

The context is typically the current directory, all its direct and
indirect subdirectories, and their contents -- in other words, the
entire project.  Or the context can be whatever you want it to be.
"make" is a very general tool (with some defaults for more specific
uses).  You can write a Makefile to do just about anything that
can be done on a computer; building a project from source is just
the most common use case.

There are plenty of less generic build tools that work by generating
and invoking a Makefile -- which is a perfectly sensible thing to do,
since "make" already exists.  And of course there are other tools
that do similar things without using "make" -- also a perfectly
sensible thing to do.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Medtronic
void Void(void) { Void(); } /* The recursive call of the void */