Re: [CMake] Recommandations for public custom macro/functions installation

On Dienstag, 17. April 2018 13:48:39 CEST David Demelier wrote: > On Tue, 2018-04-17 at 12:25 +0200, Johannes Zarl-Zierl wrote: > > Just replying to this topic of your message: you may want to > > reconsider. The > > cmake gui allows you to group options automatically by prefix. This > >

Re: [CMake] Recommandations for public custom macro/functions installation

2018-04-17 11:58 GMT+02:00 David Demelier : > Hello, > > In my application I have some custom functions that help the process of > creating executable, libraries, plugins and such. > > They don't do magic things but they mostly build, provide installation > to specific place

Re: [CMake] Recommandations for public custom macro/functions installation

On Tue, Apr 17, 2018 at 9:48 PM, David Demelier wrote: > On Tue, 2018-04-17 at 12:25 +0200, Johannes Zarl-Zierl wrote: > > Just replying to this topic of your message: you may want to > > reconsider. The > > cmake gui allows you to group options automatically by prefix.

Re: [CMake] Recommandations for public custom macro/functions installation

On Tue, 2018-04-17 at 12:25 +0200, Johannes Zarl-Zierl wrote: > Just replying to this topic of your message: you may want to > reconsider. The > cmake gui allows you to group options automatically by prefix. This > de-clutters > the options considerably. I didn't know that! Nice catch. I'll

Re: [CMake] Recommandations for public custom macro/functions installation

Hi David, On Dienstag, 17. April 2018 11:58:12 CEST David Demelier wrote: > I personally do not want to prefix all my options in my project with > the project name prefix, I think that would be a bit ugly, and I do > want this macro to build and install the documentation. Just replying to this

[CMake] Recommandations for public custom macro/functions installation

Hello, In my application I have some custom functions that help the process of creating executable, libraries, plugins and such. They don't do magic things but they mostly build, provide installation to specific place and optionally build the documentation and install them as well. This happens