Hi Kai,

On 2021-08-06 21:38:20, you wrote to me:

 KR>>> The concept is well described from my point of view.

 WV>> Well I managed to compile htick in december last year. But I needed
 WV>> some help with conflicting and not all that clear information in the
 WV>> documentation of the different modules. (You even commented in the
 WV>> thread)

 WV>> So I wouldn't call it "well described".

 KR> True. I didn't understand that you are now much deeper into details of
 KR> different modules.

I am?

 KR> My point of view was on the basic sequence of the building process.

And that process isn't very well documented in my opinion.

 WV>> Ideally you should only have to type 'make' once in the htick
 WV>> directory, which would automatically make the different husky
 WV>> libraries in the right order and with the right options, that htick
 WV>> depends on, if they are not yet build and installed...

 KR> Ideally i wouldn't have to use 'make' at all. 'apt/rpm/pkg/yours install
 KR> htick' should do the trick. ;)

Wouldn't that be nice! ;)

But you would have to convince a lot of distribution maintainers to support husky, just for maybe a few hundred (at best) users... Ain't gona happen.

 KR> Maybe i'm too much used to husky but i don't see htick as a standalone
 KR> programm.

It is for me.

 KR> It's a part of a toolset and the base tool is huskybase. Once the
 KR> huskymak.cfg of the huskybse is set up any other module should compile
 KR> on the fly.

Is that documented? ;-)


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815