[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to handle data/script files in a VPATH build ?
From: |
Ralf Wildenhues |
Subject: |
Re: How to handle data/script files in a VPATH build ? |
Date: |
Mon, 8 Feb 2010 20:48:49 +0100 |
User-agent: |
Mutt/1.5.20 (2009-10-28) |
* Steffen Dettmer wrote on Mon, Feb 08, 2010 at 11:15:52AM CET:
> On Sat, Feb 6, 2010 at 6:56 PM, <address@hidden> wrote:
> [...]
> > data-in-build-tree: data-in-source-tree
> > cp $(srcdir)/data-in-source-tree data-in-build-tree
>
> We typically write something like:
>
> # file /must/ be in current dir (builddir) for proprietary tool:
> __heap.o: lib/__dfl_heap.o
> cp -f $< $@
>
> Make finds $(srcdir)/lib/__dfl_heap.o via VPATH, if any, and
> sets `$<' accordingly
Using $< is portable only inside inference rules (.suf1.suf2 rules),
in target rules it is a GNU make-only feature. For non-GNU make,
you need to spell out the source file inside the rule commands.
Cheers,
Ralf
- How to handle data/script files in a VPATH build ?, Sylvestre Ledru, 2010/02/03
- Re: How to handle data/script files in a VPATH build ?, Peter Johansson, 2010/02/03
- Re: How to handle data/script files in a VPATH build ?, Sylvestre Ledru, 2010/02/06
- Re: How to handle data/script files in a VPATH build ?, Sylvestre Ledru, 2010/02/09
- Re: How to handle data/script files in a VPATH build ?, Ralf Wildenhues, 2010/02/09
- Re: How to handle data/script files in a VPATH build ?, Steffen Dettmer, 2010/02/10
- Re: How to handle data/script files in a VPATH build ?, Ralf Wildenhues, 2010/02/10
- Re: How to handle data/script files in a VPATH build ?, Steffen Dettmer, 2010/02/12
- Re: How to handle data/script files in a VPATH build ?, Dr. David Kirkby, 2010/02/12
- portability testing (was: How to handle data/script files in a VPATH build ?), Ralf Wildenhues, 2010/02/20