Skip to content
Snippets Groups Projects
  1. Jun 19, 2017
  2. Jun 06, 2017
  3. Jun 01, 2017
  4. May 30, 2017
  5. May 24, 2017
  6. May 18, 2017
  7. May 17, 2017
  8. May 16, 2017
  9. May 11, 2017
  10. May 08, 2017
  11. Apr 25, 2017
  12. Apr 20, 2017
  13. Apr 19, 2017
  14. Apr 07, 2017
  15. Apr 04, 2017
  16. Apr 03, 2017
  17. Mar 31, 2017
  18. Mar 30, 2017
  19. Mar 28, 2017
  20. Mar 21, 2017
  21. Mar 20, 2017
  22. Mar 17, 2017
  23. Mar 13, 2017
  24. Mar 07, 2017
  25. Mar 06, 2017
  26. Feb 24, 2017
  27. Feb 21, 2017
    • Marcel Loose's avatar
      Task #3014: Reintroduced the current directory (.) to BASE_SEARCH_DIR. · 39b9fad8
      Marcel Loose authored
      There's a good reason for doing this, because some things have changed in the
      meantime:
      - Binaries are now always built in <CMAKE_BINARY_DIR>/bin.
      - Configuration files are now always symlinked in <CMAKE_BINARY_DIR>/etc
      
      The ConfigLocator searches the following default locations:
        ${LOFARROOT}, ${LOFARROOT}/etc, /opt/lofar, /opt/lofar/etc
      
      If it doesn't find the configuration file in any of these directories, it will
      also search the following directories:
        <BIN_DIR>, <BIN_DIR>/etc, <BIN_DIR>/.., <BIN_DIR>/../etc,
      where <BIN_DIR> is the directory containing the executable.
      
      And here's the problem. In the old days, the binary would be somewhere in the
      build tree, in a location similar to its source. But now it's in
      <CMAKE_BINARY_DIR>/bin. The extended search rule above will *always* find the
      configuration file in <CMAKE_BINARY_DIR>/etc; there's no way you can override
      this anymore. (Well, you could use the very dirty hack to redefine LOFARROOT
      in your test, but that's plain ugly.)
      
      So, by reintroducing the current directory in BASE_SEARCH_DIR, we now have
      again the option to use a different configuration file for testing.
      39b9fad8
Loading