Hello Martin,

Monday August 02 2021, Martin Foster wrote to All:

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

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

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

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

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

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

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

Michael

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