MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014095CMakeCMakepublic2013-04-17 09:452013-04-17 10:36
ReporterTom Rondeau 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusclosedResolutionwon't fix 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0014095: Add FindGnuradio.cmake file to installed cmake files
DescriptionI run the GNU Radio project, which uses cmake as it's configuration build tool. We have a FindGnuradio.cmake file that we would like to add to cmake's distribution to help us make it generally usable by out-of-tree builds (which are an important concept for the project).

I have attached the file in question. It allows us to set a list of GNU Radio components to search for and sets the include/library paths accordingly if found.

For the time being, we will install this as GnuradioConfig.cmake ourselves, but we'd like to see this as part of the larger cmake project, anyways.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files? FindGnuradio.cmake (4,159) 2013-04-17 09:45
https://public.kitware.com/Bug/file/4742/FindGnuradio.cmake
Issue History
Date ModifiedUsernameFieldChange
2013-04-17 09:45Tom RondeauNew Issue
2013-04-17 09:45Tom RondeauFile Added: FindGnuradio.cmake
2013-04-17 10:03Rolf Eike BeerNote Added: 0032890
2013-04-17 10:08Tom RondeauNote Added: 0032892
2013-04-17 10:32Rolf Eike BeerNote Added: 0032896
2013-04-17 10:32Rolf Eike BeerStatusnew => closed
2013-04-17 10:32Rolf Eike BeerResolutionopen => won't fix
2013-04-17 10:36Brad KingNote Added: 0032898

Notes
(0032890)
Rolf Eike Beer   
2013-04-17 10:03   
You got the concept in the wrong order ;) It's preferable for _you_ to install a *Config.cmake file instead of CMake to ship a Find*.cmake module. This way whoever has your development package installed can use your tool, regardless of which CMake version (well, sort of) he is using. And with your config file you can make sure everything is included, e.g. if you need additional external libs in the next release or whatever. A shipped find module is by design always behind such changes.
(0032892)
Tom Rondeau   
2013-04-17 10:08   
Yeah, that's what I thought you'd say. We just noticed that a lot of other projects have standard FindFoo.cmake files that you ship and thought that we could slip ours in as well.

Is there any structural difference between a FindGnuradio.cmake and a GnuradioConfig.cmake file? I couldn't find much info on this, in particular. Or is it just a different name so it can be found in the standard search paths?
(0032896)
Rolf Eike Beer   
2013-04-17 10:32   
No, the config files are different as you don't have to search anything in there. You generate them using install(EXPORT...) and probably some additional magic. Please ask on the CMake user mailinglist for details.

I'll close this bug now as we will not take your Find* module as you can do better ;)
(0032898)
Brad King   
2013-04-17 10:36   
For reference, see tutorials on package configuration files here:

 http://www.cmake.org/Wiki/CMake/Tutorials#CMake_Packages [^]

As Eike requested please ask on the user list for further help with them. You'll get a broader audience over there.