Re: RV: [Dev-C++] Why this bug? Error in the compilation of the Makefile.win

[Luigi S. <gi...@li...>]

On Tue, Jun 03, 2003 at 11:20:30AM +0200, Juli?n Calder?n Almendros wrote=
:
> The Makefile.win contains:
> =20
> --- BEGIN Makefile.win BEGIN ---
> [...]
> =20
> NadaMain.o: NadaMain.c C:/mingw/include/stdlib.h
> C:/mingw/include/_mingw.h C:/mingw/include/stddef.h =20
>                         $(CC) -c NadaMain.c -o NadaMain.o $(CFLAGS)
> --- END Makefile.win END ---
> The compiling of the project don=92t successful with error =93multiple
> targets in line (NadaMain.o: NadaMain.c =85.)=94.
> In the other hand, if I change the Makefile.win and write:=20
> --- BEGIN Makefile.win Changed BEGIN ---
> [...]
> =20
> NadaMain.o: NadaMain.c =20
>                         $(CC) -c NadaMain.c -o NadaMain.o $(CFLAGS)
> --- END Makefile.win Changed END ---
> and write =93mingw32-make =96fMakefile.win=94 all functions correctly.
> Is this problem due to a error configuration?.
> =20
> Thanks in Advance.
> =20
> Juli=E1n Calder=F3n Almendros

Hello Julien,

please forgive the awful look of the above quotation, my system is set to
display a limited amount of characters, it lacks some of those which you=20
have used.

Now back to your question. If you wish to have the list of dependency=20
files spread across more than one line, place a slash ('\') at the end of=
=20
each line (except the last one), this is the same thing one would do when=
=20
dealing with a C macro which does not fit on one line.

So, the dependency in the first version of your makefile should look like
the following:

NadaMain.o: NadaMain.c \
            C:/mingw/include/stdlib.h \
            C:/mingw/include/_mingw.h \
            C:/mingw/include/stddef.h =20

Indenting continuation lines should make things clearer.

Of course the second version of the makefile is OK because the dependency=
=20
lies on a single line. More details about syntax of Make may be found in=20
the manual, I once downloaded it from the site where djgpp is distributed=
=2E

If the behavior you describe is not the consequence of you manipulating
the file, then a bug report should be sent to Dev-C++ developers.

IMHO, "standard" header files (those which you get together with the comp=
iler)
should not be included in the dependency, because these are not under the
control of the programmer (unless he is developing/debugging the standard=
=20
library itself). However, including them will do no harm (probably a smal=
l=20
time loss because program Make has to check their time stamp).

--=20
>> gisan >>
A is for Apple.
		-- Hester Pryne