[Cmake-commits] CMake branch, master, updated. v3.11.0-rc4-341-gcf39c14

VERSION_MINOR 11) -set(CMake_VERSION_PATCH 20180327) +set(CMake_VERSION_PATCH 20180328) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] looking for 2 features to help pkg-config pc files

Dear Nikos, Thank you for concrete suggestion! Nikos Chantziaras wrote: > Is there a reason why you can't generate your .pc file from a .pc.in > file using the configure_file() function? Yes, that's what I'm doing now :-)

Re: [CMake] Listing all the include directories

Thanks Robert. Too bad that this something I cannot inspect. A list of include directories would be useful even with unexpanded generator expressions. CMake-server mode sounds like an interesting option. On Tue, Mar 27, 2018 at 10:47 AM Robert Maynard wrote: > In

Re: [CMake] looking for 2 features to help pkg-config pc files

On 2018-03-27 21:25+0300 Nikos Chantziaras wrote: Note that one downside to that is that people not using CMake cannot make use of that. They still need a pkgconfig file. So in a sense, pkgconfig is the common denominator everybody can use, regardless of build system. It is not an either-or

Re: [CMake] looking for 2 features to help pkg-config pc files

On 27/03/18 21:35, Rolf Eike Beer wrote: Am Dienstag, 27. März 2018, 21:25:51 schrieb Nikos Chantziaras: Note that one downside to that is that people not using CMake cannot make use of that. They still need a pkgconfig file. So in a sense, pkgconfig is the common denominator everybody can use,

Re: [CMake] looking for 2 features to help pkg-config pc files

Am Dienstag, 27. März 2018, 21:25:51 schrieb Nikos Chantziaras: > Note that one downside to that is that people not using CMake cannot > make use of that. They still need a pkgconfig file. So in a sense, > pkgconfig is the common denominator everybody can use, regardless of > build system. What

Re: [CMake] looking for 2 features to help pkg-config pc files

Note that one downside to that is that people not using CMake cannot make use of that. They still need a pkgconfig file. So in a sense, pkgconfig is the common denominator everybody can use, regardless of build system. On 27/03/18 20:36, Alan W. Irwin wrote: On 2018-03-27 21:19+0900 suzuki

Re: [CMake] looking for 2 features to help pkg-config pc files

On 2018-03-27 21:19+0900 suzuki toshiya wrote: Hi all, I'm looking for 2 features to generate pkg-config pc files. Hi Suzuki: CMake has its own native way of generating package information describing software (see, ). So

Re: [CMake] looking for 2 features to help pkg-config pc files

Is there a reason why you can't generate your .pc file from a .pc.in file using the configure_file() function? As in: configure_file( ${PROJECT_SOURCE_DIR}/mylibrary.pc.in ${PROJECT_BINARY_DIR}/mylibrary.pc @ONLY ) Your mylibrary.pc.in file would look something like this:

Re: [CMake] looking for 2 features to help pkg-config pc files

Dear Craig, Thank you for prompt reply. But all 3 functions; pkg_get_variable(), pkg_check_modules(), pkg_search_module() are different from my purpose. in my impression, these functions are designed to retrieve the infos from/via pkg-config, not to generate the infos to be written in pkg-

Re: [CMake] Listing all the include directories

In general your options are to look at the command line or use cmake-server mode to query the code model. The full set of include directories is not known while configuring due to generator expressions expanding after the configure step. On Mon, Mar 26, 2018 at 9:45 PM, Saad Khattak

Re: [CMake] looking for 2 features to help pkg-config pc files

You most likely want to use the FindPkgConfig module and also use the IMPORTED_TARGET option with the commands provided therein. On Tue, Mar 27, 2018 at 11:19 PM, suzuki toshiya wrote: > Hi all, > > I'm

[CMake] looking for 2 features to help pkg-config pc files

Hi all, I'm looking for 2 features to generate pkg-config pc files. I already wrote something, but some experts advised that there would be many people trying to do such, and there might be existing solution. If such functions are already included in cmake's official modules, please let me know.

[Cmake-commits] CMake branch, master, updated. v3.11.0-rc4-340-gd5f0b2d

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via d5f0b2df8eaa7d4d266ac43384e7aa91e19107e2 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.11.0-rc4-338-g760f83d

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 760f83d5c0d97359d1686ea4b56dabf2ac051a6d (commit) via

[Cmake-commits] CMake branch, release, updated. v3.11.0-rc4-6-g188c5c2

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 188c5c2a46173b0bcff928098fb406ad925fb3db (commit) via

[Cmake-commits] CMake branch, master, updated. v3.11.0-rc4-336-g99f3f6d

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 99f3f6d528fb9e7e05c1618675d4c998fce3dd59 (commit) via