[CMake] Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Hi everyone, I'm trying to install rtl-sdr on my Linux, and i have this error during the compilation "Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)", i searched where the problem came from and apparently a function named find_package(PkgConfig) is called in CMakeLists.txt to find pkg-config, this function search with 2 modes, the first one being the module mode where the function go in the Modules repertory of CMake and catch the file named FindPkgConfig.cmake... I checked in this repertory and found no such file...I found a find with this name here https://github.com/Kitware/CMake/blob/master/Modules/FindPkgConfig.cmake but i put it in the Modules dir. but still the same error... I'm stuck there... Any suggestion ? Cheers Aurélien -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] CMake on OpenVMS - Apparent roadblock buried within cmake-3.3.2\Tests\CMakeLists.txt
Questions inline: On 10/28/2015 3:35 PM, Custin, Jay (CSC Sw Middleware) wrote: So the configuration/bootstrap script seems to blissfully get all the way to the end and even displays the following: - CMake has bootstrapped. Now run make. Except when I looked… it had not created the Makefile. I ran the same basic process on one of my Linux systems and noticed that in addition to NOT creating the Makefile… it also did not create the bin subdirectory. I tried simply adding the –trace option on the bootstrap’s cmake command (the last thing it does before posting the text above), but that didn’t seem to reveal any clues. I would love to simply comment out large swaths of the 3000+ lines of cmake-3.3.2\Tests\CMakeLists.txt but at this point I don’t have sufficient understanding of what impact doing this would have and fear that without the understanding doing so would probably do little to help me isolate where things appear to have gone awry. What makes you think there is a problem in Tests/CMakeLists.txt? Does anyone know where (specifically) I should investigate to determine where the Makefile itself should get generated? What files are generated in the build tree? The toplevel makefile is created here: void cmGlobalUnixMakefileGenerator3::WriteMainCMakefile() But there are lots of other files that get created. One thing you could try is to use the bootstrapped cmake to configure a more simple project. Something like: project(foo) add_library(foo foo.c) foo.c can be an empty file. Does the bootstrapped cmake work on that project? What about what triggers the creation of the bin folder? I would not worry about that yet. -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoff...@kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] CMake on OpenVMS - Apparent roadblock buried within cmake-3.3.2\Tests\CMakeLists.txt
I thought I had turned the final corner and only had the “home stretch” left to get to the finish line… and then a brick wall suddenly appeared to block my way… So the configuration/bootstrap script seems to blissfully get all the way to the end and even displays the following: - CMake has bootstrapped. Now run make. Except when I looked… it had not created the Makefile. I ran the same basic process on one of my Linux systems and noticed that in addition to NOT creating the Makefile… it also did not create the bin subdirectory. I tried simply adding the –trace option on the bootstrap’s cmake command (the last thing it does before posting the text above), but that didn’t seem to reveal any clues. I would love to simply comment out large swaths of the 3000+ lines of cmake-3.3.2\Tests\CMakeLists.txt but at this point I don’t have sufficient understanding of what impact doing this would have and fear that without the understanding doing so would probably do little to help me isolate where things appear to have gone awry. Does anyone know where (specifically) I should investigate to determine where the Makefile itself should get generated? What about what triggers the creation of the bin folder? Jay -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Colored diagnostic output for GCC 4.9 through Ninja
On Wed, Oct 28, 2015 at 11:20 AM, Robert Dailey
wrote:
> On Wed, Oct 28, 2015 at 11:19 AM, Robert Dailey
> wrote:
>> On Wed, Oct 28, 2015 at 9:03 AM, Miller Henry
>> wrote:
>>>
>>> I do something like this, which works for clang and should work for gcc 4.9
>>> though I haven't tested it. I haven't wrote the right way to do this
>>> which is to check if the terminal supports color before passing the flag
>>> in. I don't know what will happen on our e.g. CI system which doesn't
>>> support color.
>>>
>>> macro(AddCXXFlagIfSupported flag test)
>>>CHECK_CXX_COMPILER_FLAG(${flag} ${test})
>>>if( ${${test}} )
>>> message("adding ${flag}")
>>> set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${flag}")
>>>endif()
>>> endmacro()
>>>
>>> if("Ninja" STREQUAL ${CMAKE_GENERATOR})
>>>AddCXXFlagIfSupported(-fcolor-diagnostics
>>> COMPILER_SUPPORTS_fcolor-diagnostics)
>>> endif()
>>>
>>> P.s. AddCXXFlagIfSupported ought to be in the default cmake distribution
>>> along with a lot or similar things
>>
>> Unfortunately your solution doesn't seem to work. I get the following output:
>>
>> [1/1] Re-running CMake...
>> -- Performing Test COMPILER_SUPPORTS_fcolor-diagnostics
>> -- Performing Test COMPILER_SUPPORTS_fcolor-diagnostics - Failed
>>
>> GCC 4.9 supports this I thought?
>
> I found the issue, the flag is diagnostics-color, not color-diagnostics.
Actually, even after getting this working, I still get no color output. :-(
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Colored diagnostic output for GCC 4.9 through Ninja
On Wed, Oct 28, 2015 at 11:19 AM, Robert Dailey
wrote:
> On Wed, Oct 28, 2015 at 9:03 AM, Miller Henry
> wrote:
>>
>> I do something like this, which works for clang and should work for gcc 4.9
>> though I haven't tested it. I haven't wrote the right way to do this which
>> is to check if the terminal supports color before passing the flag in. I
>> don't know what will happen on our e.g. CI system which doesn't support
>> color.
>>
>> macro(AddCXXFlagIfSupported flag test)
>>CHECK_CXX_COMPILER_FLAG(${flag} ${test})
>>if( ${${test}} )
>> message("adding ${flag}")
>> set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${flag}")
>>endif()
>> endmacro()
>>
>> if("Ninja" STREQUAL ${CMAKE_GENERATOR})
>>AddCXXFlagIfSupported(-fcolor-diagnostics
>> COMPILER_SUPPORTS_fcolor-diagnostics)
>> endif()
>>
>> P.s. AddCXXFlagIfSupported ought to be in the default cmake distribution
>> along with a lot or similar things
>
> Unfortunately your solution doesn't seem to work. I get the following output:
>
> [1/1] Re-running CMake...
> -- Performing Test COMPILER_SUPPORTS_fcolor-diagnostics
> -- Performing Test COMPILER_SUPPORTS_fcolor-diagnostics - Failed
>
> GCC 4.9 supports this I thought?
I found the issue, the flag is diagnostics-color, not color-diagnostics.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Colored diagnostic output for GCC 4.9 through Ninja
On Wed, Oct 28, 2015 at 9:03 AM, Miller Henry wrote:
>
> I do something like this, which works for clang and should work for gcc 4.9
> though I haven't tested it. I haven't wrote the right way to do this which
> is to check if the terminal supports color before passing the flag in. I
> don't know what will happen on our e.g. CI system which doesn't support color.
>
> macro(AddCXXFlagIfSupported flag test)
>CHECK_CXX_COMPILER_FLAG(${flag} ${test})
>if( ${${test}} )
> message("adding ${flag}")
> set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${flag}")
>endif()
> endmacro()
>
> if("Ninja" STREQUAL ${CMAKE_GENERATOR})
>AddCXXFlagIfSupported(-fcolor-diagnostics
> COMPILER_SUPPORTS_fcolor-diagnostics)
> endif()
>
> P.s. AddCXXFlagIfSupported ought to be in the default cmake distribution
> along with a lot or similar things
Unfortunately your solution doesn't seem to work. I get the following output:
[1/1] Re-running CMake...
-- Performing Test COMPILER_SUPPORTS_fcolor-diagnostics
-- Performing Test COMPILER_SUPPORTS_fcolor-diagnostics - Failed
GCC 4.9 supports this I thought?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Colored diagnostic output for GCC 4.9 through Ninja
I do something like this, which works for clang and should work for gcc 4.9
though I haven't tested it. I haven't wrote the right way to do this which is
to check if the terminal supports color before passing the flag in. I don't
know what will happen on our e.g. CI system which doesn't support color.
macro(AddCXXFlagIfSupported flag test)
CHECK_CXX_COMPILER_FLAG(${flag} ${test})
if( ${${test}} )
message("adding ${flag}")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${flag}")
endif()
endmacro()
if("Ninja" STREQUAL ${CMAKE_GENERATOR})
AddCXXFlagIfSupported(-fcolor-diagnostics
COMPILER_SUPPORTS_fcolor-diagnostics)
endif()
P.s. AddCXXFlagIfSupported ought to be in the default cmake distribution along
with a lot or similar things
-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Robert Dailey
Sent: Wednesday, October 28, 2015 8:43 AM
To: CMake
Subject: [CMake] Colored diagnostic output for GCC 4.9 through Ninja
I'm using CMake + Ninja against GCC 4.9 in the Android NDK. I'm on Windows,
invoking 'ninja' through CMD.exe.
I do not see colored output for diagnostics (errors, warnings, etc) GCC gives.
Is there something in CMake I need to configure to enable colored output?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Colored diagnostic output for GCC 4.9 through Ninja
On Wed, Oct 28, 2015 at 6:43 AM, Robert Dailey wrote: > I'm using CMake + Ninja against GCC 4.9 in the Android NDK. I'm on > Windows, invoking 'ninja' through CMD.exe. > > I do not see colored output for diagnostics (errors, warnings, etc) > GCC gives. Is there something in CMake I need to configure to enable > colored output? Try adding -fdiagnostics-color=always to the compiler options. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] Colored diagnostic output for GCC 4.9 through Ninja
I'm using CMake + Ninja against GCC 4.9 in the Android NDK. I'm on Windows, invoking 'ninja' through CMD.exe. I do not see colored output for diagnostics (errors, warnings, etc) GCC gives. Is there something in CMake I need to configure to enable colored output? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
