From: Alan W. Irwin <irwin@be...> - 2013-03-28 20:34:29
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 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).
---------- Forwarded message ----------
Date: Thu, 28 Mar 2013 13:26:28 -0400
From: Jean-Christophe Fillion-Robin <jchris.fillionr@...>
To: Alan W. Irwin <irwin@...>
Cc: David Cole <dlrdave@...>, CMake ML <cmake@...>
Subject: Re: [CMake] CMakeModules repository at GitHub?
[reordered into a rational order]
On Thu, Mar 28, 2013 at 1:17 PM, Alan W. Irwin <irwin@...>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
> 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?
You could look at: https://github.com/davidsansome/python-cmake-buildsystem
More particularly this commit:
- Export targets from both the installed and build tree 
- Add generation of <PROJECT_NAME>Config.cmake 
This was based on the explanation of Alexander Neundorf. See
We should really update the following tutorial: