There is another pattern for dependencies files, .P.
I use normally P, as I've seen in some sites when I wanted to learn about
automatic dependency generation.
--- El jue, 15/1/09, Kustaa Nyholm escribió:
> De: Kustaa Nyholm
> Asunto: Re: [Sdcc-user] SDCC deleted .d files?
> Para: sdcc-user@
Oops, a bit trigger happy today, works as adverticed, by bad, directory
did not exist!
Sorry for the interruption.
br Kusti
>>> kustaa.nyh...@planmeca.com 15.1.2009 10:28 >>>
When I try to compile as follows:
/usr/local/bin/sdcc -c -mpic16 -p18f4550 --disable-warning 85
--std-sdcc99 main.c -o
Thanks Raphael,
so I assume this a 'quirk' ie something that the developer(s) used
without considering
that there is a well established usage pattern for '.d' files.
On the second thought, I think it is a bug. Even if some targets use .d
files to output
debug information, under normal situations,
When I try to compile as follows:
/usr/local/bin/sdcc -c -mpic16 -p18f4550 --disable-warning 85
--std-sdcc99 main.c -o ../obj/main.o
I get:
main.c:174: error 4: 'fopen' failed on file '../obj/main.asm'
so obviously the compiler is trying to load the intermediate files from
the output directory
I do not think it is a SDCC problem. It is a make issue. Probably make will
interpret %.d files as intermediate files, and it deletes them by default. If
you put .d files in the PRECIOUS target, make will preserve them.
PRECIOUS: %.d
See the gnu make manual for more information at:
http://www.
Hi Kusti,
> After some tracking it seems that SDCC deletes file 'X.d' if I specify
> output file with '-o X.o'
>
> Is this how it should work? Is this different from gcc? If so is it a
> bug or feature?
At least some SDCC targets (e.g., pic16) use .d files to output debug
information (to debug
