Hello Michael!

*** Monday August 02 2021 13:41, you wrote to me:

 MF>> I'm in need of a tic file processor for Linux and was wondering
 MF>> if it's possible to compile 'htick' without the rest of the husky
 MF>> stuff.

 MF>> If that's not possible, what else would I need to build 'htick'.

 MD> You have to build Husky libraries before building htick. So first you
 MD> have to grab the sources.

 MD> mkdir ~/husky
 MD> cd husky
 MD> git clone https://github.com/huskyproject/huskylib.git
 MD> git clone https://github.com/huskyproject/smapi.git
 MD> git clone https://github.com/huskyproject/fidoconf.git
 MD> git clone https://github.com/huskyproject/areafix.git
 MD> git clone https://github.com/huskyproject/htick.git

 MD> Now you take the makefile configuration common for the subprojects:
 MD> wget https://raw.githubusercontent.com/huskyproject/huskybse/master/hu
 MD> skymak.cfg and update it according to your needs. It should be in the
 MD> same 'husky' directory. After that you may build and install htick.

 MD> cd huskylib
 MD> make && sudo make install
 MD> cd ../smapi
 MD> make && sudo make install
 MD> cd ../fidoconf
 MD> make && sudo make install
 MD> cd ../areafix
 MD> make && sudo make install
 MD> cd ../htick
 MD> make && sudo make install

 MD> You have htick now. If you used static linking (DYNLIBS=0 in
 MD> huskymak.cfg), you may delete the static libraries libhusky.a,
 MD> libsmapi.a, libfidoconfig.a, libareafix.a from LIBDIR you configured
 MD> in huskymak.cfg. It is not necessary to store them after you have
 MD> built htick.

Everything worked just fine apart from 'config' wasn't installed in the location that I'd defined in 'huskymak.cfg'. In fact, I don't think it got installed at all, so I just manually copied it to my desired location.

Thank you very much indeed for the clear and concise step by step instructions, very much appreciated.

Regards,
Martin

--- GoldED+/LNX 1.1.5-b20180707