Hi,
Andreas roe...@users.sf.net writes:
I just had an ingenious idea to limit conflicts in versioning systems.
When you specify a list of files for a rule you put every file in a line like
this.
fileA.c \
fileB.c \
fileC.c
One slightly ugly-looking approach I've seen is
Hello Andreas,
* Andreas wrote on Sun, Jan 25, 2009 at 06:42:52PM CET:
fileA.c \
fileB.c \
fileC.c
[...]
This is not nice so I thought well let's add a backslash after the
last file and add an empty line at the end. Then there's no need to
modify the fileC line and everybody
* Andreas wrote on Sun, Jan 25, 2009 at 06:42:52PM CET:
fileA.c \
fileB.c \
fileC.c
[...]
I do it this way:
NULL=
...
FOO= \
fileA.c\
fileB.c\
$(NULL)
BAR= \
fileC.c\
fileD.c\
$(NULL)
Mostly I do this so it is easy for me to sort
On Mon, 26 Jan 2009, Ralf Wildenhues wrote:
Jan already provided a way around this. Here's why automake warns about
it at all: it is not portable to have a backslash followed by a blank
line, as some make implementations are rather unpredictable with it:
However, Automake could offer to
Am Montag, 26. Januar 2009 schrieb Ralf Wildenhues:
Hello Andreas,
* Andreas wrote on Sun, Jan 25, 2009 at 06:42:52PM CET:
fileA.c \
fileB.c \
fileC.c
[...]
This is not nice so I thought well let's add a backslash after the
last file and add an empty line at the end.
* Bob Friesenhahn wrote on Tue, Jan 27, 2009 at 02:47:26AM CET:
On Mon, 26 Jan 2009, Ralf Wildenhues wrote:
Jan already provided a way around this. Here's why automake warns about
it at all: it is not portable to have a backslash followed by a blank
line, as some make implementations are
Hello everybody,
I just had an ingenious idea to limit conflicts in versioning systems.
When you specify a list of files for a rule you put every file in a line like
this.
fileA.c \
fileB.c \
fileC.c
now if 2 independent people add another file fileD and fileE to that list you
On Sunday 2009-01-25 18:42, Andreas wrote:
When you specify a list of files for a rule you put every file in a line like
this.
fileA.c \
fileB.c \
fileC.c
now if 2 independent people add another file fileD and fileE to that list you
have a conflict because both of them modify the
