Debian CDBS to DH

.gitignore

@@ -17,6 +17,7 @@
 # Windows Compiled files
 *.exe
 *.pdb
+*.ilk
 
 # Compiled Python
 *.pyc
@@ -31,6 +32,8 @@ config.log
 package.txt
 lib
 include
+build_info.cpp
+/dist.txt
 
 # Backup files
 *~
@@ -39,3 +42,15 @@ include
 .ninja_deps
 .ninja_log
 build.ninja
+
+# VS Code files
+.vscode
+*.code-workspace
+
+# Patches, regects, origs
+*.patch
+*.rej
+*.orig
+
+# Env files
+/scons-env-options.py

.travis.yml

@@ -0,0 +1,35 @@
+sudo: false
+dist: bionic
+language: cpp
+compiler:
+  - gcc
+python:
+  - "3.8"
+
+cache: ccache
+
+addons:
+  apt:
+    update: true
+    packages:
+      - scons
+      - build-essential
+      - libssl-dev
+      - binutils-dev
+      - libiberty-dev
+      - libmariadb-dev-compat
+      - libleveldb-dev
+      - libsnappy-dev
+      - git
+
+jobs:
+  include:
+    - stage: Build
+      script:
+        - scons
+    - stage: Test
+      script:
+        - scons
+        - cd tests
+        - scons
+        - ./testHarness

CODE_TAG

@@ -1,7 +1,7 @@
           This file is part of the C! library.  A.K.A the cbang library.
 
-              Copyright (c) 2003-2019, Cauldron Development LLC
-                 Copyright (c) 2003-2017, Stanford University
+               Copyright (c) 2021-2024, Cauldron Development  Oy
+               Copyright (c) 2003-2021, Cauldron Development LLC
                              All rights reserved.
 
         The C! library is free software: you can redistribute it and/or

README.md

@@ -2,19 +2,21 @@ C! (a.k.a. C-Bang)
 ==================
 
 The C! or cbang library is a collection of C++ utility libraries
-developed over the course of +15 years and several major C++
+developed over the course of +20 years and several major C++
 application development projects.  It should compile and run on
-Windows, Linux and OSX using a modern C++ compiler.
+Windows, Linux and macOS using a modern C++ compiler such as GNU C++,
+clang or MSVC.
 
 Many of the facilities of C! are geared towards cross-platform
 application development and providing basic services that most
 applications need such as a configuration system, run-time build
-information, logging facilities, threads, smart pointers, simple
-embedded scripting, etc.
+information, configuration and logging facilities, and smart pointers.
 
 C!'s philosophy is to create clean, simple, readable, modular and
-reusable code.  C! also encourages exception based error handling, and
-light use of C++ templates and C preprocesor macros.
+reusable code.  C! also encourages exception based error handling,
+light use of C++ templates and C preprocesor macros.  Event driven
+asynchronoius programing is prefered but threading is also fully
+supported.
 
 C! "leans" on the venerable boost library but also reimplements
 several boost APIs which are considered by the author to be too
@@ -25,76 +27,81 @@ be any sort of grand unifying system for C++ application development.
 However, I hope you find many parts of the library useful in your C++
 development projects.
 
-For licensing information please see the files LICENSE and COPYING.
-
+For licensing information please see ``LICENSE`` file.
 
 # Features
+
   - Smart pointers, both thread safe and non, with downcasting capability.
-  - Threading, mutexes, conditions & thread local storage
-  - Soft exit & signal handling
   - Extensively configurable logging facilities.
-  - Exception class with stack trace capability including line and file info.
+  - Stack trace capability with function, file and line. (macOS and Linux only)
   - Exception throwing and catching convenience macros.
-  - HTTP and HTTPS client and server.
+  - Command line parsing and configuration file configuation system.
+  - HTTP, HTTPS and Websocket client and server.
+  - Automatic ACMEv2 TLS certification aquisition.
+  - OAuth2 logins.
+  - Event driven programming via C++ wrapper for libevent.
+  - Asynchronous IP address / hostname resolution, parsing and manipulation.
+  - IPv6 support.
   - Socket client and server with asynchronous capability.
-  - XMacro based enum implementation.
-  - PyON Python Object Notation language for serializing and deserializing data.
-  - Simple scripting language for configuration and text based command server.
+  - Threading, mutexes, conditions & thread local storage
+  - Soft exit & signal handling
+  - GPU detection with OpenCL and CUDA support detection.
+  - CPU type and feature detection for x86, amd64 and aarch64.
+  - PCI bus enumeration.
+  - Embedded Javascript (ECMA) support.
+  - Dynamic library and symbol loading.
+  - Subprocess handling.
+  - Powermanagment and system idle detection.
+  - XMacro based enumerations with automatic string parsing and printing.
   - Software build information system.
-  - A system for compiling in a directory tree of resources.
+  - Compile in resource trees from directory of files on disk.
   - Network packet automatic byte order and string packing functionality.
-  - Temporary directories, directory traversal & file operations
-  - C++ style number, to and from, string conversions.
-  - iostream utilities.
-  - Application configuration system.
-  - XML facilities.
+  - Temporary directories, directory traversal & file operations.
+  - File locking.
+  - C++ style number conversions to/from string.
+  - std::iostream and compression utilities.
+  - JSON, YAML and XML facilities.
   - TAR file read and write.
   - Time and timing functions.
   - OpenSSL C++ interface.
-  - IP address / hostname resolution, parsing and manipulation.
   - URL parsing.
   - Geometric primitives.
-  - C++ wrapper for libevent.
-  - Async MariaDB interface using libevent.
+  - Async MariaDB/MySQL client interface.
   - Human readable size & time formatting.
   - Many other utility classes.
   - Completely contained in it's own C++ namespace.
   - Consistent and clean code formating <= 80 column width.
-
+  - Platform independent API.
 
 # Prerequisites
-## General
+## Required
   - A modern C++ compiler: GNU C++, Intel C++, MSVS
-  - SCons      http://scons.org/
-  - openssl    http://www.openssl.org/ (optional)
-  - ChakraCore https://github.com/Microsoft/ChakraCore/ (optional)
-  - V8         https://developers.google.com/v8/ (optional)
-  - mariadb    https://mariadb.org/ (optional)
+  - SCons http://scons.org/
 
-## Debug mode only
+## Optional
+The following add optional features to C!.
 
-  - libbfd    ftp://ftp.gnu.org/old-gnu/Manuals/bfd-2.9.1/html_mono/bfd.html
-  - libiberty https://gcc.gnu.org/onlinedocs/libiberty/
+  - openssl    http://www.openssl.org/
+  - V8         https://developers.google.com/v8/
+  - mariadb    https://mariadb.org/
+  - LevelDB    https://github.com/google/leveldb
+  - Snappy     http://google.github.io/snappy/
 
-## Windows only
-  - Winsock
+## Debug mode
+Debug mode is enabled by compiling with ``debug=``.
 
-## OS-X only
-  - IOKit
-  - CoreFoundation
+Compiling with ``libbfd`` will enhance stack track output on Linux systems.
+Install ``binutils-dev`` to get ``libbfd`` on Debian.
 
-## POSIX/Linux only
-  - pthreads
-  - libbfd (For debug mode only)
+## Debian/Ubuntu install
+On most Debian based systems the prerequisites can be installed with the
+following command line:
 
-On Debian based systems the prerequisites can be installed with the following
-command line:
+    sudo apt-get install -y scons build-essential libssl-dev binutils-dev \
+      libiberty-dev libmariadb-dev-compat libleveldb-dev libsnappy-dev git \
+      libzstd-dev
 
-    sudo apt-get install scons build-essential libssl-dev binutils-dev \
-      libiberty-dev libmariadbclient-dev git
-
-Unfortunately, at this time, there is no ChakraCore package for Debian.  See
-the build instructions below.
+The necessary library packages can very by Linux distribution type and version.
 
 # Build
 
@@ -112,7 +119,7 @@ command line to scons or place in a configuration file named
   - strict               - Enable strict checking
   - distcc               - Enable distcc distributed compile system
   - ccache               - Enable ccache caching compile system
-  - backtrace_debugger   - Enable the printing backtraces
+  - backtrace_debugger   - Enable the printing of stack traces
 
 These options are enabled by setting them to 1.  For example:
 
@@ -126,76 +133,6 @@ strict checking.
 
 # Testing the Build
 
-You can testing C! by going to the *tests* directory in the root of the
-cbang source tree, building the test programs and running the test harness:
-
-    cd tests
-    scons
-    ./testHarness
-
-# Troubleshooting
-
-This section describes some common problems and their solutions.
-
-## OpenSSL Library Less than v1.0.0
-
-If you get an error about the openssl library version being too old then you
-either need to upgrade your package or build openssl from source like this:
-
-    wget http://www.openssl.org/source/openssl-1.0.1f.tar.gz
-    tar xzvf openssl-1.0.1f.tar.gz
-    cd openssl-1.0.1f
-    ./config
-    make
-    export OPENSSL_HOME=$PWD
-
-Then try building C!.
-
-## ChakraCore
-
-You can either download a prebuilt ChakraCore or build it yourself.  Currently
-we require a fork of ChakraCore which includes some fixes.
-
-### Windows Binaries
-
-You can find windows binaries of ChakraCore here:
-https://github.com/CauldronDevelopmentLLC/ChakraCore/releases/tag/v2.0.0.1
-
-### Building ChakraCore
-
-ChakraCore is the Javascript engine used by the Microsoft Edge browser.  It
-is fast and Open-Source.  Unfortunately there currently aren't any readily
-available Debian packages for ChakraCore so you will have to build it from
-source.
-
-First make sure you have the prerequisites:
-
-    sudo apt-get install -y cmake clang libunwind-dev libicu-dev
-
-You need at least cmake 3.2 and clang 3.8.  If your system doesn't have these
-then you need to build them from source.
-
-
-First download the source code:
-
-    git clone --depth=1 https://github.com/CauldronDevelopmentLLC/ChakraCore.git
-
-Then build it:
-
-    cd ChakraCore
-    ./build.sh --static -j 8
-
-Next collect the various libraries it produces in to one:
-
-    mkdir tmp
-    cd tmp
-    for i in $(find ../Build* -name \*.a); do
-      ar x $i
-    done
-    ar rcs ../libChakraCore.a *.o
-    cd ..
-    rm -rf tmp
-
-Now setup the environment so that the C! build system can find ChakraCore:
+You can testing C! by running the test suite:
 
-    export CHAKRA_CORE_HOME=$PWD
+    scons test