GitLab

<Dan_C> DigitalMan: minor install issue noted today - during a fresh (Linux) install on a test box, the build failed because it was unable to execute the "sudo setcap ..." command.  This was on Slackware 15.0, where the setcap executable is located in /sbin , and that directory is not in the $PATH of a normal user, or even when a normal user uses the 'sudo' command.

We only support platforms where slash is a legal path separator.

This won't impact Synchronet as it has a separate signal handling
thread, but we still need to behave properly for processes that
don't.  I'm also saying that ENOMEM does not indicate a disconnection,
though it may be better to pretend it was disconnected...

This reduces the number of unnecessary recompiles of ver.cpp -> ver.o.

To be sure these buggers are always created for every build that includes the
'all' target. Perhaps these should be creatd in build or an output dir and
maybe for all projects (not just sbbs3) - but will ponder tomorrow.

Allows reporting of branch/commit that was used to build the code.

If for some reason building without 'git', you'll need these 2 files to
already exist somehow - still need to work that out (e.g. for daily
built-source archives).

Need to update the Windows build to generate these files now.

This requires anything that includes sbbs.h to have cryptlib and
mozjs already built/isntalled... to track this, I've added the new
extdeps.mk file.

This is pretty terrible though... not sure how important that
dependency really is.

This is because it includes js_version.h if JAVASCRIPT is defined,
and JAVASCRIPT is defined for everything using CFLAGS.

It may be worth re-working the JAVASCRIPT define, but that's a bunch
of extra work.

This is the first (and easiest) step in getting parallel builds
working.

the sbbs3/gtk* outputs too.

and a gtkutils build target to build them all (e.g. "make gtkutils")
to make life easier for Nelgin

the generated 'sbbs' executable to enable low-port-binding capability.
e.g. run 'make RELEASE=1 setcap symlinks' to make a release (non-debug)
build, set the bind-capability on sbbs, and create symlinks from your
exec directory to the build output (*.exe.release) directory.

sub-projects: scfg, uedit, and umonitor

makes (scfg, uedit, umonitor).

Windows

recursive make of scfg, uedit, and umonitor.

the default/all target.
So a single "make" command in src/sbbs3 should build these nested targets
as well.
Caveat: "make clean" does not clean these sub-make targets.

Created 'install' and 'symlinks' targets to ease the copying (install) or creating of symlinks after build, requires SBBSEXEC env var

directory.  This is the beginnings of the ability to write a door in JS for
all BBSes, not just Synchronet (door kit pending).

This requires moving js_CreateCommonObjects() into main.cpp, which requires
constifying the name parameter to js_CreateClientObject() due to C++ being
more paranoid about using a string literal as a char * parameter
(warning fix).

bored.)

Used by Smeg@