Subj : Setting up Husky
To   : Sparky
From : Accession
Date : Sat Jul 17 2021 07:08 am

On 14 Jul 2021, Sparky said the following...
 
 Sp> Well I have to give my hat off to all of you that have set up Husky, I
 Sp> have spent close to a month trying to get it set up and running and have
 Sp> now decided it is too complex/not enough clear documentation for me so I
 Sp> am scrapping my linux box and just going to continue running Mystic on
 Sp> win32. Some of my major issues with Husky was trying to compile Fidoconf
 Sp> and getting an error I could not find an answer for, Running tparser and
 Sp> have switches autoAreaCreate on/autoFileCreate on cause errors and not
 Sp> being able to find documentation that describes those switches. 

Not sure if you're even interested in this topic any more, but it shouldn't be as big a deal as you're making it out to be. It's possible you pulled the git repo while there was a bug, or you didn't install the prerequisites first, which could create issues for you.

If you don't mind me asking, what problems were you having trying to compile fidoconf? And what linux distribution were you trying to compile it on?j

First, and assuming you cloned the git repo, you have to edit huskymak.cfg to your liking (the directories you choose should probably exist as well) and put it in the husky project's root directory. Then, compiled *in this order*, and following each module's instructions (ie: huskylib/INSTALL.md, smapi/INSTALL.md, and fidoconf/INSTALL.md) - which may give you the exact same instructions, but at least you covered your behind in the process: huskylib, smapi, and fidoconf. After that you can compile any modules you want to use (ie: hpt, htick, nltools, etc).

With that said, if fidoconf doesn't compile for you, I can't imagine that any module after that would either, but if you were somehow able to get hpt or htick to compile without a working fidoconf, something is probably very wrong in your case (linked libraries in multiple locations? who knows).

Lastly, I've quickly glossed over and searched some of the .texi files, and can't for the life of me find an "autoAreaCreate" option. The closest thing I could find is "autoAreaCreateSubdirs" which may not even pertain to what you're trying to do. So if there is no documentation on those switches, they may not exist any more, and if you trying to use them cause errors, maybe it's something that should be brought up to a developer as it's possible those switches were once removed but some old code was left in? Or, over the years those switches were forgotten about and broken and it's possible you were the first to notice. *shrug*

I've had the husky software runnig here for years, and have upgraded over the years as well, so if you really want to get this stuff working, I'd be happy to help out where I can if you're still interested. It is usually super easy to compile/install, and if it isn't, something is either wrong with the code (it is still actively updated, so random git pulls could give you a broken package. However, any issues are usually addressed within a reasonable time) or something with your compiler, system, or directory structure.

Regards,
Nick

.... Don't sweat the petty things and don't pet the sweaty things

--- Mystic BBS v1.12 A47 2021/07/06 (Linux/64)
 * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

.