Hello All,

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

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

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

All actions that need to be performed to build Husky programs are described in detail in "huskybse/install.asciidoc". To read this description, you need to open in a browser

https://github.com/huskyproject/huskybse

and click on the "INSTALL.asciidoc" file.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20180707