Subj : Talisman - alpine?
To   : apam
From : deon
Date : Thu Apr 18 2024 09:06 am

  Re: Talisman - alpine?
  By: apam to deon on Mon Apr 15 2024 07:18 am

Howdy,

 >  de> Is it fixable? (it doesntlike the (const char**)
 >
 > Yeah, that's the iconv thing i mentioned, i've got two versions in the
 > source, you'll want to add a whatever the MUSL define is to the list on the
 > ones above the const char ** things.
 >
 > With the amount of systems that don't like the const char ** i'm thinking i
 > should have made the other way default :)

So it compiles and seems to be working OK. I'm building a docker container of talisman, so if anybody wants to use it let me know and I'll make it available.

I did hit a few hurdles with the configuration, but that might have been my inexperience with talisman and/or finger trouble, which I'll test out and let you know if I hit the same problem. (I'm using full paths, but it seemed to ignore them?)

Do you want a patch for alpine? Its pretty easy, basically you need a
#include <ctime> for the files where you are using time_t, and to get past that iconv const issue, was to define __GLIBC__ in Talisman/Config.cpp.

It probably would make sense to have all that wrapped around ifdefs and maybe a define for alpine - and for it to be automatically detected, but that is beyond my knowledge. ;)


....лоеп
--- SBBSecho 3.20-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

.