Make script

On Mar 4, 5:07 pm, Vladimir Vassilevsky <antispam_bo...@hotmail.com>
wrote:
> CBFalconer wrote:
> > Vladimir Vassilevsky wrote:
>
> >>The minor mistake in makefile can result in a file not being
> >>rebuilt when it is required. This type of mistake is easy to do
> >>when you have different sorts of files and toolchains included
> >>into one project.
>
> > Then you have a mistake in your makefile, and it should get fixed.
>
> At first, the build mistake should get noticed. The files of the older
> revisions could be included without any warnings.
>
> > That way the mistake won't happen again.  Not really hard.
>
> It certainly will. The major weakness of make (as well as many other
> scripting tools) is there is no simple way to debug and verify their
> operation.

How is that different from any other tool? Write, test, debug, rinse,
repeat.

>
> Vladimir Vassilevsky
> DSP and Mixed Signal Design Consultanthttp://www.abvolt.com

toby wrote:
> On Mar 4, 5:07 pm, Vladimir Vassilevsky <antispam_bo...@hotmail.com>
> wrote:
>> CBFalconer wrote:
>>> Vladimir Vassilevsky wrote:
>>>> The minor mistake in makefile can result in a file not being
>>>> rebuilt when it is required. This type of mistake is easy to do
>>>> when you have different sorts of files and toolchains included
>>>> into one project.
>>> Then you have a mistake in your makefile, and it should get fixed.
>> At first, the build mistake should get noticed. The files of the older
>> revisions could be included without any warnings.
>>
>>> That way the mistake won't happen again.  Not really hard.
>> It certainly will. The major weakness of make (as well as many other
>> scripting tools) is there is no simple way to debug and verify their
>> operation.
> 
> How is that different from any other tool? Write, test, debug, rinse,
> repeat.
> 

And make *does* have some debugging tools (at least, gnu make does - I 
don't know about others).  You can easily print out variables such as 
current targets, and use dry-run modes to see what is going to happen. 
It's not a step-by-step debugger, but I expect most programmers can 
figure it out.

David Brown <david.brown@hesbynett.removethisbit.no> writes:

> And make *does* have some debugging tools (at least, gnu make does - I
> don't know about others).  You can easily print out variables such as
> current targets, and use dry-run modes to see what is going to
> happen. It's not a step-by-step debugger, but I expect most
> programmers can figure it out.

Actually there is a step-by-step debugger for GNU Make (version 3.80):
http://bashdb.sf.net/remake