[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-618-g929352a

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 47ea9a8f3927ad605729400e812ca52560f9265f (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-593-g6cd8aa3

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 6cd8aa3c2a2fc6ecee9b8efea300b3b978660c35 (commit) from

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc2-617-g47ea9a8

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 1b4bc2f130f28fc4a5c9ed8464b467380749a0b5 (commit) discards

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc2-592-gf0f60c5

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-617-g47ea9a8

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-614-g2b1a230

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

Re: [CMake] Trying to get android toolchain setup for Crystax

Sorry last email: Assuming I get past the host tag issue, the next one is that the test program is unable to compile because: error: cannot find -lcrystax Somehow, somewhere the linker is expecting this library. I do not see it in the output from CMake when the build fails. I do know the file

Re: [CMake] Trying to get android toolchain setup for Crystax

Update: Using the x86_64 version of the Crystax NDK worked. Meaning, the directory name aligned with what CMake was expecting. However, the question now is: Why didn't changing CMAKE_ANDROID_NDK_TOOLCHAIN_HOST_TAG work? On Thu, Mar 23, 2017 at 3:14 PM, Robert Dailey

Re: [CMake] Trying to get android toolchain setup for Crystax

Sorry I guess it would help if I showed where the ANDROID_ variables are being defined: cmake .. -G"Ninja" -DCMAKE_BUILD_TYPE="Release" -DCMAKE_TOOLCHAIN_FILE="crystax.toolchain.cmake" -DBUILD_TESTING=OFF -DANDROID_API=15 -DANDROID_TOOLCHAIN_NAME=arm-linux-androideabi-4.9

[CMake] Trying to get android toolchain setup for Crystax

So I'm having no luck getting the Crystax NDK setup using built-in android support in CMake 3.8. I have the following toolchain file: set( CMAKE_SYSTEM_NAME Android ) set( CMAKE_SYSTEM_VERSION ${ANDROID_API} ) # set( CMAKE_ANDROID_NDK $ENV{ANDROID_NDK} ) set( CMAKE_ANDROID_NDK

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-609-ge527693

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-607-g299f570

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

Re: [cmake-developers] How to get install locations?

> One cmInstallTargetGenerator seems to install one file only and there > seems to be one per cmGeneratorTarget. Is that correct? How does the > installation of targets with multiple artifacts work? Just to clarify/muddy the waters. Once https://gitlab.kitware.com/cmake/cmake/merge_requests/574

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-605-gdd8f935

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

Re: [CMake] Include file in the Makefile

Thanks, Mike! HNG On Thu, Mar 23, 2017 at 12:59 PM, Michael Ellery wrote: > >> On Mar 22, 2017, at 2:07 PM, Hom Nath Gharti wrote: >> >> Dear all, >> >> I use PETSc in my package and I need to use the following line in my >> GNU Makefile: >> >>

Re: [cmake-developers] How to get install locations?

On 03/23/2017 11:37 AM, Tobias Hunger wrote: > cmInstallTargetGenerator has std::string GetDestination(std::string > const& config) const, too, which might have what I need. Unfortunately > that is not static, so I need to figure out how to get the right > instance of cmInstallTargetGenerator. >

Re: [cmake-developers] enable_language behavior change

On 03/23/2017 12:08 PM, Robert Dailey wrote: > Crystax NDK (on master branch) has a toolchain.cmake which invokes > enable_language() That is not something we expected to be done or intended to support. A toolchain file should configure information about the toolchain, not inject functionality

Re: [CMake] Include file in the Makefile

> On Mar 22, 2017, at 2:07 PM, Hom Nath Gharti wrote: > > 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?

Re: [cmake-developers] enable_language behavior change

On Thu, Mar 23, 2017 at 10:50 AM, Brad King wrote: > On 03/23/2017 11:35 AM, Robert Dailey wrote: >> Thanks Brad. For future reference, are these changes documented >> anywhere? I searched for "enable_language" in the 3.6 release notes, >> and there is no 3.6 entry for

Re: [cmake-developers] enable_language behavior change

On 03/23/2017 11:35 AM, Robert Dailey wrote: > Thanks Brad. For future reference, are these changes documented > anywhere? I searched for "enable_language" in the 3.6 release notes, > and there is no 3.6 entry for policy changes. The release notes are for new features, deprecations, and major

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-603-g08b2a3a

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 ab31b34c7f87f2703299f0e5af1fb3cec9fa39b5 (commit) discards

Re: [cmake-developers] enable_language behavior change

On Thu, Mar 23, 2017 at 10:33 AM, Brad King wrote: > On 03/23/2017 11:16 AM, Robert Dailey wrote: >> I remember around cmake v3.6, the behavior of enable_language() >> changed so that if you did it too many times, you'd get the error: >> >> Language 'C' is currently being

Re: [cmake-developers] enable_language behavior change

On 03/23/2017 11:16 AM, Robert Dailey wrote: > I remember around cmake v3.6, the behavior of enable_language() > changed so that if you did it too many times, you'd get the error: > > Language 'C' is currently being enabled. Recursive call not allowed. > > I need to implement some backward

Re: [cmake-developers] VS Project Settings User Defines

On 03/23/2017 11:15 AM, Wesley Smith wrote: > the solution here is to add something like the VS_GLOBAL_ > prefix or somehow attach custom flags to a target config > e.g. attach a flag to the Debug|x64 config of target X. Once could either try to add a property prefix like that or add dedicated

[cmake-developers] enable_language behavior change

I remember around cmake v3.6, the behavior of enable_language() changed so that if you did it too many times, you'd get the error: Language 'C' is currently being enabled. Recursive call not allowed. I need to implement some backward compatibility code to check of CMake version less than 3.6

Re: [cmake-developers] VS Project Settings User Defines

The only reference I've been able to find to this property is via the VisualStudio SDK https://msdn.microsoft.com/en-us/library/hh710870.aspx . It doesn't seem to be part of any compiler configuration. The conclusion here being that none of the flags in the VS tables map to this XML tag. I

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-603-gab31b34

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

Re: [cmake-developers] VS Project Settings User Defines

On 03/23/2017 10:41 AM, Wesley Smith wrote: > Specifically, I'm trying to add these tags: > > ..\..\add-in.ruleset > true > > per-config tags are added via Flag arguments, What are the corresponding command-line flags that these add? If they appear in `Source/cmVS*CLFlagTable.h` then adding

[cmake-developers] VS Project Settings User Defines

Hi, I'm trying to figure out if it's possible to add user defined XML entries to the project config section of a visual studio file. From what I can see it's not, but maybe someone here know of a code path I haven't come across. Specifically, I'm trying to add these tags: ..\..\add-in.ruleset

Re: [CMake] C# Language Detection Errors in 3.8.0-rc2

Eventually I figured out the answer to this question after stepping through the CMake project code. DO: enable_language(CSharp) DONT: enable_language(CSHARP) Unlike C, CXX, FORTRAN, etc. CSharp is not an abbreviation requiring capitalization of all letters. Case matters. On Thu, Mar 16, 2017

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-597-gb95ba9c

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 fcaf48bb9b9e64022a2b72819a3affd9e9b6ea11 (commit) discards

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc2-52-g324d7f5

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-594-gfcaf48b

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 528202e71179d9e7c3ce3029cb49b1fa0bb22132 (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-592-gf0f60c5

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

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

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 cb7f9893763ab2cab4a45d9ef1853e12b2480e76 (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-580-gcfa55fd

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

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

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 24c959a2b299b0152ed8c76d8b67cb5e37976ff1 (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-569-g922b777

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

Re: [CMake] libsndfile in windows

@Johannes Zarl-Zierl PFA . I found this link and tried how its mentioned in it . I was not able to successfully build it using this . Probably you could go though this and we could discuss. On Tue, Mar 21, 2017 at 6:52 PM, Johannes Zarl-Zierl < johannes.zarl-zi...@jku.at> wrote: > On Dienstag,