Skip to content
Snippets Groups Projects
  1. Jun 13, 2018
    • Jorrit Schaap's avatar
      Task #10079: manually copied parts of the QA package into LOFAR-Release-3_1.... · 8ee4d0c2
      Jorrit Schaap authored
      Task #10079: manually copied parts of the QA package into LOFAR-Release-3_1. This allows us to roll out a new LOFAR-Release-3_1 on the scu with an extra QA_Service. The QA_Service hardly depends on anything, and doesn't require modifications to the rest of the lofar code. This makes this unusual manual merge acceptable. The rest of the QA code is not part of this release, and is not merged to this branch (yet). It runs isolated in docker containers on cep4.
      8ee4d0c2
  2. Feb 03, 2016
  3. May 20, 2015
  4. Aug 26, 2014
  5. Sep 30, 2013
  6. May 15, 2013
  7. May 14, 2013
  8. Jan 07, 2011
  9. Jan 06, 2011
  10. Mar 29, 2010
  11. Nov 24, 2009
  12. Nov 17, 2009
  13. Nov 11, 2009
    • Marcel Loose's avatar
      Bug 1395: · 808316b1
      Marcel Loose authored
      * Merged changes on the branch into the trunk (again, sigh!). 
      * Fixed RPATH install problem. 
      * Removed SubSystems and its subdirectories as LOFAR packages.
      808316b1
  14. Oct 16, 2009
  15. Oct 09, 2009
  16. Oct 07, 2009
    • Marcel Loose's avatar
      Bug 1310: · 1ce7c167
      Marcel Loose authored
      - New lofar_package() macro replaces lofar_add_package(). The new macro
        supports recursive addition of LOFAR packages, using the dependencies passed
        as arguments. For example: 
          lofar_package(Blob 1.0 DEPENDS Common) 
        will add the package Common to the build (unless it was already added).
        This new features enables a "top-down" package specification order, which is
        required for building subsystems.
      
      - New lofar_add_package() macro replaces lofar_add_subdirectory(). This macro
        uses a ${pkg}_SOURCE_DIR variable to locate the source directory of the
        package <pkg>. This information is needed, as we cannot simply include
        actual subdirectories anymore, because dependent package(s) might be located
        in a different directory tree.
      
      - New file LofarPackageList.cmake, which sets the ${pkg}_SOURCE_DIR variables.
        This file is generated by a script gen_LofarPackageList_cmake.sh, which must
        be rerun when LOFAR packages are added, moved, or removed.
      1ce7c167
  17. Aug 14, 2009
  18. Jun 24, 2009
  19. Jun 17, 2009
  20. Jun 16, 2009
  21. Mar 11, 2009
  22. Mar 06, 2009
  23. Jun 20, 2008
  24. Jun 19, 2008
  25. Jun 16, 2008
Loading