Is smapi-2.5-current basically the same thing as smapi-2.4-rc5, just changed to be a part of the huskyproject? Or were there significant changes made to the sources between the two?
Is smapi-2.5-current basically the same thing as smapi-2.4-rc5, just
changed to be a part of the huskyproject? Or were there significant
changes made to the sources between the two?
There was no tag for smapi-2.4-rc5 in the current git repository. I've
set a new tag 'smapi-2_4-RC5' for 9355cf5 commit made on 2006-02-09. Multiple bugs were fixed since then.
The next one would be, is there a way to get the latest
smapi-2.5-current to not require most of the rest of the husky project
to be built at the same time? Is there an older makefile still
included that would only compile smapi instead of using
the new 'build.sh' method?
Current SMAPI version from HUSKY has dependency on Huskylib. You can use any build system, makefiles, cmake, you name it, but SMAPI lib requires some functionality from Huskylib.
You are probably looking for something old like this https://github.com/pgul/smapi. Even this ancient 2.5 version includes a small portion of huskylib inside but very limited, just a compiler definition compiler.h header and locking.{h,c} file for portable file locking primitives.
Please don't be confused with the original Squish MSGAPI0 library, copyright 1991 by Scott J. Dudley. The HUSKY SMAPI library branched
from the original Squish MSGAPI0, added OPUS/MSG format and reused
jamlib as well to provide a message API abstraction for manipulating all three message databases with the a single API.
For the record, I'm working on Smapinntpd a bit. It requires smapi
which, in turn, will require huskylib. I installed it fairly easy with some tinkering, because I have all of the husky project already
installed and in use on my system, but for someone downloading the
program and trying to install it without the husky project already installed will be confusing. I'm trying to figure out the easiest way
to do so, so I can either write up more current installation
instructions, or somehow provide these with the package so one can
just install everything in one shot.
Is smapi-2.5-current basically the same thing as smapi-2.4-rc5,
just changed to be a part of the huskyproject? Or were there
significant changes made to the sources between the two?
There was no tag for smapi-2.4-rc5 in the current git repository.
I've set a new tag 'smapi-2_4-RC5' for 9355cf5 commit made on
2006-02-09. Multiple bugs were fixed since then.
Ok, that answered that question. The next one would be, is there a way
to get the latest smapi-2.5-current to not require most of the rest of
the husky project to be built at the same time?
Is there an older makefile still included that would only compile
smapi instead of using the new 'build.sh' method?
And if there was a separate way outside of 'build.sh', if I remember right, the order was huskybse, huskylib, then smapi.. and I don't
remember if huskybse actually compiled anything, so I assume smapi
only requires huskylib to be compiled?
Smapi depends on huskylib only. If you do not want this dependency, the code from huskylib used by smapi should be inserted back into smapi. I made it when I ported smapi-2.5 to RNtrack. So, if you need smapi for
your pet project, you may take it from there. I do not support RNtrack anymore and I gave away its git repository to Max Vasilyev.
https://github.com/vasilyevmax/rntrack
Sysop: | Saxainden |
---|---|
Location: | Littleton, CO |
Users: | 30 |
Nodes: | 10 (0 / 10) |
Uptime: | 04:24:05 |
Calls: | 350 |
Messages: | 36,657 |