[task #15749] Printing programs that are being built in the middle of build commands

[Mohammad Akhlaghi]

URL:
  <https://savannah.nongnu.org/task/?15749>

                 Summary: Printing programs that are being built in the middle
of build commands
                 Project: Reproducible paper template
            Submitted by: makhlaghi
            Submitted on: Thu 13 Aug 2020 03:20:31 PM BST
         Should Start On: Thu 13 Aug 2020 12:00:00 AM BST
   Should be Finished on: Thu 13 Aug 2020 12:00:00 AM BST
                Category: Software
                Priority: 5 - Normal
                  Status: Postponed
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00

    _______________________________________________________

Details:

Currently, when Maneage is being configured, all the outputs of the build
process of many programs are printed in the terminal together and it is very
hard to see what is being built at every moment. The way I personally work is
to open a parallel terminal, go to the project's top directory and run
'./project --check-config'. 

But in some cases (like when building in Docker, or in the Continuous
Integration tests of task #15741) this is not possible because we only have
one terminal!

While talking with Mohammadreza on task #15741, this solution suddenly
occurred to me: we can make a phony target in the two 'basic.mk' and
'high-level.mk's and set that target to call './project --check-config' until
the final configuration-completion file is created. This will print the status
of the programs that are currently being built in the middle of all the build
outputs. 

My only worry now is that this will effectively occupy one of the system's
threads (and thus slow down the build!). If there was a way that would could
run some kind of back-ground job that would activate every N-seconds (without
occupying one thread), it would be great!

But anyway, I can't implement right now and it is mostly just cosmetic (we can
ultimately search for the final program target files in '.local/version-info'
manually), so I thought of leaving this here in case anyone comes up with a
solution in the meantime.




    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/task/?15749>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/