diff options
| author | Mike Taves <mwtoews@gmail.com> | 2019-09-25 11:47:40 +1200 |
|---|---|---|
| committer | Mike Taves <mwtoews@gmail.com> | 2019-09-25 20:50:07 +1200 |
| commit | 4013aeaaf7796cfff6b97668870ce4a2af3d509a (patch) | |
| tree | 3d19245a8df8c4f102d28c4b19a1065d81957b8f /docs/source/community | |
| parent | 14828d9695ab54272fee0dab35a489180c20f2ea (diff) | |
| download | PROJ-4013aeaaf7796cfff6b97668870ce4a2af3d509a.tar.gz PROJ-4013aeaaf7796cfff6b97668870ce4a2af3d509a.zip | |
Upgrade testing from trusty to xenial, and also:
* From openjdk-7 via apt to openjdk-11 via Travis CI xenial's $JAVA_HOME
* From mingw 4.8 -> 5.3, as supported by xenial
* clang+llvm for csa kept at version 6.0.0, but for ubuntu-16.04
* Furthermore xenial implicitly has many upgrades, specifically:
- gcc 4.8.4 -> 5.4.0
- clang 4.0.0 -> 5.0.0
- cmake 3.9.2 -> 3.12.4
- python 3.4.3 -> 3.5.2
* cppcheck version kept at 1.61 (for trusty) due to many
false positives with version 1.72 (for xenial)
* Community code contribution documentation simplified to remove
version of cppcheck, as this may outdated with updates to scripts
Diffstat (limited to 'docs/source/community')
| -rw-r--r-- | docs/source/community/code_contributions.rst | 13 |
1 files changed, 4 insertions, 9 deletions
diff --git a/docs/source/community/code_contributions.rst b/docs/source/community/code_contributions.rst index 3c8850bd..7e354a70 100644 --- a/docs/source/community/code_contributions.rst +++ b/docs/source/community/code_contributions.rst @@ -88,12 +88,7 @@ cppcheck static analyzer ~~~~~~~~~~~~~~~~~~~~~~~~ You can run locally ``scripts/cppcheck.sh`` that is a wrapper script around the -cppcheck utility. It is known to work with cppcheck 1.61 of Ubuntu Trusty 14.0, -since this is what is currently used on Travis-CI -(``travis/linux_gcc/before_install.sh``). -At the time of writing, this also works with cppcheck 1.72 of Ubuntu Xenial -16.04, and latest cppcheck -master. +cppcheck utility. This tool is used as part of the quality control of the code. cppcheck can have false positives. In general, it is preferable to rework the code a bit to make it more 'obvious' and avoid those false positives. When not @@ -115,9 +110,9 @@ Preliminary step: install clang. For example: :: - wget http://releases.llvm.org/6.0.0/clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz - tar xJf clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz - mv clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04 clang+llvm-6 + wget http://releases.llvm.org/6.0.0/clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz + tar xJf clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz + mv clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-16.04 clang+llvm-6 Run configure under the scan-build utility of clang: |