I think we should incorporate the subject-line idea into the PLplot build system which would make it more convenient for other CMake-based build systems (e.g., that for the PLplot installed examples or the external te_gen project) to find the installed PLplot headers and libraries. Because I don't have time to implement this idea at the moment I preserve below the relevant parts of a thread that occurred on the CMake mailing list about this idea.
Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ---------- Forwarded message ---------- Date: Thu, 28 Mar 2013 13:26:28 -0400 From: Jean-Christophe Fillion-Robin <jchris.filli...@kitware.com> To: Alan W. Irwin <ir...@beluga.phys.uvic.ca> Cc: David Cole <dlrd...@aol.com>, CMake ML <cm...@cmake.org> Subject: Re: [CMake] CMakeModules repository at GitHub? [reordered into a rational order] On Thu, Mar 28, 2013 at 1:17 PM, Alan W. Irwin <ir...@beluga.phys.uvic.ca>wrote: > On 2013-03-28 12:25-0400 David Cole wrote: > > CMake needs no new Find modules. >> >> All projects should provide a "project config file .cmake script" >> readable by CMake's find_package, and installed in a location where CMake >> can find it, so that a CMake find module is completely unnecessary. >> > > Hi David: > > Your idea sounds like a good one, but can you recommend an easily > understood > project that follows this approach that would serve as a good template > for build-system developers to use when implementing this approach for > their own projects? > > Alan Hi Alan, You could look at: https://github.com/davidsansome/python-cmake-buildsystem More particularly this commit: - Export targets from both the installed and build tree [1] - Add generation of <PROJECT_NAME>Config.cmake [2] [1] https://github.com/davidsansome/python-cmake-buildsystem/commit/73134d77881ae6648a8f98daaf8630130b7f54ea [2] https://github.com/davidsansome/python-cmake-buildsystem/commit/3f504d8be5b41086f615494517ddd2cf66f4d365 This was based on the explanation of Alexander Neundorf. See http://www.cmake.org/pipermail/cmake/2013-February/053689.html We should really update the following tutorial: http://www.cmake.org/Wiki/CMake/Tutorials/How_to_create_a_ProjectConfig.cmake_file [...] ------------------------------------------------------------------------------ Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
