On Thu, Apr 2, 2015 at 10:38 AM, Paul Smith wrote:
> On Wed, 2015-04-01 at 17:37 +0530, Basil Mathew wrote:
> > This is a copy of the e-mail that I have send to Christian.
>
> You don't need to forward another copy: that's the beauty of a mailing
> list: everyone gets all the mail :).
>
>
That's
Hello Mr. Smith,
Thank you for the reply.
This is a copy of the e-mail that I have send to Christian.
My apologies for not having mentioned the information about the "-include"
statement. To be honest, the possibility that you described did not occur
to me.
But, having said that, I have to tell
Hello Christian,
Thank you for the reply. My apologies for not having mentioned the
information about the "-include" statement. To be honest, the possibility
that you described did not occur to me.
But, having said that, I have to tell you that the way we include the d
files is a bit different.
On Wed, 2015-04-01 at 09:46 +0530, Basil Mathew wrote:
> In our build environment, the compilation of a C-file into the object file
> is a 2 step process as described below. We use the GNU’s “cpp.exe” to
> generate the dependency file and then compile the C source file using the
> specific compiler
Hi.
The dependency files are gendered first most likely because they are
included with a statement like
-include $(sources_c:.c=.d)
By the way, to me or doesn't make sense to make the object file dependent
on the dependency file.
Regards,
Christian
On Apr 1, 2015 10:05 AM, "Basil Mathew" wrote
Dear Support,
My name is Basil Mathew. I work as a support engineer, for a Windows
Eclipse based build platform that uses GNU Make scripts, in my
organization. I have been asked to take over the GNU Make script support
and maintenance for the future. I was going through our GNU Make scripts
for bu
