[CMake] can't locate library with find_library

hi all, I am running cmake 3 using EPEL install on RHEL 7. I also have installed "gflags", $rpm -ql gflags /usr/bin/gflags_completions.sh /usr/lib64/libgflags.so.2.1 /usr/lib64/libgflags_nothreads.so.2.1 /usr/share/doc/gflags-2.1.1 /usr/share/doc/gflags-2.1.1/AUTHORS.txt

Re: [CMake] can't locate library with find_library

On 22.03.2017 14:52, Oliver wrote: hi all, I am running cmake 3 using EPEL install on RHEL 7. I also have installed "gflags", $rpm -ql gflags /usr/bin/gflags_completions.sh /usr/lib64/libgflags.so.2.1 /usr/lib64/libgflags_nothreads.so.2.1 /usr/share/doc/gflags-2.1.1

Re: [CMake] can't locate library with find_library

oh, no, silly me, I didn't. that fixed the problem. thx Feiyi On Wed, Mar 22, 2017 at 10:08 AM, Nils Gladitz wrote: > On 22.03.2017 14:52, Oliver wrote: > >> hi all, >> >> I am running cmake 3 using EPEL install on RHEL 7. I also have installed >> "gflags", >> >> >> >>

[CMake] Include file in the Makefile

Dear all, I use PETSc in my package and I need to use the following line in my GNU Makefile: include ${PETSC_DIR}/lib/petsc/conf/variables What is the equivalent command for CMakeLists.txt for this? Thanks for your help. Thanks, HNG -- Powered by www.kitware.com Please keep messages

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-566-g9a733c7

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 9a733c7bd626f457a71632da46934995da7bbd4b (commit) via

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc2-35-g352b195

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 352b195f8769c5e4c884c1f9d0ba6d747d533547 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-570-g8725317

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, next has been updated discards fb79b7e3a94b17f9410cf71060230941c9a6e607 (commit) discards

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-566-gfb79b7e

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, next has been updated discards 61beaf2735aec3a10ce8806639785403b487974b (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-561-g61beaf2

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, next has been updated discards a16cf09e57105c0ccb3d86419b1daf72c3b0e6e2 (commit) discards

Re: [cmake-developers] Is it possible to clone an existing target?

Aliases for imported targets also would be useful. I found some old email threads, but seems they had not been implemented. On 22 March 2017 at 16:53, Stanislav Pankevich wrote: > Hi Brad, > > Thanks for the answer. > > Yes, I am going to write my own macro which, I hope,

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-561-ga16cf09

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, next has been updated discards ad1d900e9fe1013dbf0edf5c01ee9065892d72ed (commit) via

Re: [cmake-developers] Is it possible to clone an existing target?

Hi Brad, Thanks for the answer. Yes, I am going to write my own macro which, I hope, will do the job for the most cases. My use case is to generate the LLVM bitcode artefacts *.bc from existing CMake target instead of a binary that it would produce by default. Cloning existing target and then

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-562-gda802af

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 da802afd6e88d6cb4b562a816eee1f85e9ad1e8c (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-577-g606c1fc

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, next has been updated via 606c1fcdf87b319fe10f2ad100508b16f23a4e59 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-583-g4ea507d

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, next has been updated via 4ea507d989fed7a3bc8fa762419f4e8b13a0ea50 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-573-g377cd08

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, next has been updated via 377cd0876d8101934496d83ab86c06cd6b2ba246 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-581-g31004b5

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, next has been updated via 31004b59ed1dd444582ce5948ee151247ae3fb6c (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-585-g1c3e7cc

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, next has been updated via 1c3e7cc20f7f92d68264e2ec15c0f1d73eb2f15d (commit) via

Re: [cmake-developers] Debugging issues with enable_language(CSHARP)

Have you looked into https://github.com/Kitware/CMake/blob/master/Modules/CMakeDetermineCSharpCompiler.cmake ? Send steps to reproduce the problem you're seeing... Maybe somebody else here has encountered the same thing and worked through it already. HTH, David C. On Wed, Mar 22, 2017 at

Re: [cmake-developers] Debugging issues with enable_language(CSHARP)

Thanks David, I'll have a look at that. Here's my CMake script ``` cmake_minimum_required(VERSION 3.8.0) project(add-in) enable_language(CSHARP) ``` On Wed, Mar 22, 2017 at 9:58 AM, David Cole wrote: > Have you looked into >

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-587-g1b4bc2f

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, next has been updated discards 1c3e7cc20f7f92d68264e2ec15c0f1d73eb2f15d (commit) via

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc2-587-g1b4bc2f

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, nightly has been updated discards 6f5459e67de1d0f0ed40dd2abef86a295b52cd7f (commit) discards

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc2-566-g9a733c7

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, nightly-master has been updated via 9a733c7bd626f457a71632da46934995da7bbd4b (commit) via

Re: [cmake-developers] Debugging issues with enable_language(CSHARP)

So the answer is enable_language(CSHARP) should be enable_language(CSharp). -- 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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-567-g82db83d

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 82db83d2f143fa90c13be2a63fe0273e7e80bd09 (commit) from

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-588-g24c959a

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, next has been updated discards 1b4bc2f130f28fc4a5c9ed8464b467380749a0b5 (commit) discards

[cmake-developers] Is it possible to clone an existing target?

Hello, I have a target `MyTarget`. Is there a way I could do something like clone_target(MyTarget MyNewTarget) so that MyNewTarget appears to be the exact clone (deep copy) of original target with the only difference of a target name? P.S. I understand that complex projects may be the

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-551-g5379a6a

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, next has been updated via 5379a6a630d988cd12532413e98824fb462f (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-547-g10cbb87

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 10cbb87fa3a5f81dc9dedd24580a64e062047887 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-553-gc24b513

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, next has been updated discards ed2a6b4d93647fa6f997ecf8432aa065936d9da1 (commit) discards

Re: [cmake-developers] Is it possible to clone an existing target?

On 03/22/2017 03:30 AM, Stanislav Pankevich wrote: > I have a target `MyTarget`. Is there a way I could do something like > > clone_target(MyTarget MyNewTarget) > > so that MyNewTarget appears to be the exact clone (deep copy) > of original target with the only difference of a target name?

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-553-gcc58090

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, next has been updated discards 5379a6a630d988cd12532413e98824fb462f (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-525-g7ebbe4f

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 7ebbe4f9d853a5823ef47a13b53ef7e1f469bd2e (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-553-ged2a6b4

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, next has been updated discards cc58090bb01be9c687ae307201040e4d9f27ca23 (commit) discards

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-559-g6b86e36

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, next has been updated discards c24b513a06200b2f3ad73e7ce71cd805420bc1aa (commit) discards

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc2-31-g849f1ec

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 849f1ec1c07826973772599a55ad1736123b7708 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-553-g84a96aa

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 84a96aa0a57959f8552b4329d59329be6c645a4c (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-561-g10b21f0

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, next has been updated discards 6b86e3618662f1d559bd0b94899aaf81232a412d (commit) discards

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc2-33-g5b31104

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 5b311041f3c5b000137e6c52a9a0bba53146bc79 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-557-ge24ed7a

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 e24ed7ad870730304431f5cb09d90c980136639c (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-561-gad1d900

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, next has been updated discards 10b21f015010580ceef56d04935650658e7d7236 (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-559-g5d2f30f

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 5d2f30f5acbcf572a464f6f45fafaea23c7ae75a (commit) via