1. 07 Mar, 2019 1 commit
  2. 05 Mar, 2019 3 commits
  3. 04 Mar, 2019 2 commits
  4. 02 Mar, 2019 4 commits
  5. 01 Mar, 2019 4 commits
  6. 28 Feb, 2019 2 commits
  7. 26 Feb, 2019 2 commits
  8. 24 Feb, 2019 7 commits
  9. 23 Feb, 2019 2 commits
  10. 22 Feb, 2019 3 commits
  11. 21 Feb, 2019 1 commit
  12. 20 Feb, 2019 3 commits
  13. 19 Feb, 2019 6 commits
    • Arthur de Araújo Farias's avatar
    • Arthur de Araújo Farias's avatar
      6f1af08b
    • Arthur de Araújo Farias's avatar
      Creating third-party source code directory · fdc52fac
      Arthur de Araújo Farias authored
      This is a common practice int a lot of C++ projects. With this we can ignore all code analysis of third-party repos at once by removing third-party repos root path. In this directory instead of using the source itself we use a git submodule for the repository of the third-party code we want to use. In this case, I removed googletest-release-1.7.0 from root repo path and placed a git submodule pointing to official google repository in github pointing to release 1.7.0.
      fdc52fac
    • Arthur de Araújo Farias's avatar
      Creating third-party source code directory · e5722c98
      Arthur de Araújo Farias authored
      This is a common practice int a lot of C++ projects.
      
      The goal of this structure is to reduce complexity by ignoring third-party directory from code analysis. All repos that resides in this subdirectory would be ingored. In this case I placed googletest inside it by linking a git submodule to google's official repository. Note that this solution could simplify the process of adding a new third party library just by creating a new submodule in this git repository and including the code in CMakeLists.txt.
      e5722c98
    • Arthur de Araújo Farias's avatar
      Creating third-party source code directory · 87fa681b
      Arthur de Araújo Farias authored
      This is a common practice int a lot of C++ projects.
      
      The goal of this structure is to reduce complexity by ignoring third-party directory from code analysis. All repos that resides in this subdirectory would be ingored. In this case I placed googletest inside it by linking a git submodule to google's official repository. Note that this solution could simplify the process of adding a new third party library just by creating a new submodule in this git repository and including the code in CMakeLists.txt.
      87fa681b
    • Arthur de Araújo Farias's avatar
      Creating third-party source code directory · 9468e4f5
      Arthur de Araújo Farias authored
      This is a common practice int a lot of C++ projects.
      
      The goal of this structure is to reduce complexity by ignoring third-party directory from code analysis. All repos that resides in this subdirectory would be ingored. In this case I placed googletest
      inside it by linking a git submodule to google's official repository. Note that this solution could simplify the process of adding a new third party library just by creating a new submodule in this git
      repository and including the code in CMakeLists.txt.
      9468e4f5