Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: jacobwilliams/json-fortran
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 4.2.0
Choose a base ref
...
head repository: jacobwilliams/json-fortran
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
Loading
Showing with 26,712 additions and 9,641 deletions.
  1. +1 −0 .PREPROCESSOR
  2. +1 −0 .VERSION
  3. +1 −0 .VERSION.in
  4. +6 −7 { → .github}/CONTRIBUTING.md
  5. +182 −0 .github/workflows/CI.yml
  6. +27 −9 .gitignore
  7. +0 −106 .travis.yml
  8. +658 −2 CHANGELOG.md
  9. +239 −138 CMakeLists.txt
  10. +2 −2 LICENSE
  11. +76 −203 README.md
  12. +0 −1 __VERSION__
  13. +217 −166 build.sh
  14. +3 −3 cmake/jsonfortran-config.cmake.in
  15. +12 −2 cmake/pickFortranCompilerFlags.cmake
  16. +2 −2 cmake/pkg/jsonfortran-config.cmake.in
  17. +4 −4 cmake/uninstall.cmake.in
  18. +15 −0 codecov.yml
  19. +0 −34 deploy.sh
  20. +0 −1 files/expected-outputs/hello-world-ascii.json
  21. +23 −0 files/expected-outputs/hello-world-ascii.json
  22. +0 −1 files/expected-outputs/hello-world-ucs4.json
  23. +23 −0 files/expected-outputs/hello-world-ucs4.json
  24. +1 −1 files/expected-outputs/test12.json
  25. +0 −1 files/expected-outputs/test2.json
  26. +100 −0 files/expected-outputs/test2.json
  27. +13 −0 files/expected-outputs/test21.json
  28. +57 −0 files/inputs/comments.json
  29. +1 −1 files/inputs/invalid.json
  30. +4 −0 files/inputs/invalid3.json
  31. +11 −0 files/inputs/invalid4.json
  32. +51 −37 files/inputs/test1.json
  33. +2 −1 files/inputs/test2.json
  34. +269 −0 fpm.toml
  35. +13 −0 json-fortran.code-workspace
  36. +155 −0 json-fortran.fobis
  37. +45 −27 json-fortran.md
  38. +9 −0 json-fortran.pc.cmake.in
  39. BIN media/json-fortran-logo-2.png
  40. +131 −0 media/json-fortran-logo-2.svg
  41. BIN media/json-fortran-logo-250px.png
  42. +24 −26 media/json-fortran-logo.svg
  43. +57 −0 packaging/CMakeLists.txt
  44. +3 −3 pages/development-resources/{travis.yml.md → CI.yml.md}
  45. +1 −1 pages/development-resources/CONTRIBUTING.md
  46. +7 −0 pages/development-resources/codecov.yml.md
  47. +0 −9 pages/development-resources/deploy.sh.md
  48. +1 −1 pages/development-resources/gccr.pl
  49. +4 −5 pages/development-resources/index.md
  50. +6 −3 pages/development-resources/json_module.F90.gcov.md
  51. +15 −14 pages/development-resources/release-checklist.md
  52. +3 −3 pages/index.md
  53. +126 −12 pages/releases/index.md
  54. +3,066 −0 src/json_file_module.F90
  55. +32 −0 src/json_get_scalar_by_path.inc
  56. +27 −0 src/json_get_vec_by_path.inc
  57. +43 −0 src/json_get_vec_by_path_alloc.inc
  58. +117 −0 src/json_initialize_arguments.inc
  59. +26 −0 src/json_initialize_dummy_arguments.inc
  60. +148 −0 src/json_kinds.F90
  61. +58 −0 src/json_macros.inc
  62. +58 −6,849 src/json_module.F90
  63. +144 −0 src/json_parameters.F90
  64. +932 −0 src/json_string_utilities.F90
  65. +11,618 −0 src/json_value_module.F90
  66. +519 −0 src/tests/jf_test_01.F90
  67. +429 −0 src/tests/jf_test_02.F90
  68. +50 −29 src/tests/{jf_test_3.f90 → jf_test_03.F90}
  69. +73 −40 src/tests/{jf_test_4.f90 → jf_test_04.F90}
  70. +31 −27 src/tests/{jf_test_5.f90 → jf_test_05.F90}
  71. +128 −0 src/tests/jf_test_06.F90
  72. +281 −0 src/tests/jf_test_07.F90
  73. +42 −37 src/tests/{jf_test_8.f90 → jf_test_08.F90}
  74. +23 −24 src/tests/{jf_test_9.f90 → jf_test_09.F90}
  75. +0 −261 src/tests/jf_test_1.f90
  76. +106 −80 src/tests/{jf_test_10.f90 → jf_test_10.F90}
  77. +74 −73 src/tests/jf_test_11.F90
  78. +256 −0 src/tests/jf_test_12.F90
  79. +0 −218 src/tests/jf_test_12.f90
  80. +28 −22 src/tests/{jf_test_13.f90 → jf_test_13.F90}
  81. +168 −0 src/tests/jf_test_14.F90
  82. +0 −121 src/tests/jf_test_14.f90
  83. +265 −0 src/tests/jf_test_15.F90
  84. +236 −0 src/tests/jf_test_16.F90
  85. +190 −0 src/tests/jf_test_17.F90
  86. +126 −0 src/tests/jf_test_18.F90
  87. +182 −0 src/tests/jf_test_19.F90
  88. +0 −237 src/tests/jf_test_2.f90
  89. +220 −0 src/tests/jf_test_20.F90
  90. +94 −0 src/tests/jf_test_21.F90
  91. +97 −0 src/tests/jf_test_22.F90
  92. +310 −0 src/tests/jf_test_23.F90
  93. +177 −0 src/tests/jf_test_24.F90
  94. +167 −0 src/tests/jf_test_25.F90
  95. +86 −0 src/tests/jf_test_26.F90
  96. +94 −0 src/tests/jf_test_27.F90
  97. +133 −0 src/tests/jf_test_28.F90
  98. +159 −0 src/tests/jf_test_29.F90
  99. +87 −0 src/tests/jf_test_30.F90
  100. +112 −0 src/tests/jf_test_31.F90
  101. +127 −0 src/tests/jf_test_32.F90
  102. +111 −0 src/tests/jf_test_33.F90
  103. +165 −0 src/tests/jf_test_34.F90
  104. +101 −0 src/tests/jf_test_35.F90
  105. +135 −0 src/tests/jf_test_36.F90
  106. +158 −0 src/tests/jf_test_37.F90
  107. +148 −0 src/tests/jf_test_38.F90
  108. +83 −0 src/tests/jf_test_39.F90
  109. +69 −0 src/tests/jf_test_40.F90
  110. +142 −0 src/tests/jf_test_41.F90
  111. +137 −0 src/tests/jf_test_42.F90
  112. +103 −0 src/tests/jf_test_43.F90
  113. +115 −0 src/tests/jf_test_44.F90
  114. +161 −0 src/tests/jf_test_45.F90
  115. +307 −0 src/tests/jf_test_46.F90
  116. +149 −0 src/tests/jf_test_47.F90
  117. +103 −0 src/tests/jf_test_48.F90
  118. +77 −0 src/tests/jf_test_49.F90
  119. +101 −0 src/tests/jf_test_50.F90
  120. +92 −0 src/tests/jf_test_51.F90
  121. +0 −86 src/tests/jf_test_6.f90
  122. +0 −276 src/tests/jf_test_7.f90
  123. +41 −0 visual_studio/jsonfortran.sln
  124. +55 −0 visual_studio/jsonfortranlib/jsonfortranlib.vfproj
  125. +118 −0 visual_studio/jsonfortrantest/jsonfortrantest.f90
  126. +101 −0 visual_studio/jsonfortrantest/jsonfortrantest.vfproj
  127. +0 −110 visual_studio_2010/jsonfortran.sln
  128. +0 −31 visual_studio_2010/jsonfortran.vfproj
  129. +0 −29 visual_studio_2010/test1.vfproj
  130. +0 −33 visual_studio_2010/test11.vfproj
  131. +0 −29 visual_studio_2010/test2.vfproj
  132. +0 −29 visual_studio_2010/test3.vfproj
  133. +0 −29 visual_studio_2010/test4.vfproj
  134. +0 −29 visual_studio_2010/test5.vfproj
  135. +0 −29 visual_studio_2010/test6.vfproj
  136. +0 −29 visual_studio_2010/test7.vfproj
  137. +0 −29 visual_studio_2010/test8.vfproj
  138. +0 −29 visual_studio_2010/test9.vfproj
1 change: 1 addition & 0 deletions .PREPROCESSOR
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
gfortran -E
1 change: 1 addition & 0 deletions .VERSION
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
9.0.3
1 change: 1 addition & 0 deletions .VERSION.in
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
${PROJECT_VERSION}
13 changes: 6 additions & 7 deletions CONTRIBUTING.md → .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -31,20 +31,20 @@ Looking to contribute something to [JSON-Fortran](https://github.com/jacobwillia
[top](#contributing-to-json-fortran)
## Outstanding Work

- Take a look at the [issues](https://github.com/jacobwilliams/json-fortran/issues) to see if there is an issue you'd like to help address. [Issues](https://github.com/jacobwilliams/json-fortran/issues) with the [ready label](https://github.com/jacobwilliams/json-fortran/issues?q=is%3Aopen+is%3Aissue+label%3A%22ready%22) or in the [ready column on waffle.io](https://waffle.io/jacobwilliams/json-fortran) are issues that are ready to be dealt with. (i.e., They are not blocked by other dependencies and are higher priority.)
- Take a look at the [issues](https://github.com/jacobwilliams/json-fortran/issues) to see if there is an issue you'd like to help address. [Issues](https://github.com/jacobwilliams/json-fortran/issues) with the [ready label](https://github.com/jacobwilliams/json-fortran/issues?q=is%3Aopen+is%3Aissue+label%3A%22ready%22) are issues that are ready to be dealt with. (i.e., They are not blocked by other dependencies and are higher priority.)
- Increasing the test coverage is another helpful way to
contribute. Please take a look at
[the test coverage page](http://jacobwilliams.github.io/json-fortran/page/development-resources/json_module.F90.gcov.html)
[the test coverage page](https://jacobwilliams.github.io/json-fortran/page/development-resources/json_module.F90.gcov.html)
for a list of uncovered procedures, and at the
[Codecov.io suggestions page](https://codecov.io/github/jacobwilliams/json-fortran/features/suggestions)
[Codecov.io coverage status](https://codecov.io/gh/jacobwilliams/json-fortran)
to find procedures and lines of code that are still uncovered by the
[unit tests](https://github.com/jacobwilliams/json-fortran/tree/master/src/tests). It
is worth pointing out that the majority of uncovered procedures are
internal, overloaded procedures and can only be exercised by calling
the corresponding generic procedure with input arguments that will
resolve to the specific procedure in question. Let's keep the
following graph trending upwards!
![Codecov.io](https://codecov.io/github/jacobwilliams/json-fortran/branch.svg?branch=master)
![Codecov.io](https://codecov.io/gh/jacobwilliams/json-fortran/branch/master/graphs/commits.svg)

[top](#contributing-to-json-fortran)
## Pull Requests
@@ -72,7 +72,7 @@ git rebase upstream/master
```
- Create a branch in your fork with a descriptive name that also includes the [issue number](https://github.com/jacobwilliams/json-fortran/issues), if applicable. For example, after forking the repo, you can run something like `git checkout -b Unicode-support-issue-35` before starting work on [issue #35 : Unicode support](https://github.com/jacobwilliams/json-fortran/issues/35)
- When you're content with your changes, your commits are clean, self contained, with concise descriptive messages, and your changes compile and pass the tests, submit a pull request. We will review your changes, and may ask for certain modifications to be made.
- Pull requests are tested by our [travis-ci](https://travis-ci.org/jacobwilliams/json-fortran) continuous integration system, and any errors uncovered will need to be fixed before the pull request can be merged into master.
- Pull requests are tested by our [GitHub Actions](https://github.com/jacobwilliams/json-fortran/actions) continuous integration system, and any errors uncovered will need to be fixed before the pull request can be merged into master.
- The JSON-Fortran library and associated documentation is released under a BSD style [license](https://github.com/jacobwilliams/json-fortran/blob/master/LICENSE). By submitting a pull request, you are agreeing to release your code under the same license. Note that code with GPL or other "copyleft" style licenses will not be accepted.

[top](#contributing-to-json-fortran)
@@ -98,7 +98,6 @@ git rebase upstream/master
- Please adhere to the code indentation and formatting as it currently exists, aligning common elements vertically, etc. Tab characters are not allowed. Indentations should be done with *4* space characters.
- *Do NOT* allow your editor to make a bunch of indentation or white space changes, that will introduce non-substantive changes on lines that you have not actually edited.
- The coding style is modern free-form Fortran, consistent with the Fortran 2008 standard. Note that the two supported compilers (ifort and gfortran) do not currently include the entire Fortran 2008 standard. Therefore, only those language features supported by Gfortran 4.9 and Intel 13.1.0 are currently allowed. This also means that previous versions of these compilers are not supported, and major changes to the code to support earlier compilers (or Fortran 95) will not be accepted. At some point in the future (when compiler support has improved), all Fortran 2008 features will be allowed.
- All subroutines and functions *must* be properly documented. This includes useful inline comments as well as comment blocks using the [FORD](https://github.com/cmacmackin/ford/wiki/Writing-Documentation) syntax.
- For simplicity, JSON-Fortran currently consists of one module file. It is not envisioned that it will ever need to expand to include multiple files (if it does, there would need to be a very good reason).
- All subroutines and functions *must* be properly documented. This includes useful inline comments as well as comment blocks using the [FORD](https://github.com/Fortran-FOSS-Programmers/ford/wiki/Writing-Documentation) syntax.

[top](#contributing-to-json-fortran)
182 changes: 182 additions & 0 deletions .github/workflows/CI.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,182 @@
name: CI

on: [push, pull_request]

jobs:

Build:
runs-on: ${{ matrix.os }}
strategy:
fail-fast: false
matrix:
os: [ubuntu-20.04]
gcc_v: [7,8,9,10,11] # Version of GFortran we want to use.
python-version: [3.11]
env:
FC: gfortran-${{matrix.gcc_v}}
GCC_V: ${{matrix.gcc_v}}

steps:

- name: Checkout code
uses: actions/checkout@v4.1.6
with:
submodules: recursive

- name: Setup cmake
if: contains( matrix.gcc_v, 9 )
uses: jwlawson/actions-setup-cmake@v2.0.2
with:
cmake-version: '3.28.x'

- name: Install Python
uses: actions/setup-python@v5.1.0 # Use pip to install latest CMake, & FORD/Jin2For, etc.
with:
python-version: ${{ matrix.python-version }}

- name: Setup Graphviz
uses: ts-graphviz/setup-graphviz@v2.0.2

- name: Install Python dependencies
if: contains( matrix.os, 'ubuntu')
run: |
python -m pip install --upgrade pip
pip install ford FoBiS.py pygooglechart fpm
if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
- name: Install GFortran Linux
if: contains( matrix.os, 'ubuntu')
run: |
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get install -y gcc-${GCC_V} gfortran-${GCC_V}
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-${GCC_V} 100 \
--slave /usr/bin/gfortran gfortran /usr/bin/gfortran-${GCC_V} \
--slave /usr/bin/gcov gcov /usr/bin/gcov-${GCC_V}
- name: Compile_with_build
if: matrix.gcc_v != 7 && matrix.gcc_v != 11
run: |
GFORTRAN=gfortran-${{matrix.gcc_v}}
GCOV=gcov-${{matrix.gcc_v}}
# build with build.sh, run unit tests
./build.sh --skip-documentation
./build.sh --skip-documentation --enable-unicode
- name: Compile_with_FPM
if: matrix.gcc_v == 11
run: |
GFORTRAN=gfortran-${{matrix.gcc_v}}
GCOV=gcov-${{matrix.gcc_v}}
sudo apt update && sudo apt install -y valgrind
fpm test jf_test_01 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_02 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_03 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_04 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_05 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_06 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_07 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_08 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_09 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_10 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_11 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_12 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_13 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_14 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_15 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_16 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_17 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_18 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_19 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_20 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_21 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_22 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_23 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_24 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_25 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_26 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_27 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_28 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_29 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_30 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_31 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_32 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_33 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_34 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_35 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_36 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_37 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_38 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_39 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_40 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_41 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_42 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_43 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_44 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_45 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_46 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_47 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_48 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_49 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_50 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
fpm test jf_test_51 --runner "valgrind --leak-check=full --show-leak-kinds=all --error-exitcode=1"
- name: Compile_with_cmake
# CMake build with unit tests, no documentation, with coverage analysis
# No unicode so that coverage combined with the build script will cover unicode
# and non-unicode code paths
if: matrix.gcc_v == 9
run: |
GFORTRAN=gfortran-${{matrix.gcc_v}}
GCOV=gcov-${{matrix.gcc_v}}
mkdir cmake-build
cd cmake-build
cmake -D ENABLE_TESTS=ON ..
make -j 4 check
- name: Compile_with_build_mkdocs
# build with build.sh, make documentation, run unit tests
# and perform coverage analysis - used for doc deployment
if: matrix.gcc_v == 7
run: |
GFORTRAN=gfortran-${{matrix.gcc_v}}
GCOV=gcov-${{matrix.gcc_v}}
./build.sh --coverage --skip-documentation
./build.sh --coverage --enable-unicode
- name: Deploy Documentation for master
if: matrix.gcc_v == 7 && github.ref == 'refs/heads/master'
uses: JamesIves/github-pages-deploy-action@v4.7.3
with:
branch: gh-pages # The branch the action should deploy to.
folder: doc # The folder the action should deploy.
clean: true
clean-exclude: |
prev
- name: Rebuild documentation for tagged release
env:
TAGNAME: ${{github.ref_name}}
if: matrix.gcc_v == 7 && startsWith(github.ref, 'refs/tags/')
run: |
echo ${TAGNAME}
rm -rf doc
sed "2 s/^/version: ${TAGNAME}\n/" json-fortran.md > json-fortran.tagged.md
ford --debug json-fortran.tagged.md
- name: Deploy documentation for tagged release
if: matrix.gcc_v == 7 && startsWith(github.ref, 'refs/tags/')
uses: JamesIves/github-pages-deploy-action@v4.7.3
with:
branch: gh-pages # The branch the action should deploy to.
folder: doc # The folder the action should deploy.
target-folder: prev/${{github.ref_name}} # deploy to a version-specific folder
single-commit: true

- name: Upload coverage
if: matrix.gcc_v == 7
run: |
rm json_*.F90-*unicode.gcov || true
mv json_*.F90.gcov src/
mv jf_test*.[fF]90.gcov src/tests/
bash <(curl -s https://codecov.io/bash) -v -X $GCOV
36 changes: 27 additions & 9 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,7 +1,11 @@
bin/
lib/
builds/
build/
install/
doc/
.vscode/

*.gcov
*.gcov.md*
*.mod
@@ -11,12 +15,26 @@ doc/
.sconsign.*
files/*.json
.cflags.*
src/tests/jf_test_example[12].f90
documentation/
visual_studio_2010/*.suo
visual_studio_2010/*.u2d
visual_studio_2010/Debug/
visual_studio_2010/Release/
visual_studio_2010/x64
FoBiS.py
robodoc
*.suo
*.u2d
*.user
*.fdz

visual_studio/Debug/
visual_studio/Release/
visual_studio/x64/
visual_studio/.vs/
visual_studio/jsonfortranlib/
visual_studio/jsonfortrantest/Debug/
visual_studio/jsonfortrantest/Release/
visual_studio/jsonfortrantest/x64
visual_studio/config
My Advisor Results*
My Amplifier*
My Inspector*
x64/
Debug/
Release/

# mac
.DS_Store
106 changes: 0 additions & 106 deletions .travis.yml

This file was deleted.

Loading