Hi Michael,

On 2021-09-30 14:03:42, you wrote to All:

 MD> Husky has two sets of makefiles: "universal" suitable for different
 MD> operating systems and "legacy" suitable only for a specific operating
 MD> system. I didn't touch the second ones, but I rewrote the first ones from
 MD> scratch. What shortcomings made me do this, and what has changed? Normally,
 MD> if we built a program using a makefile, re-accessing the makefile should
 MD> not cause a rebuild. It didn't happen. A properly written makefile should
 MD> allow parallel execution. That didn't happen either. And finally, to build
 MD> each subsequent Husky subproject, it was necessary to install all the
 MD> previous ones. It was inconvenient.

 MD> Now there is a list of programs that we want to build in the "huskymak.cfg"
 MD> configuration file, and they are all built at once, in one call of the
 MD> makefile, without the need for intermediate installations. Parallel
 MD> execution works.

 MD> Now there is a central makefile managing the makefiles of subprojects. It
 MD> lies in "huskybse". There are also scripts there that perform auxiliary
 MD> actions and run the build. There is no need to download the next version of
 MD> programs separately before build. If there were any changes, they would be
 MD> downloaded automatically. This also applies to makefiles, scripts, and the
 MD> "huskymak.cfg" configuration.

Cool!

I'll try it out in the coming weeks...


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815