Federico Bruni writes:
>
>
> Il giorno gio 29 mar 2018 alle 18:18, th...@vmware.com ha scritto:
> > Federico Bruni writes:
> > >
> > >
> > > Il giorno gio 29 mar 2018 alle 15:56, Paul Smith
> > ha
> > > scritto:
> > > > On Thu, 2018-03-29 at 14:09 +0200, Federico Bruni wrote:
> >
Il giorno gio 29 mar 2018 alle 18:18, th...@vmware.com ha scritto:
Federico Bruni writes:
>
>
> Il giorno gio 29 mar 2018 alle 15:56, Paul Smith
ha
> scritto:
> > On Thu, 2018-03-29 at 14:09 +0200, Federico Bruni wrote:
> >> VPATH = \
> >>$CURDIR/src
> >
> > This is wrong. Thi
Federico Bruni writes:
>
>
> Il giorno gio 29 mar 2018 alle 15:56, Paul Smith ha
> scritto:
> > On Thu, 2018-03-29 at 14:09 +0200, Federico Bruni wrote:
> >> VPATH = \
> >>$CURDIR/src
> >
> > This is wrong. This expands the make variable $C and appends the
> > string "URDIR/src".
Il giorno gio 29 mar 2018 alle 15:56, Paul Smith ha
scritto:
On Thu, 2018-03-29 at 14:09 +0200, Federico Bruni wrote:
VPATH = \
$CURDIR/src
This is wrong. This expands the make variable $C and appends the
string "URDIR/src". Since C is not set (most likely) you'll get:
VPATH = UR
On Thu, 2018-03-29 at 14:09 +0200, Federico Bruni wrote:
> VPATH = \
> $CURDIR/src
This is wrong. This expands the make variable $C and appends the
string "URDIR/src". Since C is not set (most likely) you'll get:
VPATH = URDIR/src
which doesn't exist, so this is a no-op.
You meant:
Dear Frederico,
I just read (again) this:
http://make.mad-scientist.net/papers/how-not-to-use-vpath/
you should do this too.
Best,
Bert
On Thu, Mar 29, 2018 at 9:21 AM, Federico Bruni wrote:
> Hi
>
> I'm having problem with a simple Makefile which uses a pattern rule to
> generate PDF files f
Dear Bert
Thank you for the pointer!
I read somewhere on Stackoverflow that VPATH may be used for targets as
well.. can't find the link now.
Anyway, I've just tried to apply what I understood from below article,
but I'm still getting the same error.
What I've changed in the Makefile:
- I've
On 12/5/06, Brendan Bridgford <[EMAIL PROTECTED]> wrote:
...
Here's a fuller picture of what I'm trying to do (pretend for a moment that
my syntax works):
...
I want to apply essentially the same rules to multiple targets without
explicitly listing each target (i.e. a variable target name), wh
Thanks Paul.
I understand now why this doesn't work but I may have mislead you on my end
goal. Is there a way to set a global variable from the context of a target?
Here's a fuller picture of what I'm trying to do (pretend for a moment that
my syntax works):
.PHONY = foobar
foobar : a = foo
fo
On Tue, 2006-12-05 at 20:19 -0500, Brendan Bridgford wrote:
> I'm trying to use a variable as a target without much luck.
> .PHONY = foobar
> foobar : a = foo
> foobar : b = bar
> c=$(a)$(b)
>
> When I invoke
> >make foobar
>
> ... it returns:
> make: *** No rule to make target `foobar'. Stop
Daniel Harezlak wrote:
Hello,
I have a problem with pattern rules. I simplified my Makefile and got
the following:
.PHONY: all create
all: create file.out
create:
touch file.ext
%.out : %.ext
mv file.ext file.out
After invoking make I get "make: *** No rule to make target
%% "Tobias Contreras" <[EMAIL PROTECTED]> writes:
tc> I am unable to add all header files as prerequisite using %
tc> wildcard,
"%" is not a wildcard. It's a pattern.
If used in a pattern rule, it can match _ONE_ file as long as the stem
(the part that matches "%") is the same between the t
12 matches
Mail list logo