[mythtv] [mythtv-commits] Ticket #4397: win32 dependancy resolver and build script

buzz davidbuzz at gmail.com
Fri Jan 4 09:32:25 UTC 2008


>
>
> i think the problem is the patch in the script
> you show that the ifdef/endif are different but they are not (no // in
> front of them)


Hmm... I see what you mean,  I''ll redo the inlined patch, I think I
cut-n-pasted it wrong, I missed the ! marks.

>
>
> another suggestion (you must be getting fed up with me by now)


not at all, the feedback is great!

>
>
> in some steps you create a special file which indicates that the step
> has been completed, rather than rely on a file created as a side effect
> of the step. why not create a directory with such special files and do
> it for each step. that way, if something goes wrong and you want to run
> a particular step, but do not want to do the whole thing again, it is
> just a small matter of deleting that special file.


Yes, that was the whole point, and I do that frequently already, but I spose
having the "marker" files in their own folder is possibly a wise
move.... but the reality is also that I'm actually hoping to reduce/remove
as many of these artificial marker/s as possible, by determining more
accurate dependancies in the build process, and codeing them in.    Doing it
properly should allow the code to accurately "test" for each missing
component/step, and only re-execute those steps integral to the process.
I'll look at analysing some more of these dependancies, and see which
"marker" files I can get rid of to start with.   it might be we end up with
only 1 or 2 of them, or none.



> i reckon you are pretty close to the finished article. another couple of
> days and this script is ready for the big time.

hmm.. define big-time?



Buzz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-dev/attachments/20080104/7967acd7/attachment.htm 


More information about the mythtv-dev mailing list