1 <!-- STDfilenameDTS -->
13 In the startup/design phase, does nothing yet.
24 The `master` branch is considered stable, no unstable development
25 happens there. Every new functionality or bug fix is created on topic
26 branches which may be rebased now and then. All tests on `master`
27 (executed with "make test") MUST succeed. If any test fails, it's
28 considered a bug. Please report any failing tests in the issue tracker.
30 To ensure compatibility between versions, the program follows the
31 Semantic Versioning Specification described at <http://semver.org>.
32 Using the version number `X.Y.Z` as an example:
34 - `X` is the *major version*.
35 This number is only incremented when backwards-incompatible changes
37 - `Y` is the *minor version*.
38 Increased when new backwards-compatible features are added.
39 - `Z` is the *patch level*.
40 Increased when new backwards-compatible bugfixes are added.
46 Generate the `STDexecDTS` executable.
50 Remove all generated files except `tags`.
54 Open all files in the subtree in your favourite editor defined in
59 Generate test coverage with `gcov`(1). Should be as close to 100% as
62 ### make gcov-cmt / make gcov-cmt-clean
64 Add or remove `gcov` markers in the source code in lines that are not
65 tested. Lines that are hard to test, for example full disk, full memory,
66 long paths and so on, can be marked with the string `/* gncov */` to
67 avoid marking them. To mark lines even when marked with gncov, set the
68 GNCOV environment variable to a non-empty value. For example:
72 These commands need the `gcov-cmt` script, available from
73 <https://gitlab.com/oyvholm/utils/raw/master/gcov-cmt>.
77 Start gdb with main() as the default breakpoint, this is defined in
78 `src/gdbrc`. Any additional gdb options can be added in `src/gdbopts`.
79 An example would be "-tty /dev/\[...\]" to send the program output to
84 `make install` installs `STDexecDTS` to the location defined by `PREFIX`
85 in `src/Makefile`. Default location is `/usr/local`, but it can be
86 installed somewhere else by specifying `PREFIX`. For example:
88 make install PREFIX=~/local
92 Generate `tags` file, used by Vim and other editors.
96 Run all tests. This command MUST NOT fail on purpose on `master`.
100 Delete the installed version from `PREFIX`.
104 Run all tests with Valgrind to find memory leaks and other problems.
105 Should also not fail on master.
107 ### Create HTML or PDF
109 `make html` creates HTML versions of all documentation in the current
110 directory tree, and `make pdf` creates PDF versions.
112 All `*.md` files can be converted to HTML or PDF by replacing the `.md`
113 extension with `.html` or `.pdf`. For example, use `make README.html` to
114 generate an HTML file from the `.md` file, or `make README.pdf` to
115 create a PDF version. If the `.md` file is stored in Git, an extra
116 footer with the text "Generated from *filename* revision *git-id*
119 Uses `cmark`, available from <https://commonmark.org/>.
123 The main Git repository is stored at GitLab:
125 - URL: <https://gitlab.com/oyvholm/STDexecDTS>
126 - SSH clone: git@gitlab.com:oyvholm/STDexecDTS.git
127 - https clone: <https://gitlab.com/oyvholm/STDexecDTS.git>
131 This program is free software; you can redistribute it and/or modify it
132 under the terms of the GNU General Public License as published by the
133 Free Software Foundation; either version 2 of the License, or (at your
134 option) any later version.
136 This program is distributed in the hope that it will be useful, but
137 WITHOUT ANY WARRANTY; without even the implied warranty of
138 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
139 Public License for more details.
141 You should have received a copy of the GNU General Public License along
142 with this program. If not, see <http://www.gnu.org/licenses/>.
146 Øyvind A. Holm \<<sunny@sunbase.org>\>
148 ## About this document
150 This file is written in [Commonmark](https://commonmark.org) and all
151 `make` commands use `cmark`(1) to generate HTML and reformat text.
153 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
154 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
155 document are to be interpreted as described in RFC 2119.
162 vim: set ts=2 sw=2 sts=2 tw=72 et fo=tcqw fenc=utf8 :
163 vim: set com=b\:#,fb\:-,fb\:*,n\:> ft=markdown :