Hey 👋 I wonder if bmakelib's `timed` could help:
https://github.com/bahmanm/bmakelib/blob/main/doc/timed.md
Shameless plug: I am the author 😅
--
Bahman Movaqar (he/him)https://linktr.ee/bahmanm
On Wed, 23 Jul 2025 at 10:33, Ross Burton wrote:
> Hi,
>
> Is there a way
On Wed, 2 Jul 2025 at 20:11, Tim Murphy wrote:
> On Wed, 2 Jul 2025 at 22:40, Bahman Movaqar wrote:
>
>> Somehow in the same vein is the work I did in bmakelib:
>> https://github.com/bahmanm/bmakelib/blob/main/doc/logged.md
>>
> That library is impressive.
>
T
configurable OR default to the
user's locale.
- The log prefix should either be configurable (e.g. passed as a parameter)
OR be in the form of `FILENAME:LINENO`
- Should we stop at `info` and not expand it to implement the well-known
log levels, such as WARN and ERROR?
--
Bahman Movaqar (he/him)
s
[2] https://hub.docker.com/r/bdockerimg/bmakelib
[3] https://github.com/bahmanm/bmakelib/releases
--
Bahman Movaqar (he/him)
Problem solver ● Software engineer ● Hands-on leader
https://linktr.ee/bahmanm
On Sat, 2025-04-05 at 21:06 -0700, carl hansen wrote:
> FYI
>
> https://gmsl.jgc.org/
On Tue, 2023-10-31 at 17:14 -0400, Benjamin Tilley wrote:
> Follow-up Comment #1, bug #64571 (project make):
>
> I'm also interested in this feature. I often find when coming back to
> an old
> project I want a quick way to list the possible targets so that I
> remember
> what `make` invocation I
Follow-up Comment #1, bug #64818 (project make):
I think the different is that in the case of suffix, you can simply omit '%'
.
That is instead of $(objects:%.c=%.o) you can conveniently write
$(objects:.c=.o).
___
Reply to this item at:
On Wed, 2023-10-04 at 23:20 +0200, Till Backhaus wrote:
> This rather short Makefile shows exponential runtime depending on the
> number of variables.
> export
>
> VAR_1 ?= $(shell echo 1)
> VAR_2 ?= $(shell echo 2)
> VAR_3 ?= $(shell echo 3)
> VAR_4 ?= $(shell echo 4)
> VAR_5 ?= $(shell echo 5)
On Wed, 2023-09-27 at 17:17 +0200, Markus F.X.J. Oberhumer wrote:
> Thanks for trying to help me understanding this issue.
It's a learning process for me too 🙂 Interesting topic!
>
> ### BEGIN Makefile
> FOO +=
> build/%: BAR +=
> build/release: ; @echo "FOO='$(FOO)' BAR='$(BAR)'"
> ### END
>
I certainly tried out your snippet the first time before replying 🙂
To my mind, what you're missing is the fact that `build/% : BAR +=' is
evaluated as part of `build/release'.
It is no different than the following snippet from the manual:
🙶
objects = foo.o bar.o
foo.o : defs.h
bar.o : defs.h te
Invoking make like `make FOO=X BAR=Y' causes Make to consider `FOO' and
`BAR' as special recursive/deferred variables.
>From GNU Make manual:
> all ordinary assignments of the same variable in the makefile are
> ignored; we say they have been overridden by the command line
> argument.
Each on
ail Code: C7004
> 1460 National Road
> Columbus, Indiana 47201
> United States
>
> -Original Message-
> From: Bahman Movaqar
> Sent: Tuesday, September 26, 2023 12:11 PM
> To: Ed L Wolf ; bug-make@gnu.org
> Subject: Re: Problem setting a variable inside a target
&
_SETUP)/McData-copyright-can.a2l
> $(DIR_A2LGEN_SETUP)/McData-setup.a2l
> @echo "A2L Supplier folder not available"
> endif
>
> Ed L Wolf
> Technical Advisor - Embedded Software
> e.l.w...@cummins.com
> Cummins Inc.
> Mail Code: C7004
> 1460
On Sun, 2023-09-24 at 17:23 +, Ed L Wolf wrote:
>
> ifneq ($(wildcard $(DIR_SUPPLIER)),)
> ...
> > $(eval SUPPLIER_A2l := $(sort $(shell find $(DIR_A2LGEN_SUPPLIER) -
> > type f -name "*.a2l")))
> ...
> ifeq ($(SUPPLIER_A2l),"*.a2l")
>
Quickly skimming through your co
13 matches
Mail list logo
