Hello Wilfred!

05 Aug 21, Wilfred van Velzen wrote to Kai Richter:

 WV>>> It should be in the faq, or documented somewhere.

 KR>> Well, in a far far away past, there was something like RTFM.

 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".

True. I didn't understand that you are now much deeper into details of different modules. My point of view was on the basic sequence of the building process.

 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...

Ideally i wouldn't have to use 'make' at all. 'apt/rpm/pkg/yours install htick' should do the trick. ;) Maybe i'm too much used to husky but i don't see htick as a standalone programm. It's a part of a toolset and the base tool is huskybase. Once the huskymak.cfg of the huskybse is set up any other module should compile on the fly. The december issue was a bug. A global parameter for all husky modules in the huskymak.cfg was overrided. If a module doesn't follow the huskymak.cfg settings then it's worth a bug report.

Regards

Kai

--- GoldED+/LNX 1.1.4.7