warning: passing argument 2 of ‘mosquitto_message_callback_set’ from incompatible pointer type

Interestingly, not required for successful MSVC build. <shurg>

I suspecte the circular dependency and include-guards around mqtt.h
and startup.h were going to be a problem.

Now support subscriptions (e.g. recycle topics, node input topics) in SBBSCTRL.
This required a lot of search/replace and fun with circular struct pointers.

Doing this via manual edits to this bpr file don't seem to work.

Fix issue #470 reported via IRC: timed event "mdays" values were read and written as 16-bit values, meaning any setting for days > 15 would do weird things.

The only difference in the data/scheme is that the "error" topic (error log) is now under each server rather than each host. I don't *think* there are any other changes from the MQTT consumer side.

Still not done: subscribing (e.g. support for recycle or node-spy-input via MQTT) and NT services support.

This change also includes a cool feature that will prompt the sysop if there's a timeout (30 seconds) while waiting for servers to shutdown gracefully and giving the sysop the option to abort (Cancel) the wait (and shutdown ungracefully) or continue the wait (OK).

And export a simple ver() function to be used in MainFormUnit.cpp (for mqtt stuff)

e.g. sbbs.dll

Turned of "Use dynamic RTL" and "Build with runtime packages" under
Project options.

This should resolve the UserEdit.exe runtime issue reported by Diamond Dave
via DOVE-Net.

Bug introduced in the systemd integration (commit 7e320d92)
and reported by Dan_C via #synchronet at irc.synchro.net

(last user record wouldn't have been updated)

These are rather old update steps (e.g. v3.18), so don't fret it.

This reverts commit 2975dc62.

This reverts commit 0280050f.

This reverts commit 0ee77637.

This seems to stop the CI build and I haven't found any other solution.
So just copy/paste the contents of makelibs.bat into this batch file. <sigh>

when run from Gitlab-Runner (CI) using shell="cmd"

Apparently when the Gitlab Runner is using "cmd", you must do this or only
the first invoked bat file is executed. This explains why sbbsctrl.exe
(and other) files have been missing from the CI-generated artifact archives.
Back when I was using "powershell" to invoke the CI build for sbbs-windows
(my Gitlab-runner/config.toml file had shell = "powershell"), this wasn't an
issue, but this configuration stopped working on Vert at some point
(https://forum.gitlab.com/t/windows-10-gitlab-runner-fails-with-error-no-process-is-on-the-other-end-of-the-pipe/66691)
so I switched to "cmd", even though it's deprecated.

Remove the dependencies: [] line since that wasn't a solution to anything.

I think this addresses issue #403, at least in part.

CID 433272

DDMsgReader: For Synchronet >= 3.20, read external editor quote wrap setting from xtrn.ini (rather than xtrn.cnf)

See merge request !236

Eric Oulashin authored 2 years ago and Rob Swindell committed 2 years ago

DDMsgReader: For Synchronet >= 3.20, read external editor quote wrap setting from xtrn.ini (rather than xtrn.cnf)

Some trailing whitespace clean-up too.

Previously, many servers and services didn't support login by real name
(e.g. issue #469) even if the sysop had that option enabled in SCFG.

Move login control settings from node.ini to system (main.ini -> login)

The 3 node toggle options:
- Allow Login by User Number
- Allow Login by Real Name
- Always Prompt for Password

... have been now moved from SCFG->Nodes->Node x->Toggle Options to
SCFG-System->Toggle Options.

If you upgraded to v3.20a before now, you'll want to double-check these
settings to make sure they're how you want them set. New upgraders that run
upgrade_to_v320.js (e.g. via 'jsexec update') will get these settings migrated
automatically.

Added some error detection/logging to upgrade_to_v320.js when failing to open
.cnf files.

Constified some more user/login related function args and return types.

Oversight probably during the new filebase overhaul in v3.19. Reported by Nelgin.

No immediate use, but I thought I had one. I didn't. Still, will probably need these one day.

As apparently these happen a lot when a client disconnects right
away after connecting.

Need to start the MQTT init/thread-start stuff after daemonizing.

Thanks to Nelgin for letting me know this was recently broken.