Re: #include in a C file

[ali hagigat]

This makes each ‘.d’ file depend on all the source and header files
that the corresponding
‘.o’ file depends on. make then knows it must regenerate the
prerequisites whenever any of
the source or header files changes.
-------------------------------------------------------------------------------------------------------------------------
What is inside each .d file?
When a source or header file changes, what prerequisites will be generated?


On 12/5/10, Sam Ravnborg <address@hidden> wrote:
> On Sat, Dec 04, 2010 at 02:00:20PM +0330, ali hagigat wrote:
>> Thank you for the reply. When i was reading the section 4.13 of the
>> manual, first i learned that if we use -M option,  compiler will
>> generate some prerequisites for each #include of the C source file.
>> But then the manual talks about having one makefile for each C source
>> file. I am wondering what is the relationship of -M and having one
>> makefile for every C file?
>
> If you have 10 "gcc -m" running in parallel then you need
> separate files otherwise they would try to write to the same file.
>
>       Sam
>