Skip to content

Releases: jade-nl/dt.bldr

dt.bldr v2.0.0 released

03 Apr 14:48
e4b5e23
Compare
Choose a tag to compare

I just released dt.bldr 2.0.0

Changes

The possibility to use non-default configuration files

  • It is now possible to point dt.bldr.sh to a specific, non-standard configuration file from the command line using -C /path/to/file. As is the case with the user specific default configuration file, this one is put on top of the default configuration file when it is parsed.

  • Using the -C file option automatically sets the build flag (-b). This means that a build is triggered when using the -C file option (-bC file and -C file do the same thing).

  • The previous method, using the default configuration files, is still the default behaviour when running dt.bldr.sh without the -C file option.

  • Merging can now be done without forcing a clone if wanted/needed.
    The default behaviour is still a forced clone before the external branch is merged, but this can now be overridden using the -p flag in conjunction with the -m (or -M file) option. This also makes merging multiple external branches possible.

  • Using the -M file option instead of -m it is now possible to point dt.bldr.sh to a specific file that holds the configuration needed. Using -m will still use the default configuration file ($HOME/.local/cfg/dt.ext.branch.cfg).
    The -M file option expects a valid file to use.

  • Multiple branches can be merged in the following way:

    dt.bldr.sh -m or dt.bldr.sh -M /path/to/merge.file.1.cfg
    dt.bldr.sh -pM /path/to/merge.file.2.cfg
    dt.bldr.sh -pM /path/to/merge.file.3.cfg
    dt.bldr.sh -bi

  • All external branch merge actions are now included in the log file

It is strongly recommended to run the installer and not copy files by hand to make sure that everything is set up correctly for this new version.


IMPORTANT NOTE:

!! The location of the log files has changed !!

Because of the above modifications I had to change the way log files are handled:

  • The location can no longer be set in the configuration files
  • The log files location is now hardcoded in dt.bldr.sh
  • The new log files location is /opt/dt.bldr/log
  • The UID of the user running the script is now added to the log filenames

Running the installer (install.sh) will take care of the obsolete option (logDir="$HOME/.local/log") in the main configuration file. If this entry is present in your personal configuration file ($HOME/.local/cfg/dt.bldr.cfg), you need to remove it yourself. Leaving it in will not do any harm, but it will be ignored.

v1.7.5

01 Apr 11:52
bb70096
Compare
Choose a tag to compare
  • removed obsolete github option
  • made merging of external branches more flexible

v1.7.3

16 Nov 10:43
Compare
Choose a tag to compare

Project is basically complete. I'll push a new release along with any (minor) changes made from now on.

Just 3 minor updates since release 1.7.0:

  • Streamlined the compiler option (1.7.1)
  • Make sure cloned repo is 100% clean
  • Disable integration test downloads (1.7.2)
  • Removed now obsolete CMake option (1.7.3)

Version 1.7.0 is available

14 Nov 20:24
4ad6da7
Compare
Choose a tag to compare

Added the possibility to use clang as the default compiler instead of gcc. Out-of-the-box gcc is still the default.

If clang is wanted add the following to the local configuration file ($HOME/.local/cfg/dt.bldr.cfg):

# -------------------------------------------------------------------------- #
# use gcc or clang as compiler
compSRC="clang"