Dear all,
We recently noticed a few undefined variables in our makefiles.
We would like to use --warn-undefined-variables to track them, e.g. on
our CI infrastructure, but we find it problematic that the warning can
not be turned into an error.
Am I correct that there is currently no way to achie
Hi all
Say I would like to reproduce the behavior of make. How exactly does
make decide if a binary is 'up to date'?
Maybe something like this?:
https://unix.stackexchange.com/questions/372857/compare-two-file-modification-dates
But how exactly?
Thanks a lot for any answer,
Chris
Hi Chris,
Make uses file existence and last-modified timestamps to determine if a
target is newer than it's prerequisites. There are other tools that use
checksums like md5, but make only uses presence and timestamps.
John
On Thu, May 2, 2019 at 11:52 AM wrote:
> Hi all
>
> Say I would like t
Hi Sébastien,
I've not heard of that tool, but it sounds useful.
Unfortunately we now use cmake internally, but a while ago I wrote
some GNU makefile code to perform some checks like this for our rather
complex GNU make-based build system of the time. See the attached
file; it should still work a
Dear Duane,
Many thanks for your response!
You are right, the code is rather straightforward and at the same time I
find it clever! In particular, I like the fact that, because of the
options you are using, you don't need to use grep to figure out whether
there are warnings or not. We would have
On 2019-05-02 18:31, Sébastien Hinderer wrote:
Dear Duane,
Many thanks for your response!
You are right, the code is rather straightforward and at the same time
I
find it clever! In particular, I like the fact that, because of the
options you are using, you don't need to use grep to figure ou
Kaz Kylheku (gmake) (2019/05/02 19:48 -0700):
> On 2019-05-02 18:31, Sébastien Hinderer wrote:
> > Dear Duane,
> >
> > Many thanks for your response!
> >
> > You are right, the code is rather straightforward and at the same time I
> > find it clever! In particular, I like the fact that, because o
On Fri, May 3, 2019 at 1:31 PM Sébastien Hinderer
wrote:
> Dear Duane,
>
> Many thanks for your response!
>
> You are right, the code is rather straightforward and at the same time I
> find it clever! In particular, I like the fact that, because of the
> options you are using, you don't need to us
On Fri, May 3, 2019 at 2:48 PM Kaz Kylheku (gmake)
<729-670-0...@kylheku.com> wrote:
> Let's try it in a project of mine:
>
>~/txr$ make --warn-undefined-variables --silent --dry-run clean 2>&1
> > /dev/null
>Makefile:32: warning: undefined variable `CFLAGS'
>Makefile:33: warning: unde
