* 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 ar
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
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 re-wri
On Monday 2009-01-26 23:33, Adam Nielsen wrote:
>>> $ g++ -fPIC -c -o main.o main.cpp -I/usr/include/boost-1_37/ && g++ -o
>>> test.so main.o -shared
>>
>> This works since main.cpp is being compiled to main.o with PIC. However,
>> Boost
>> is not involved here so it proves nothing about Boost.
>
* 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 "sor
$ g++ -fPIC -c -o main.o main.cpp -I/usr/include/boost-1_37/ && g++ -o
test.so main.o -shared
This works since main.cpp is being compiled to main.o with PIC. However,
Boost is not involved here so it proves nothing about Boost.
It does prove something about Boost to me - as soon as I add the
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 everybod
Hi,
Andreas 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
EMPTY =
fo
On Mon, 26 Jan 2009, Adam Nielsen wrote:
I think it must have been the way Boost was compiled, because I get the same
error even when I don't link to any libraries:
$ g++ -c -o main.o main.cpp -I/usr/include/boost-1_37/ && g++ -o test.so
main.o -shared
Note that with the above, "main.o" wo
