[cmake-developers] Exporting dependent library targets in multiple export sets

[Alexander Neundorf]

On Monday 17 September 2012, Alexander Neundorf wrote:
> On Monday 17 September 2012, Alexander Neundorf wrote:
> > On Monday 17 September 2012, Brad King wrote:
> > > On 09/15/2012 04:45 PM, Alexander Neundorf wrote:
> > > > There is now a branch export-sets-2 on cmake stage.
> > > > It cherry-picks a lot of the patches from
> > > > http://gitorious.org/~urkud1/cmake/urkud-cmake/commits/w/export-set,
> > > > mostly those from May, and then proceeds a bit differently.
> > > > 
> > > > In the end, cmake now checks whether a target which is missing in the
> > > > current export set has been exported and installed exactly once, gets
> > > > the correct name from that one installation (i.e. the used
> > > > namespace), and uses that.
> > > 
> > > That simple approach will allow us to move forward with this.  If
> > > anyone wants multiple exports of the same targets then they can add
> > > the explicit export set DEPENDS options later.
> > 
> > Cool.
> > The tests are not yet passing, I'll work on this.
> 
> The tests are passing now.
> 
> I had to change the order how the target files are included in the test, so
> that the required targets already exist when the other targets are set up.
> 
> I pushed that to stage too.
> 
> I think basically we're back to generating useful error messages again...


How about defining a variable which can be set by Config-files which holds an 
error message for the case that the Config-file has set <package>_FOUND to FALSE 
?
Like e.g. <package>_FIND_FAILURE_MESSAGE ?
This could then be printed by cmFindPackage and/or FPHSA ?

Alex