compiletools 5.3.3__tar.gz → 6.0.2__tar.gz

{compiletools-5.3.3 → compiletools-6.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: compiletools
-Version: 5.3.3
+Version: 6.0.2
 Summary: Tools to make compiling C/C++ projects easy
 Keywords: c++,make,development
 Author: DrGeoff
@@ -25,7 +25,7 @@ Requires-Dist: stringzilla>=3.0.0
 Requires-Dist: bump-my-version>=0.26.0 ; extra == 'dev'
 Requires-Dist: twine>=5.0.0 ; extra == 'dev'
 Requires-Dist: pytest>=7.0.0 ; extra == 'dev'
-Requires-Dist: pytest-xdist>=3.0.0 ; extra == 'dev'
+Requires-Dist: pytest-xdist>=3.5 ; extra == 'dev'
 Requires-Dist: ruff>=0.12.9 ; extra == 'dev'
 Requires-Python: >=3.9
 Project-URL: Download, https://github.com/DrGeoff/compiletools/archive/v{version}.tar.gz
@@ -47,7 +47,7 @@ C/C++ build tools that requires almost no configuration.
 :Author: drgeoffathome@gmail.com
 :Date:   2016-08-09
 :Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
-:Version: 5.3.3
+:Version: 6.0.2
 :Manual section: 1
 :Manual group: developers
 
@@ -57,20 +57,23 @@ SYNOPSIS
 
 DESCRIPTION
 ===========
-The various ct-* tools exist to build C/C++ executables with almost no 
+The various ct-* tools exist to build C/C++ executables with almost no
 configuration. For example, to build a C or C++ program, type
 
 .. code-block:: bash
 
-    ct-cake --auto
+    ct-cake
 
-which will try to determine the correct source files to generate executables
-from and also determine the tests to build and run.
+which will automatically determine the correct source files to generate executables
+from and also determine the tests to build and run. (The ``--auto`` flag is the
+default; use ``--no-auto`` to disable automatic target detection.)
 
 A variant is a configuration file that specifies various configurable settings
 like the compiler and compiler flags. Common variants are "debug" and "release".
 
-Options are parsed using python-configargparse.  This means they can be passed
+CONFIGURATION
+=============
+Options are parsed using the python package ConfigArgParse.  This means they can be passed
 in on the command line, as environment variables or in config files.
 Command-line values override environment variables which override config file 
 values which override defaults. Note that the environment variables are 
@@ -101,12 +104,53 @@ For example,
     or 
     --append-CXXFLAGS='"-march=skylake"'
 
-Other notable tools are
+SHARED OBJECT CACHE
+===================
+compiletools supports a shared object file cache for multi-user/multi-host
+environments. When enabled via ``shared-objects = true`` in ct.conf 
+(or via the command line or environment variable), the Makefile
+generation includes proper locking mechanisms to safely share object files across
+concurrent builds by multiple users and hosts. 
 
-.. code-block:: text
+Setting in ct.conf is the recommended way to enable this feature for teams so that 
+all users gain the locking without needing to set their own environment variables. 
 
-    * ct-headertree: provides information about structure of the include files
-    * ct-filelist:   provides the list of files needed to be included in a tarball (e.g. for packaging)
+This feature can also be used by a single developer on a single machine to compile 
+different directories in parallel, sharing the same object file cache for objects 
+that are in common.
+
+Key features:
+
+* **Content-addressable storage**: Object files named by source + flags hash
+* **Filesystem-aware locking**: Uses flock on local filesystems, atomic mkdir on network filesystems (NFS, GPFS, Lustre)
+* **Multi-user safe**: Group-writable cache with proper file permissions
+* **Cross-host compatible**: Automatic filesystem detection and appropriate locking strategy
+* **Stale lock detection**: Automatic cleanup of locks from crashed builds
+* **Minimal configuration**: Just set ``shared-objects = true`` in config
+
+Example setup for shared cache:
+
+.. code-block:: bash
+
+    # In ct.conf or variant config
+    shared-objects = true
+    objdir = /shared/nfs/build/cache
+
+    # Ensure cache directory is group-writable with SGID
+    mkdir -p /shared/nfs/build/cache
+    chmod 2775 /shared/nfs/build/cache
+
+Configuration options in ct.conf:
+
+* ``max_file_read_size = 0`` - Bytes to read from files (0 = entire file)
+* ``shared-objects = true`` - Enable shared object cache
+
+OTHER TOOLS
+===========
+Other notable tools are:
+
+* ct-headertree: provides information about structure of the include files
+* ct-filelist: provides the list of files needed to be included in a tarball (e.g. for packaging)
 
 SEE ALSO
 ========
@@ -117,13 +161,14 @@ SEE ALSO
 * ct-cache-clean
 * ct-cake
 * ct-cmakelists
-* ct-commandline
+* ct-compilation-database
 * ct-config
 * ct-cppdeps
 * ct-create-cmakelists
 * ct-create-makefile
 * ct-filelist
 * ct-findtargets
+* ct-git-sha-report
 * ct-gitroot
 * ct-headertree
 * ct-jobs

{compiletools-5.3.3 → compiletools-6.0.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "compiletools"
-version = "5.3.3"
+version = "6.0.2"
 description = "Tools to make compiling C/C++ projects easy"
 readme = "src/compiletools/README.ct-doc.rst"
 requires-python = ">=3.9"
@@ -35,7 +35,7 @@ dev = [
     "bump-my-version>=0.26.0",
     "twine>=5.0.0",
     "pytest>=7.0.0",
-    "pytest-xdist>=3.0.0",
+    "pytest-xdist>=3.5",
     "ruff>=0.12.9",
 ]
 
@@ -83,7 +83,7 @@ include = [
 ]
 
 [tool.bumpversion]
-current_version = "5.3.3"
+current_version = "6.0.2"
 parse = "(?P<major>\\d+)\\.(?P<minor>\\d+)\\.(?P<patch>\\d+)"
 serialize = ["{major}.{minor}.{patch}"]
 search = "{current_version}"
@@ -113,9 +113,15 @@ filename = "src/compiletools/README.ct-cake.rst"
 [[tool.bumpversion.files]]
 filename = "src/compiletools/README.ct-commandline.rst"
 
+[[tool.bumpversion.files]]
+filename = "src/compiletools/README.ct-compilation-database.rst"
+
 [[tool.bumpversion.files]]
 filename = "src/compiletools/README.ct-config.rst"
 
+[[tool.bumpversion.files]]
+filename = "src/compiletools/README.ct-cppdeps.rst"
+
 [[tool.bumpversion.files]]
 filename = "src/compiletools/README.ct-findtargets.rst"
 

{compiletools-5.3.3 → compiletools-6.0.2}/src/compiletools/README.ct-cache-clean.rst

@@ -9,7 +9,7 @@ Remove the current dependency cache
 :Author: drgeoffathome@gmail.com
 :Date:   2018-02-23
 :Copyright: Copyright (C) 2011-2018 Zomojo Pty Ltd
-:Version: 5.3.3
+:Version: 6.0.2
 :Manual section: 1
 :Manual group: developers
 

{compiletools-5.3.3 → compiletools-6.0.2}/src/compiletools/README.ct-cache.rst

@@ -9,7 +9,7 @@ Where is the dependency information used by the ct-* applications stored
 :Author: drgeoffathome@gmail.com
 :Date:   2018-02-21
 :Copyright: Copyright (C) 2011-2018 Zomojo Pty Ltd
-:Version: 5.3.3
+:Version: 6.0.2
 :Manual section: 1
 :Manual group: developers
 

{compiletools-5.3.3 → compiletools-6.0.2}/src/compiletools/README.ct-cake.rst

@@ -9,7 +9,7 @@ Swiss army knife for building a C/C++ project
 :Author: drgeoffathome@gmail.com
 :Date:   2018-02-06
 :Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
-:Version: 5.3.3
+:Version: 6.0.2
 :Manual section: 1
 :Manual group: developers
 
@@ -23,18 +23,19 @@ ct-cake is the Swiss army knife of build tools that combines many of the
 compiletools into one uber-tool. For many C/C++ projects you can compile
 simply using
 
-    ``ct-cake --auto``
+    ``ct-cake``
 
-ct-cake will try to determine the correct source files to generate executables
+ct-cake will automatically determine the correct source files to generate executables
 from and also determine the tests to build and run. It works by spidering over
-the source code to determine what implementation files to build, what libraries 
+the source code to determine what implementation files to build, what libraries
 to link against and what compiler flags to set. Only build what you
 need, and throw out your Makefiles.
 
-The --auto flag tells ct-cake to search for files that will be the "main" file.  
+By default (``--auto``), ct-cake searches for files that will be the "main" file.
 From that set of files, ct-cake then uses the header includes to
-determine what implementation (cpp) files are also required to be built and 
-linked into the final executable/s.
+determine what implementation (cpp) files are also required to be built and
+linked into the final executable/s. Use ``--no-auto`` to disable automatic
+target detection and specify files explicitly.
 
 Cake works off the same principles as Ruby on Rails. It will make your life
 easy if you don't arbitrarily name things. The main rules are:
@@ -75,10 +76,9 @@ testing, but it's not essential.
 
 The basic workflow is to simply type:
 
-    ``ct-cake --auto``
+    ``ct-cake``
 
-If there are multiple executables that --auto finds and you only want to build 
-one specific one:
+If there are multiple executables found and you only want to build one specific one:
 
     ``ct-cake path/to/src/app.cpp``
 
@@ -94,15 +94,15 @@ How it Works
 ============
 
 ct-cake generates the header dependencies for the "main.cpp"
-file you specify at the command line by either examining the "#include" lines in 
-the source code (or by executing "gcc -MM -MF" if you use the --preprocess flag).  
+file you specify at the command line by either examining the "#include" lines in
+the source code (or by executing "gcc -MM -MF" if you use the --preprocess flag).
 For each header file found in the source file, it looks for
-an underlying implementation (c,cpp,cc,cxx,etc) file with the same name, and 
-adds that implementation file to the build.  ct-cake also reads the first 8KB
-of each file for special comments
+an underlying implementation (c,cpp,cc,cxx,etc) file with the same name, and
+adds that implementation file to the build.  ct-cake also reads the entire file
+(configurable via --max-file-read-size) for special comments
 that indicate needed link and compile flags.  Then it recurses through the
 dependencies of the cpp file, and uses this spidering to generate complete
-dependency information for the application. A Makefile is generated and finally 
+dependency information for the application. A Makefile is generated and finally
 it calls make.
 
 Magic Comments / Magic Flags
@@ -132,19 +132,34 @@ Performance
 
 Because ct-cake internally generates a makefile to build the C++ file, cake is
 about as fast as a handrolled Makefile that uses the same lazily generated
-dependencies. One particular example project took 0.04 seconds to build if 
+dependencies. One particular example project took 0.04 seconds to build if
 nothing is out of date, versus 2 seconds for, say, Boost.Build.
 
 ct-cake also eliminates the redundant generation of static archive files that
 a more hierarchical build process would generate as intermediaries, saving
 the cost of running 'ar'.
 
-Note that ct-cake doesn't build all cpp files that you have checked out, only 
+Note that ct-cake doesn't build all cpp files that you have checked out, only
 those
 strictly needed to build your particular binary, so you only pay for what
 you use. This difference alone should see a large improvement on most
 projects, especially for incremental rebuilds.
 
+Shared Object Cache
+-------------------
+
+ct-cake supports a shared object file cache that enables multiple users and build
+hosts to share compiled object files. This significantly speeds up builds in
+multi-developer and CI/CD environments by reusing object files across builds.
+
+Enable by setting ``shared-objects = true`` in your configuration file. This adds
+filesystem-aware locking to ensure safe concurrent access (flock on local filesystems,
+atomic mkdir on network filesystems). The cache uses content-addressable storage
+(files named by hash of source + compiler flags) and includes automatic stale lock
+detection for crashed builds.
+
+See the main compiletools README for setup details.
+
 Selective build and test
 ========================
 
@@ -154,7 +169,7 @@ limiting building and testing in a Continuous Integration pipeline to only
 source that has changed from master.
 
 ``changed_source=git diff --name-only master | sed "s,^,$(git rev-parse --show-toplevel)/,"
-ct-cake --auto --build-only-changed \"$changed_source\"``
+ct-cake --build-only-changed \"$changed_source\"``
 
 Configuration
 =============
@@ -275,7 +290,7 @@ the build.sh, before cake runs.
     #!/bin/sh
     set -e
     python fancypythoncodegenerator.py
-    ct-cake --auto "$@"
+    ct-cake "$@"
 
 
 The special *"$@"* marker is the recommended way

{compiletools-5.3.3 → compiletools-6.0.2}/src/compiletools/README.ct-commandline.rst

@@ -9,7 +9,7 @@ This document describes the command line arguments that are common across ct-* p
 :Author: drgeoffathome@gmail.com
 :Date:   2017-07-06
 :Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
-:Version: 5.3.3
+:Version: 6.0.2
 :Manual section: 1
 :Manual group: developers
 

compiletools-6.0.2/src/compiletools/README.ct-compilation-database.rst

@@ -0,0 +1,127 @@
+=========================
+ct-compilation-database
+=========================
+
+--------------------------------------------------------------------------------
+Generate compile_commands.json for clang tooling and IDE integration
+--------------------------------------------------------------------------------
+
+:Author: drgeoffathome@gmail.com
+:Date:   2025-10-08
+:Copyright: Copyright (C) 2011-2025 Zomojo Pty Ltd
+:Version: 6.0.2
+:Manual section: 1
+:Manual group: developers
+
+SYNOPSIS
+========
+ct-compilation-database [-h] [-c CONFIG_FILE] [--variant VARIANT] [-v] [-q]
+                        [--version] [--compilation-database-output OUTPUT]
+                        [--relative-paths]
+                        [filename ...]
+
+DESCRIPTION
+===========
+ct-compilation-database generates a compilation database (compile_commands.json)
+for C/C++ projects. This JSON file contains the exact compiler commands used to
+build each source file, enabling integration with modern development tools.
+
+The compilation database format is used by:
+
+* **Language servers**: clangd, ccls for IDE features (autocomplete, go-to-definition)
+* **Static analyzers**: clang-tidy, clang-format, cppcheck
+* **Code indexers**: rtags, ycmd
+* **Refactoring tools**: clang-rename, clang-include-fixer
+
+ct-compilation-database is automatically invoked by ct-cake when building projects.
+You can also run it standalone to regenerate the compilation database without
+rebuilding.
+
+The tool uses the same dependency analysis as ct-cake to ensure the compilation
+database reflects the actual build configuration, including:
+
+* Automatic detection of source files
+* Magic flags from source comments
+* Variant-specific compiler settings
+* Include paths and preprocessor definitions
+
+OUTPUT FORMAT
+=============
+The generated compile_commands.json follows the JSON Compilation Database
+specification. Each entry contains:
+
+.. code-block:: json
+
+    {
+      "directory": "/path/to/project",
+      "command": "g++ -std=c++11 -Wall -c main.cpp",
+      "file": "main.cpp"
+    }
+
+OPTIONS
+=======
+--compilation-database-output OUTPUT
+    Output filename for compilation database.
+    Default: <gitroot>/compile_commands.json
+
+--relative-paths
+    Use relative paths instead of absolute paths in the database.
+    Useful for portable compilation databases.
+
+EXAMPLES
+========
+
+Generate compilation database for current project::
+
+    ct-compilation-database
+
+Generate with specific output location::
+
+    ct-compilation-database --compilation-database-output build/compile_commands.json
+
+Generate with relative paths for portability::
+
+    ct-compilation-database --relative-paths
+
+Generate for specific source files (disables auto-detection)::
+
+    ct-compilation-database --no-auto src/main.cpp src/utils.cpp
+
+INTEGRATION WITH ct-cake
+=========================
+ct-cake automatically generates compile_commands.json by default. To control this
+behavior, use these flags:
+
+--compilation-database / --no-compilation-database
+    Enable or disable automatic generation (default: enabled)
+
+--compilation-database-output OUTPUT
+    Customize output location
+
+--compilation-database-relative-paths
+    Use relative paths
+
+Example ct-cake usage::
+
+    ct-cake --no-compilation-database    # Disable generation
+    ct-cake --compilation-database-output .compile_db.json
+
+CLANGD CONFIGURATION
+====================
+For best results with clangd, create a .clangd config file in your project root:
+
+.. code-block:: yaml
+
+    CompileFlags:
+      CompilationDatabase: .
+
+This tells clangd to use the compile_commands.json in the project root.
+
+SEE ALSO
+========
+``compiletools`` (1), ``ct-cake`` (1), ``ct-config`` (1)
+
+REFERENCES
+==========
+* JSON Compilation Database: https://clang.llvm.org/docs/JSONCompilationDatabase.html
+* clangd: https://clangd.llvm.org/

{compiletools-5.3.3 → compiletools-6.0.2}/src/compiletools/README.ct-config.rst

@@ -9,7 +9,7 @@ Helper tool for examining ct-* configuration
 :Author: drgeoffathome@gmail.com
 :Date:   2016-08-16
 :Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
-:Version: 5.3.3
+:Version: 6.0.2
 :Manual section: 1
 :Manual group: developers
 

{compiletools-5.3.3 → compiletools-6.0.2}/src/compiletools/README.ct-cppdeps.rst

@@ -9,7 +9,7 @@ What
 :Author: drgeoffathome@gmail.com
 :Date:   2022-06-05
 :Copyright: Copyright (C) Geoffery Ericksson
-:Version: 4.1.85
+:Version: 6.0.2
 :Manual section: 1
 :Manual group: developers
 
@@ -33,20 +33,21 @@ ct-cppdeps generates the header dependencies for the file you specify at the
 command line.  There are two possible methodologys:  
 
 * "--headerdeps=direct" uses a regex to find the "#include" lines in the source
-  code. This methodology is fast. However, while the regex correctly ignores 
-  commented out includes, it incorrectly identifies files that are surrounded 
-  by #ifdef 0 guards.
+  code. This methodology is fast and is supposed to generate the same results as 
+  using the compiler to preprocess the file.  However, its own simple 
+  preprocessor does not handle all the complexities of a real C/C++
+  preprocessor and so it is possible to generate incorrect results.
 
 * "--headerdeps=cpp" executes "$CPP -MM -MF" which is slower but guarantees correctness.  
 
 
 For each header file found in the source file, it looks for
-an underlying implementation (c,cpp,cc,cxx,etc) file with the same name, and 
-adds that implementation file to the build.  
-ct-cppdeps also reads the first 8KB of each file for special comments
-that indicate needed link and compile flags.  Then it recurses through the
-dependencies of the cpp file, and uses this spidering to generate complete
-dependency information for the application. 
+an underlying implementation (c,cpp,cc,cxx,etc) file with the same name, and
+adds that implementation file to the build.
+ct-cppdeps also reads the entire file (configurable via --max-file-read-size)
+for special comments that indicate needed link and compile flags.  Then it
+recurses through the dependencies of the cpp file, and uses this spidering to
+generate complete dependency information for the application. 
 
 EXAMPLES
 ========

compiletools-6.0.2/src/compiletools/README.ct-doc.rst

@@ -0,0 +1,141 @@
+.. image:: https://github.com/DrGeoff/compiletools/actions/workflows/main.yml/badge.svg
+    :target: https://github.com/DrGeoff/compiletools/actions
+
+============
+compiletools
+============
+
+--------------------------------------------------------
+C/C++ build tools that requires almost no configuration.
+--------------------------------------------------------
+
+:Author: drgeoffathome@gmail.com
+:Date:   2016-08-09
+:Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
+:Version: 6.0.2
+:Manual section: 1
+:Manual group: developers
+
+SYNOPSIS
+========
+    ct-* [compilation args] [filename.cpp] [--variant=<VARIANT>]
+
+DESCRIPTION
+===========
+The various ct-* tools exist to build C/C++ executables with almost no
+configuration. For example, to build a C or C++ program, type
+
+.. code-block:: bash
+
+    ct-cake
+
+which will automatically determine the correct source files to generate executables
+from and also determine the tests to build and run. (The ``--auto`` flag is the
+default; use ``--no-auto`` to disable automatic target detection.)
+
+A variant is a configuration file that specifies various configurable settings
+like the compiler and compiler flags. Common variants are "debug" and "release".
+
+CONFIGURATION
+=============
+Options are parsed using the python package ConfigArgParse.  This means they can be passed
+in on the command line, as environment variables or in config files.
+Command-line values override environment variables which override config file 
+values which override defaults. Note that the environment variables are 
+captilized. That is, a command line option of --magic=cpp is the equivalent of 
+an environment variable MAGIC=cpp.
+
+If the option itself starts with a hypen then configargparse can fail to parse 
+it as you intended. For example, on many platforms,
+
+.. code-block:: bash
+
+    --append-CXXFLAGS=-march=skylake
+
+will fail. To work around this, compiletools postprocesses the options to 
+understand quotes. For example,
+
+.. code-block:: bash
+
+    --append-CXXFLAGS="-march=skylake" 
+
+will work on all platforms.  Note however that many shells (e.g., bash) will strip 
+quotes so you need to escape the quotes or single quote stop the shell preprocessing. 
+For example,
+
+.. code-block:: bash
+
+    --append-CXXFLAGS=\\"-march=skylake\\"  
+    or 
+    --append-CXXFLAGS='"-march=skylake"'
+
+SHARED OBJECT CACHE
+===================
+compiletools supports a shared object file cache for multi-user/multi-host
+environments. When enabled via ``shared-objects = true`` in ct.conf 
+(or via the command line or environment variable), the Makefile
+generation includes proper locking mechanisms to safely share object files across
+concurrent builds by multiple users and hosts. 
+
+Setting in ct.conf is the recommended way to enable this feature for teams so that 
+all users gain the locking without needing to set their own environment variables. 
+
+This feature can also be used by a single developer on a single machine to compile 
+different directories in parallel, sharing the same object file cache for objects 
+that are in common.
+
+Key features:
+
+* **Content-addressable storage**: Object files named by source + flags hash
+* **Filesystem-aware locking**: Uses flock on local filesystems, atomic mkdir on network filesystems (NFS, GPFS, Lustre)
+* **Multi-user safe**: Group-writable cache with proper file permissions
+* **Cross-host compatible**: Automatic filesystem detection and appropriate locking strategy
+* **Stale lock detection**: Automatic cleanup of locks from crashed builds
+* **Minimal configuration**: Just set ``shared-objects = true`` in config
+
+Example setup for shared cache:
+
+.. code-block:: bash
+
+    # In ct.conf or variant config
+    shared-objects = true
+    objdir = /shared/nfs/build/cache
+
+    # Ensure cache directory is group-writable with SGID
+    mkdir -p /shared/nfs/build/cache
+    chmod 2775 /shared/nfs/build/cache
+
+Configuration options in ct.conf:
+
+* ``max_file_read_size = 0`` - Bytes to read from files (0 = entire file)
+* ``shared-objects = true`` - Enable shared object cache
+
+OTHER TOOLS
+===========
+Other notable tools are:
+
+* ct-headertree: provides information about structure of the include files
+* ct-filelist: provides the list of files needed to be included in a tarball (e.g. for packaging)
+
+SEE ALSO
+========
+* ct-build
+* ct-build-dynamic-library
+* ct-build-static-library
+* ct-cache
+* ct-cache-clean
+* ct-cake
+* ct-cmakelists
+* ct-compilation-database
+* ct-config
+* ct-cppdeps
+* ct-create-cmakelists
+* ct-create-makefile
+* ct-filelist
+* ct-findtargets
+* ct-git-sha-report
+* ct-gitroot
+* ct-headertree
+* ct-jobs
+* ct-list-variants
+* ct-magicflags

{compiletools-5.3.3 → compiletools-6.0.2}/src/compiletools/README.ct-filelist.rst

@@ -9,7 +9,7 @@ Determine header and source dependencies of a C/C++ file by following headers an
 :Author: drgeoffathome@gmail.com
 :Date:   2017-07-06
 :Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
-:Version: 5.3.3
+:Version: 6.0.2
 :Manual section: 1
 :Manual group: developers
 

{compiletools-5.3.3 → compiletools-6.0.2}/src/compiletools/README.ct-findtargets.rst

@@ -9,7 +9,7 @@ What
 :Author: drgeoffathome@gmail.com
 :Date:   2018-04-17
 :Copyright: Copyright (C) 2011-2018 Zomojo Pty Ltd
-:Version: 5.3.3
+:Version: 6.0.2
 :Manual section: 1
 :Manual group: developers
 

{compiletools-5.3.3 → compiletools-6.0.2}/src/compiletools/README.ct-gitroot.rst

@@ -9,7 +9,7 @@ What directory is the root of the git repository?
 :Author: drgeoffathome@gmail.com
 :Date:   2017-09-28
 :Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
-:Version: 5.3.3
+:Version: 6.0.2
 :Manual section: 1
 :Manual group: developers