Purpose :
Whenever we run makefile, we don't know when it ends. Especially when we don't know the makefile structure or new to a new makefile, we just run it and hope to end it soon. If we know how much we have to wait, it may be stopped to change a thing or two or just leave it and do something useful instead of waiting for it's end. So let's make a progress bar attached to makefile
Search Web :
Amazing this idea seems pretty new and unexplored region. Considering that there are so many makefile and no developer haven't developed any similar, I can't stop show respect on this. Though IDE gives progress bar, so this is only for those who have makefile.
GraphViz is a project which shows graph in a nice looking figure so if we can show the progress with this tree figure, it will be great. Though GraphViz is showing only static result so won't be able to update it dynamically. And by it's static nature, it seems not adequate on the purpose.
Possible implementation scenario 1 :
If we can parse makefile and go through it from start to end, all the compile and link detail we can get. Those detail tell us how many files we will compile and link and copy and do some others. With this count and with makefile result redirected to a progress bar appplication, the application can read result and count the number of compile and link occurence. This occurence can be progress.
So what we need is a parser of makefile and an application frontend which will get input from the makefile output. The parser can get the number of compile, link and other operations. This can be stored at a intermediate file. And the frontend application will decode each output line of make and if decoding finds any compile or link, it will increase occurence and will increase progress accordingly.
Considering that there are so many rules and tree structure and variable and predefinition, it seems we need a proper parser not a simple one. To be really useful, we need a complete makefile parser. And still there seems not an makefile parser. May need to look at gcc makefile. And this will really make things difficult.
How about if we can see the progress bar after second running. If we direct make result and getting the number of link and compile and store it's occurence count, we can see progress bar at the second make. Well though second time compile won't run at all if there is no modification so it won't work.
So using output from makefile seems a fault with incremental link. Need to check the makefile output with incremental link ? Can we catch skipped compile as a compilation with output ? If we can, we can proceed.
To do :
Check if we can catch skipped compile by incremental link.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Purpose :
Whenever we run makefile, we don't know when it ends. Especially when we don't know the makefile structure or new to a new makefile, we just run it and hope to end it soon. If we know how much we have to wait, it may be stopped to change a thing or two or just leave it and do something useful instead of waiting for it's end. So let's make a progress bar attached to makefile
Search Web :
Amazing this idea seems pretty new and unexplored region. Considering that there are so many makefile and no developer haven't developed any similar, I can't stop show respect on this. Though IDE gives progress bar, so this is only for those who have makefile.
GraphViz is a project which shows graph in a nice looking figure so if we can show the progress with this tree figure, it will be great. Though GraphViz is showing only static result so won't be able to update it dynamically. And by it's static nature, it seems not adequate on the purpose.
Possible implementation scenario 1 :
If we can parse makefile and go through it from start to end, all the compile and link detail we can get. Those detail tell us how many files we will compile and link and copy and do some others. With this count and with makefile result redirected to a progress bar appplication, the application can read result and count the number of compile and link occurence. This occurence can be progress.
So what we need is a parser of makefile and an application frontend which will get input from the makefile output. The parser can get the number of compile, link and other operations. This can be stored at a intermediate file. And the frontend application will decode each output line of make and if decoding finds any compile or link, it will increase occurence and will increase progress accordingly.
Considering that there are so many rules and tree structure and variable and predefinition, it seems we need a proper parser not a simple one. To be really useful, we need a complete makefile parser. And still there seems not an makefile parser. May need to look at gcc makefile. And this will really make things difficult.
How about if we can see the progress bar after second running. If we direct make result and getting the number of link and compile and store it's occurence count, we can see progress bar at the second make. Well though second time compile won't run at all if there is no modification so it won't work.
So using output from makefile seems a fault with incremental link. Need to check the makefile output with incremental link ? Can we catch skipped compile as a compilation with output ? If we can, we can proceed.
To do :
Check if we can catch skipped compile by incremental link.