1. 15 Sep, 2020 1 commit
    • Rob Swindell's avatar
      Switch from static C runtime library to runtime DLL · 05c45f17
      Rob Swindell authored
      This fixes the stat() issue on Windows XP/2K3 by allowing sbbs to benefit
      from the run-time library updates that Microsoft releases periodically
      (like https://www.microsoft.com/en-us/download/details.aspx?id=53840).
      
      For more info on the stat() issue which caused all kinds of sbbs errors
      (e.g. creating directories initially, but a lot more):
      https://stackoverflow.com/questions/32452777/visual-c-2015-express-stat-not-working-on-windows-xp
      
      Since we are using cryptlib which requires the MSVC runtime DLL anyway
      (it is the default build behavior of MSVC), we weren't really gaining
      anything from statically linking the CRTL (LIBCMT.LIB). And for some reason,
      an up-to-date MSVC2019 still has (links-in) a LIBCMT.LIB file that includes
      this stat bug. All the online help resources I found just to seem to suggest
      updating the CRTL DLLs (on the target system), with no mention of any fixes
      available for the static CRTLs on the build system. But with the no gain
      from static linking anyway, I figured it was time to switch to DLL CRTLs.
      
      The debug builds are still statically linking the CRTL for no particular
      reason.
      05c45f17
  2. 24 Aug, 2019 1 commit
    • rswindell's avatar
      New static link library, load_cfg, which contains load_cfg.c and it's immediate · 4383ed20
      rswindell authored
      dependencies (scfglib*.c, scfglib*.c, etc.) for the single-threaded SBBS
      that need to load the configuration (*.cnf) files from ctrl.
      Rather than updating 8 projects every time the load_cfg.c dependencies change
      and rebuilding 8 times, just use a lib.
      Also fixed-up some linker warnings about EDITANDCONTINUE, blah, blah, blah.
      4383ed20
  3. 18 Jul, 2019 1 commit
  4. 29 Jun, 2019 1 commit
  5. 22 Aug, 2015 1 commit
  6. 28 Mar, 2014 1 commit
    • rswindell's avatar
      Change the target to Windows XP-IA32: resolves the "not a valid Win32 · 40f5417e
      rswindell authored
      application" error message (when run on XP) and reportedly will allow target
      executables to run on non-SEE (pre-Pentium III) CPUs. Seriously, anyone really
      running Windows XP on a Pentium II today? I guess it's possible <shrug> and we
      really get little benefit from SSE in Synchronet.
      
      I couldn't get Windows 2000 running in Hyper-V, so I guess Windows 2000 is
      now officially unsupported by Synchronet (and long unsupported by Microsoft).
      
      Thanks to Android8675 for the bug report and Rushfan for the solution tip.
      40f5417e
  7. 13 Mar, 2014 1 commit
  8. 21 Oct, 2011 1 commit
  9. 09 Oct, 2011 1 commit