Re: [CMake] CMake 3.7.1 gui fails to launch

On 2017-01-06 12:41-0500 da...@daryllee.com wrote: As it turns out, no, I can't use Qt5. In fact, I'd love to hear from anyone who actually has. My "ldd -r" results for cmake-gui show my recent bootstrap builds (of cmake-3.7.0) have been built with Qt5 without linking issues. I didn't do

Re: [CMake] CMake 3.7.1 gui fails to launch

ersion 4.8.6) with $ sudo apt-get install libqt4-core libqt4-dev libqt4-gui qt4-dev-tools I installed cmake $ ./bootstrap & make & sudo make install all seemed to run without issue. Running "cmake-gui --version" reported version 3.7.1, but running "cmake-gui" fai

Re: [CMake] CMake 3.7.1 gui fails to launch

Hi, On Fri, Jan 6, 2017 at 4:41 PM, <da...@daryllee.com> wrote: > CMake suite maintained and supported by Kitware (kitware.com/cmake). > daryl@eve-ldb:~/cmake/cmake-3.7.1$ cmake-gui > cmake-gui: symbol lookup error: cmake-gui: undefined symbol: > _ZN9QListDat

Re: [CMake] CMake 3.7.1 gui fails to launch

Hm...18:52, 6 january 2017 г., David Cole via CMake <cmake@cmake.org>:Can you use Qt5? CMake 3.7 is typically built using Qt5: perhaps a Qt5**requirement** has crept in since it's the commonly used one now.It's work for me with RedHat and Qt 4.8.6.No problem cmake-gui work.HTH,David C.On Fr

Re: [CMake] CMake 3.7.1 gui fails to launch

o run without issue. Running "cmake-gui --version" reported > version 3.7.1, but running "cmake-gui" failed: > > = > daryl@eve-ldb:~/cmake/cmake-3.7.1$ cmake-gui --version > cmake version 3.7.1 > > CMake suite maintained and supported by Kitware (kitware.

[CMake] CMake 3.7.1 gui fails to launch

all all seemed to run without issue. Running "cmake-gui --version" reported version 3.7.1, but running "cmake-gui" failed: ===== daryl@eve-ldb:~/cmake/cmake-3.7.1$ cmake-gui --version cmake version 3.7.1 CMake suite maintained and supported by Kitware (kitware.com/c

[CMake] CMake project with fpp preprocessed Fortran source file failed

Hi, I'm trying to use fpp preprocessor in a Fortran project built with CMake. For example, I have two source files. The file x.f90 defines module x: module x #ifdef ENABLE_Z use z #endif implicit none end module x The module z used in module x is defined in z.f90 as followed: module z

Re: [CMake] cmake vs. Python 3.4

Yes. That did the trick. Sorry for the noise. On 23 Dec 2016 23:52, "Dan Liew" wrote: > > > On 23 Dec 2016 7:58 pm, "Lev" wrote: > > Hi list, > > > I have this: > > FIND_PACKAGE(PythonInterp) > > and cmake finds this: > > -- Found PythonInterp:

Re: [CMake] cmake vs. Python 3.4

Am Samstag, 24. Dezember 2016, 12:06:10 schrieb Rolf Eike Beer: > Am Freitag, 23. Dezember 2016, 20:57:49 schrieb Lev: > > Hi list, > > > > > > I have this: > > > > FIND_PACKAGE(PythonInterp) > > > > and cmake finds this: > > > > -- Found PythonInterp: /usr/bin/python (found version "2.7.9")

Re: [CMake] cmake vs. Python 3.4

Am Freitag, 23. Dezember 2016, 20:57:49 schrieb Lev: > Hi list, > > > I have this: > > FIND_PACKAGE(PythonInterp) > > and cmake finds this: > > -- Found PythonInterp: /usr/bin/python (found version "2.7.9") > > However, 3.4 is also installed. How can I specify to find 3.4? > > If I say: >

Re: [CMake] cmake vs. Python 3.4

On 23 Dec 2016 7:58 pm, "Lev" wrote: Hi list, I have this: FIND_PACKAGE(PythonInterp) and cmake finds this: -- Found PythonInterp: /usr/bin/python (found version "2.7.9") However, 3.4 is also installed. How can I specify to find 3.4? If I say:

Re: [CMake] cmake vs. Python 3.4

> > Try using the update-alternatives command so that "python" becomes > symbolically linked to python-3.4 rather than python-2.7.9 > > Or uninstall python 2.7.9. > The standard Python distribution for versions 3 or greater installs a binary called `python3`, not `python`. That is the standard.

Re: [CMake] cmake vs. Python 3.4

On Fri, 23 Dec 2016 12:53:30 -0800 (PST) "Alan W. Irwin" wrote: > Try using the update-alternatives command so that "python" becomes > symbolically linked to python-3.4 rather than python-2.7.9 > > Or uninstall python 2.7.9. Ok. Thanks both of you. Merry XMAS,

Re: [CMake] cmake vs. Python 3.4

On Friday, December 23, 2016 12:53:30 PM Alan W. Irwin wrote: > On 2016-12-23 20:57+0100 Lev wrote: > > Hi list, > > > > > > I have this: > > > > FIND_PACKAGE(PythonInterp) > > > > and cmake finds this: > > > > -- Found PythonInterp: /usr/bin/python (found version "2.7.9") > > > > However,

Re: [CMake] cmake vs. Python 3.4

On 23/12/16 20:53, Alan W. Irwin wrote: On 2016-12-23 20:57+0100 Lev wrote: Hi list, I have this: FIND_PACKAGE(PythonInterp) and cmake finds this: -- Found PythonInterp: /usr/bin/python (found version "2.7.9") However, 3.4 is also installed. How can I specify to find 3.4? If I say:

Re: [CMake] cmake vs. Python 3.4

On 2016-12-23 20:57+0100 Lev wrote: Hi list, I have this: FIND_PACKAGE(PythonInterp) and cmake finds this: -- Found PythonInterp: /usr/bin/python (found version "2.7.9") However, 3.4 is also installed. How can I specify to find 3.4? If I say: set(Python_ADDITIONAL_VERSIONS 3.4)

[CMake] cmake vs. Python 3.4

Hi list, I have this: FIND_PACKAGE(PythonInterp) and cmake finds this: -- Found PythonInterp: /usr/bin/python (found version "2.7.9") However, 3.4 is also installed. How can I specify to find 3.4? If I say: set(Python_ADDITIONAL_VERSIONS 3.4) FIND_PACKAGE(PythonInterp 3 REQUIRED) still no

Re: [CMake] Cmake

Hi Aishwarya, On 21 December 2016 at 11:51, aishwarya selvaraj wrote: > Hi Everyone, > Myself Aishwarya .I wanted to make use of Cmake , but I'm really new to this > and doesn't have a clear idea about it. > > 1) My Goal : > I'm using Praat a speech Processing

Re: [CMake] Cmake

to this: target_link_libraries(tsm armadillo lidsndfile) best regards, Michael From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of aishwarya selvaraj Sent: Wednesday, December 21, 2016 12:52 PM To: cmake@cmake.org Subject: [CMake] Cmake Hi Everyone, Myself Aishwarya .I wanted to make use of Cmake , but I'm really new

[CMake] Cmake

Hi Everyone, Myself Aishwarya .I wanted to make use of Cmake , but I'm really new to this and doesn't have a clear idea about it. 1) *My Goal :* I'm using Praat a speech Processing Software to create plug - in for my Algorithm on Pitch and Time scaling .(I have the .cpp file) In order to do that

Re: [CMake] CMake 3.7.0-r2 Open Project sometimes picks wrong version of Visual Studio

On Tue, Nov 8, 2016 at 10:28 AM, wrote: > > > - On Nov 8, 2016, at 8:13 AM, Taylor Braun-Jones tay...@braun-jones.org > wrote: > >> On Fri, Nov 4, 2016 at 2:55 PM, Brad King wrote: >>> >>> On 11/03/2016 06:04 PM, John Drescher wrote: >>> > I

Re: [CMake] CMake, VS, Nsight Tegra, NDK, mixed C/C++ - applies C++ options to C source

I suspect that if the first source in a target is C++, every source in that targets gets CMAKE_CXX_FLAGS, otherwise CMAKE_C_FLAGS. So for now, mixing C and C++ sources in the same target is broken. I worked around this issue by putting C sources in their own static library, and linking that into

Re: [CMake] CMake, VS, Nsight Tegra, NDK, mixed C/C++ - applies C++ options to C source

I'm pretty sure that the toolchain bundled with the NDK, made by Google, hasn't been tested with other generators than Ninja or possibly Make. Also, there are some known bugs with it, including the one related to CMAKE_CXX_STANDARD (see https://code.google.com/p/android/issues/detail?id=227915

[CMake] CMake, VS, Nsight Tegra, NDK, mixed C/C++ - applies C++ options to C source

We have a large project library of mostly C++, mixed with a handful of C. The C++ compilation commands look correct and work fine. But C files are passed to clang++.exe -x c, rather than clang.exe. Which should work, except that CMAKE_CXX_FLAGS is applied while CMAKE_C_FLAGS is ignored.

Re: [CMake] [cmake-developers] C++11/C++14 doesn't work in check_cxx_source_compiles

On 11/24/2016 01:43 PM, Roman Wüger wrote: > Shouldn't this be done by CMAKE_CXX_STANDARD? Yes, this is a known problem with try_compile. It needs to learn to honor the CMAKE__STANDARD. CMake itself works around this problem in some cases, e.g. * https://gitlab.kitware.com/cmake/cmake/b

Re: [CMake] [cmake-developers] C++11/C++14 doesn't work in check_cxx_source_compiles

> CMAKE_CXX_EXTENSIONS don't get passed through. So it looks like, at the > moment, you would have to manually pass through the relevant compiler and > linker flags to get sources built via try_compile() and therefore via > check_cxx_source_compiles(). I've recorded a new issue > <

Re: [CMake] [cmake-developers] C++11/C++14 doesn't work in check_cxx_source_compiles

get passed through. So it looks like, at the moment, you would have to manually pass through the relevant compiler and linker flags to get sources built via try_compile() and therefore via check_cxx_source_compiles(). I've recorded a new issue <https://gitlab.kitware.com/cmake/cmake/issues/16

Re: [CMake] [cmake-developers] C++11/C++14 doesn't work in check_cxx_source_compiles

but it does not set/add the required library > Am 24.11.2016 um 22:01 schrieb Craig Scott : > > You might also need to set CMAKE_CXX_EXTENSIONS to OFF (it's ON by default). > This controls which c++ library is linked for some compilers, with clang and > gcc being two

Re: [CMake] [cmake-developers] C++11/C++14 doesn't work in check_cxx_source_compiles

You might also need to set CMAKE_CXX_EXTENSIONS to OFF (it's ON by default). This controls which c++ library is linked for some compilers, with clang and gcc being two cases where it does this. You may also find this article

Re: [CMake] [cmake-developers] C++11/C++14 doesn't work in check_cxx_source_compiles

It is working now, after I added -lc++ to CMAKE_REQUIRED_LIBRARIES before the check_cxx_source_compiles() call. Shouldn't this be done by CMAKE_CXX_STANDARD? Best Regards Roman > Am 24.11.2016 um 19:08 schrieb Roman Wüger : > > Hello, > > If I use a small piece of code

[CMake] CMake and Code Signing in XCode 8 for iOS projects

Hi all, CMake was able to configure automatic code signing for XCode <=7 and iOS projects with a target property setting like set_target_properties(app PROPERTIES XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "PROPER IDENTIFIER") XCode 8 changed the signing process. It now is required that the option

[CMake] CMake Project Generation Speedup

Hi all, We are still in the process of switching our large Make-based build to CMake. One of the issues we're running into is the time it takes to reparse and regenerate the CMake project (whether ninja, VS, or make) after touching any CMake file. To give you an idea, we have about 1000 targets

Re: [CMake] CMake 3.7: Test #379: RunCMake.CPack_RPM fails

2016-11-15 15:16 GMT+01:00 Christoph Grüninger : > Hi Domen, > thanks for your answer. > > > > CMake 3.7 compiles so far, but test #379 (RunCMake.CPack_RPM) fails, > see > > > the error below from OBS. I had a brief look at our patches and I am > apt > > > to think they are

Re: [CMake] CMake 3.7: Test #379: RunCMake.CPack_RPM fails

Hi Domen, thanks for your answer. > > CMake 3.7 compiles so far, but test #379 (RunCMake.CPack_RPM) fails, see > > the error below from OBS. I had a brief look at our patches and I am apt > > to think they are unrelated. > > Can someone have a look and give some hint? > > > I'll test it today

Re: [CMake] CMake 3.7: Test #379: RunCMake.CPack_RPM fails

2016-11-12 14:38 GMT+01:00 Christoph Grüninger : > Dear CMake folks, > I am trying to package CMake for openSuse. I was a bit surprised that > the new dependency libuv was nowhere mentioned. Can it be disabled by a > configure switch for older systems? > If I remember

[CMake] CMake 3.7: Test #379: RunCMake.CPack_RPM fails

Dear CMake folks, I am trying to package CMake for openSuse. I was a bit surprised that the new dependency libuv was nowhere mentioned. Can it be disabled by a configure switch for older systems? CMake 3.7 compiles so far, but test #379 (RunCMake.CPack_RPM) fails, see the error below from OBS. I

Re: [CMake] CMake 3.7.0-r2 Open Project sometimes picks wrong version of Visual Studio

S2013 .sln file? > >> The feature is new in 3.7 and was contributed here: >> >> cmake-gui: Add button to open the generated project >> https://gitlab.kitware.com/cmake/cmake/commit/1ca2d5d1 >> >> I'm not particularly familiar with how it works, but from a qu

Re: [CMake] CMake 3.7.0-r2 Open Project sometimes picks wrong version of Visual Studio

ed here: > > cmake-gui: Add button to open the generated project > https://gitlab.kitware.com/cmake/cmake/commit/1ca2d5d1 > > I'm not particularly familiar with how it works, but from a quick > glance at the code it may be using file associations. Yes, it's just using Window

Re: [CMake] CMake 3.6 and OSX

Hello, On 02/11/2016 06:01, Robert Ramey wrote: > Here is what I'm seeing: > > a) it looks like CMake is looking for boost_filesystem rather than > libboost as I expect. (same for system). > > b) even if I tweak findBoost to force the system to look for libboost... > it still fails > > b) If I

Re: [CMake] CMake 3.7.0-r2 Open Project sometimes picks wrong version of Visual Studio

orrect ide? The feature is new in 3.7 and was contributed here: cmake-gui: Add button to open the generated project https://gitlab.kitware.com/cmake/cmake/commit/1ca2d5d1 I'm not particularly familiar with how it works, but from a quick glance at the code it may be using file associations. If

[CMake] CMake 3.7.0-r2 Open Project sometimes picks wrong version of Visual Studio

I opened a project in cmake-gui using the open project button from a vc 2010 build of a project. The open project opened the project in Visual Studio 2010. Later I opened the same project but a different build tree for Visual Studio 2013 CMake-gui had all of the correct information for the Visual

Re: [CMake] CMake 3.6 and OSX

Thanks for your help. I've managed to get past the original problem by editing FindBoost so that it checks for version 1.62. But I'm done yet! Now I'm getting compiler is AppleClang compiler is AppleClang [ /Applications/CMake.app/Contents/share/cmake-3.6/Modules/FindBoost.cmake:960 ]

Re: [cmake-developers] [CMake] CMake integration in Gradle (Android Studio)

I have got many compliant that cmake support is not work with even the new Android Studio, but it is really works for me. I try ldd on cmake which Android SDK provided, all the so is resolved correct, which break before. So, I can imagine that maybe something related to my host environment , I

Re: [CMake] CMake integration in Gradle (Android Studio)

I have got many compliant that cmake support is not work with even the new Android Studio, but it is really works for me. I try ldd on cmake which Android SDK provided, all the so is resolved correct, which break before. So, I can imagine that maybe something related to my host environment , I

Re: [CMake] [cmake-developers] CMake integration in Gradle (Android Studio)

It's my experience which maybe help. I love Android Studio for its jetbrains style coding experience, but with some bad style I don't like, like so frequency update and so many experiment feature which sometimes is a good part like CMake support! I just love coding and focus my project, but the

Re: [cmake-developers] [CMake] CMake integration in Gradle (Android Studio)

My Android Studio Version Info: Android Studio 2.2.1 Build #AI-145.3330264, built on October 6, 2016 May be the more import part is cmake version, I have two which all works: ~/Android/Sdk/cmake/3.6.3155560 ~/Android/Sdk/cmake/3.6.3133135 hope this will be help:) 2016-10-31 22:13 GMT+08:00

Re: [CMake] CMake integration in Gradle (Android Studio)

My Android Studio Version Info: Android Studio 2.2.1 Build #AI-145.3330264, built on October 6, 2016 May be the more import part is cmake version, I have two which all works: ~/Android/Sdk/cmake/3.6.3155560 ~/Android/Sdk/cmake/3.6.3133135 hope this will be help:) 2016-10-31 22:13 GMT+08:00

Re: [CMake] [cmake-developers] CMake integration in Gradle (Android Studio)

Florent, I had the same thoughts. It seems that the CMake generate + build step happen silently as a prerequisite step when doing the 'gradle build' command somewhere. It makes it appear as if CMake is not running at all, but instead the Java piece of the build is just taking forever. Really I

Re: [cmake-developers] [CMake] CMake integration in Gradle (Android Studio)

So I have been using (a custom) CMake + Android Studio/Gradle for some years now. I only recently saw that both official CMake is adding Android support, and that the official Android tools are supporting CMake. I’m actually still confused on the differences between the two and what each offers in

Re: [CMake] CMake integration in Gradle (Android Studio)

So I have been using (a custom) CMake + Android Studio/Gradle for some years now. I only recently saw that both official CMake is adding Android support, and that the official Android tools are supporting CMake. I’m actually still confused on the differences between the two and what each offers in

Re: [cmake-developers] [CMake] CMake integration in Gradle (Android Studio)

I'm sorry but that doesn't really answer my questions. On Mon, Oct 31, 2016 at 8:55 AM, Cong Monkey wrote: > Try to update your Android SDK from android studio? > > > 2016年10月31日 21:31，"Robert Dailey" 写道： > > Which version of Android Studio?

Re: [CMake] CMake integration in Gradle (Android Studio)

I'm sorry but that doesn't really answer my questions. On Mon, Oct 31, 2016 at 8:55 AM, Cong Monkey wrote: > Try to update your Android SDK from android studio? > > > 2016年10月31日 21:31，"Robert Dailey" 写道： > > Which version of Android Studio?

Re: [CMake] CMake integration in Gradle (Android Studio)

Try to update your Android SDK from android studio? 2016年10月31日 21:31，"Robert Dailey" 写道： Which version of Android Studio? Latest stable is 2.2 IIRC. Are you talking about dev/beta builds? On Sun, Oct 30, 2016 at 9:04 AM, Cong Monkey wrote: >

Re: [cmake-developers] [CMake] CMake integration in Gradle (Android Studio)

Try to update your Android SDK from android studio? 2016年10月31日 21:31，"Robert Dailey" 写道： Which version of Android Studio? Latest stable is 2.2 IIRC. Are you talking about dev/beta builds? On Sun, Oct 30, 2016 at 9:04 AM, Cong Monkey wrote: >

Re: [cmake-developers] [CMake] CMake integration in Gradle (Android Studio)

Which version of Android Studio? Latest stable is 2.2 IIRC. Are you talking about dev/beta builds? On Sun, Oct 30, 2016 at 9:04 AM, Cong Monkey wrote: > The latest release of android studio work with CMAKE well. > > you can create a new project with c++ support to test

Re: [CMake] CMake integration in Gradle (Android Studio)

Which version of Android Studio? Latest stable is 2.2 IIRC. Are you talking about dev/beta builds? On Sun, Oct 30, 2016 at 9:04 AM, Cong Monkey wrote: > The latest release of android studio work with CMAKE well. > > you can create a new project with c++ support to test

Re: [CMake] CMake 3.6 and OSX

Hello Robert, On 29/10/2016 22:03, Robert Ramey wrote: > I've just "upgraded" to version 3.6 of CMake. I'm using Xcode with the > clang compiler. Now when I'm trying to configure a project I'm getting: > > The C compiler identification is unknown > The CXX compiler identification is unknown >

Re: [CMake] CMake integration in Gradle (Android Studio)

The latest release of android studio work with CMAKE well. you can create a new project with c++ support to test CMAKE support! You can follow https://code.google.com/p/android/issues/detail?id=212007 to get the details. 2016-10-28 5:48 GMT+08:00 Robert Dailey : > I'm

[CMake] CMake 3.6 and OSX

I've just "upgraded" to version 3.6 of CMake. I'm using Xcode with the clang compiler. Now when I'm trying to configure a project I'm getting: The C compiler identification is unknown The CXX compiler identification is unknown CMake Error at CMakeLists.txt:14 (project): No CMAKE_C_COMPILER

Re: [CMake] CMake integration in Gradle (Android Studio)

I'm at a bit of a loss on finding more information. Can anyone at least confirm that this isn't a reliable place to find the answers I'm looking for? Does anyone have real experience with android + gradle + cmake integration and can provide some pointers? On Tue, Oct 25, 2016 at 8:48 AM, Robert

Re: [CMake] [cmake-developers] iwyu and clang-tidy not working under mac os

Ok, I've got it. If anyone is interested, here is my configuration: find_program(iwyu_path NAMES include-what-you-use iwyu PATHS ${CMAKE_SOURCE_DIR}/tools/include-what-you-use/${iwyu_os}/bin) if(NOT iwyu_path) message(STATUS "Program include-what-you-use: Not found") else() message(STATUS

Re: [CMake] cmake - ified libjpeg source code

On Tue, 25 Oct 2016, Aaron Boxer wrote: > Hello, > > I am looking for a cmake-ified jpeg library to add to another cmake project. > Any recommendations? I get mine here: https://phabricator.kde.org/diffusion/EMERGE/browse/master/portage/win32libs/jpeg/ -- Boudewijn Rempt |

[CMake] cmake - ified libjpeg source code

Hello, I am looking for a cmake-ified jpeg library to add to another cmake project. Any recommendations? Thanks, Aaron -- 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] CMake integration in Gradle (Android Studio)

I'm not sure if the CMake mailing lists are the right place to ask this question but I thought I'd ask just in case someone has gone down this path or has experience with what Google/Gradle is actually trying to accomplish with what seems to be a hand-built version of CMake with custom patches

[CMake] Cmake not using user configured lib for linking

I am using cmake (3.5.0) to compile a C++ probject on Ubuntu 14.04, which depends on Nvidia Cudnn. It seems that the cmake does not provide the correct paths of cudnn to the linker although I have configured the paths. File FindCUDNN.cmake: FIND_PATH(CUDNN_INCLUDE_DIR NAME "cudnn.h" PATHS

[CMake] cmake 3.6.2 FindHDF5.cmake trouble finding parallel version

Hi, I'm experiencing troubles with cmake 3.6.2 and FindHDF5.cmake module in Debian/Testing. I'm trying to build med-fichier and gmsh for instance. The main CMakeList.txt contains: find_package(HDF5 COMPONENTS C) MESSAGE("HDF5_C_INCLUDE_DIR=${HDF5_C_INCLUDE_DIR}")

Re: [CMake] cmake doesn't find QtCore

Hi, what is your compiler? HS Am 18. Oktober 2016 02:07:35 MESZ, schrieb Spencer Parkin : >Hi, > >I'm trying to install PySide. With "pip install PySide", I get the >warning... > >CMake Warning at c:/Program Files

[CMake] cmake doesn't find QtCore

Hi, I'm trying to install PySide. With "pip install PySide", I get the warning... CMake Warning at c:/Program Files (x86)/Cmake/share/cmake-3.7/Modules/FindQt4.cmake:618 (message): C:/Qt/4.8.5/bin/qmake.exe reported QT_INSTALL_LIBS as "C:/Qt/4.8.5/lib" but QtCore could not be found there. Qt

Re: [CMake] CMake doesn't detect Microsoft Build Tools 2015 on Windows 10

Please open a bug, I can take a look at it. From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Eduard Wirch Sent: Monday, October 10, 2016 02:41 To: cmake@cmake.org Subject: [CMake] CMake doesn't detect Microsoft Build Tools 2015 on Windows 10 Hi I've installed build tools from here

[CMake] CMake doesn't detect Microsoft Build Tools 2015 on Windows 10

Hi I've installed build tools from here: http://landinghub.visualstudio.com/visual-cpp-build-tools But CMake will automatically detect (and choose) Visual Studio 8 (installed here as well) instead. Looking into the source: const std::string vsregBase =

Re: [CMake] [cmake-developers] Problems with icons for Windows Store 10.0

Hi Roman, Glad to hear that it works. We discussed this when I implemented the feature, the only reason the functionality has been implemented is to supplement the intermediate projects that CMake produces that cannot easily be adapted for the requirements of a Windows Store application. For

Re: [CMake] [cmake-developers] Problems with icons for Windows Store 10.0

Thanks Gilles, I added a custom appxmanifest as you mentioned and it works, but it would nevertheless very helpful to customize such things via variables and let CMake fill out the rest. Regards Roman > Am 05.10.2016 um 21:19 schrieb Gilles Khouzam : > > That's

Re: [CMake] [cmake-developers] Problems with icons for Windows Store 10.0

That's most likely because you're missing an AppxManifest. In order to build the CMake detection projects, we inject some necessary files into the project when they aren't specified. This includes the manifest and the icons. Can you add your app manifest to the project (look at

Re: [CMake] [cmake-developers] Problems with icons for Windows Store 10.0

On 10/05/2016 02:56 PM, Roman Wüger wrote: > I tried the following to copy the required app icons to the required > destination: > > configure_file(Logo.png > ${CMAKE_CURRENT_BINARY_DIR}/${PROJECT_NAME}.dir/Logo.png COPYONLY) That's a CMake-private directory whose location is an implementation

[CMake] cmake install multiple artifacts

Hello, I'm using CMake to cross compile some code using Emscripten. Emscripten generates html/javascript files from c++ input files. In my case, my generated binary output is an html file that loads in a javascript file. Both files are generated from the final link step. When I do the

Re: [CMake] [cmake-developers] CPack [WiX] Customizations of individual features/components

On 09/30/2016 08:43 AM, Roman Wüger wrote: Hello, I want to customize some with CPack generated *.wxs files. For example: directories.wxs is generated with only the TARGET_DIR. TARGETDIR (no underscore) is always the one and only root-directory element [1]. How can I add an additional

Re: [CMake] [cmake-developers] CPack [WiX] Customizations of individual features/components

Hello Roman, directories are added automatically to the directories.wxs file if you use the install() command in cmake and set the DESTINATION to some subfolder: install(FILES DESTINATION "my/sufolder/path") To add completely new directories I'd suggest to use CPACK_WIX_EXTRA_SOURCES

Re: [CMake] [cmake-developers] CPack [NSIS] Install directory per component

Hello,I've attached a patch with which it is now possible to set custom install directories per component. 0001-CPack-NSIS-custom-component-install-directory.patch Description: Binary data Best RegardsRomanAm 21.09.2016 um 23:04 schrieb Roman Wüger :Hello,Per default the

Re: [CMake] cmake source tree pollution ?

It seems to be the cause. Thanks Vania On 09/12/2016 09:42 AM, Magnus Therning wrote: Bruce Stephens writes: Looks like https://github.com/redguardtoo/cpputils-cmake might be involved... If that is the case then this section could be of interest:

Re: [CMake] cmake source tree pollution ?

Bruce Stephens writes: > Looks like https://github.com/redguardtoo/cpputils-cmake might be involved... If that is the case then this section could be of interest: https://github.com/redguardtoo/cpputils-cmake#stop-creating-makefiles-for-flymake /M -- Magnus

Re: [CMake] cmake source tree pollution ?

Looks like https://github.com/redguardtoo/cpputils-cmake might be involved... On Fri, Sep 9, 2016 at 5:04 PM, Vania Joloboff wrote: > On 09/09/2016 05:45 PM, Michael Ellery wrote: >> >> This kinda’ sounds like you are doing an in-source build. Are you certain >> that

Re: [CMake] cmake source tree pollution ?

On 09/09/2016 05:45 PM, Michael Ellery wrote: This kinda’ sounds like you are doing an in-source build. Are you certain that your currrent/working directory is different from your source tree root when you run cmake? The typical way of doing this is just to make a subdirectory of your source

Re: [CMake] cmake source tree pollution ?

On Fri, Sep 9, 2016 at 4:45 PM, Michael Ellery wrote: > This kinda’ sounds like you are doing an in-source build. Are you certain > that your currrent/working directory is different from your source tree root > when you run cmake? The typical way of doing this is just to

Re: [CMake] cmake source tree pollution ?

This kinda’ sounds like you are doing an in-source build. Are you certain that your currrent/working directory is different from your source tree root when you run cmake? The typical way of doing this is just to make a subdirectory of your source root: mkdir my_build cd my_build cmake

[CMake] cmake source tree pollution ?

Hi, I have started to use CMake for my software. I build in a separate directory using : $> cmake -G "Unix Makefiles" Everything is built correctly and the software works fine. However all of my source code directories get polluted. Into each source directory, a new Makefile is created. All

Re: [CMake] CMake library installations and pkg-config

01.09.2016, 08:34, "n...@appletonaudio.com" : > On 2016-08-31 23:32, Konstantin Tokarev wrote: >>  31.08.2016, 16:22, "Nick Appleton" : >>>  Hi, >>> >>>  I’ve been recently doing a bit of work for an open source project >>>  trying to extend it’s

Re: [CMake] CMake library installations and pkg-config

On 2016-08-31 23:32, Konstantin Tokarev wrote: 31.08.2016, 16:22, "Nick Appleton" : Hi, I’ve been recently doing a bit of work for an open source project trying to extend it’s support for CMake. I’ve been trying to get CMake to be able to replicate most of the

Re: [CMake] CMake library installations and pkg-config

31.08.2016, 16:22, "Nick Appleton" : > Hi, > > I’ve been recently doing a bit of work for an open source project trying to > extend it’s support for CMake. I’ve been trying to get CMake to be able to > replicate most of the functionality which can be achieved with the

[CMake] CMake library installations and pkg-config

Hi, I’ve been recently doing a bit of work for an open source project trying to extend it’s support for CMake. I’ve been trying to get CMake to be able to replicate most of the functionality which can be achieved with the existing autoconf-based infrastructure (and have had pretty good

[CMake] CMake/CTest no RUN_TESTS target

Hey, I’ve try to get ctest running with my existing gtest-tests. I have my own findGTest, but should make no difference. My Problem is that I can’t see the RUN_TESTS target (I’m using Visual Studio). I follow the following tutorialhttps:// cmake.org/Wiki/CMake/Testing_With_CTest I’m start

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

On 17-Aug-16 04:29, Florent Castelli wrote: The Boost source download is cached outside of the build directory in a unique folder. So it’s effectively only done once for all platforms and then reused. This is true for local machines and for custom build servers like your personal Jenkins.

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

On 17-Aug-16 08:36, Elizabeth A. Fischer wrote: > > I don't think CMake is the best place to do it, > Can you provide any details? I personally think that CMake is a > natural and the only place where it should be done. The most important reason here is because there are combinatorially many

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

Well, I tried upstreaming the new build scripts to some projects and it didn’t go well. Some of the reasons I’ve heard of: > I installed CMake 2.8.6 five years ago and I don’t want to update yet > again! People relying on old versions is quite common and any attempt > to raise the min version

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

On 16-Aug-16 16:37, Florent Castelli wrote: Well, I tried upstreaming the new build scripts to some projects and it didn’t go well. Some of the reasons I’ve heard of: - Windows developpers don’t use CMake, they have project files on the repository. The CMake files for Windows will never be

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

On 16-Aug-16 17:04, Florent Castelli wrote: On 16 Aug 2016, at 15:29, Ruslan Baratov > wrote: On 16-Aug-16 13:52, Florent Castelli wrote: For example, Boost is used by 5 platforms: Windows, OSX, Linux, Android and iOS. Each

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

On 16-Aug-16 13:52, Florent Castelli wrote: For example, Boost is used by 5 platforms: Windows, OSX, Linux, Android and iOS. Each platform has a different CPU target (or many 32/64bit, x86/ARM). Each platform has many compilers. Some platforms have instrumentation options (Debug / Release, ASan,

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

CMake builds for existing libraries are certainly an interesting and useful thing, and deserve to be posted in a GitHub repo somewhere. They should also serve as the basis of a campaign to get the library authors to incorporate the CMake build directly in their repos. But any approach that

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

Very interesting discussion, we have the same issues here. Florent Castelli, how many third parties libraries do you use ? I think a super build can be a very good solution but I'm wondering how much third party code you have to build. Here we use OpenCV, with, boost, and poco, and other

[CMake] CMake updates timestamp when there are missing files.

Hi, I've noticed a weird (but maybe expected) behavior. My colleague forgot to edit CMakeLists.txt file for a library from which he deleted a .cpp file. As expected cmake failed with an error message during build. But next build after that passed without issues. CMake didn't run even though

Re: [CMake] cmake 3.5 vs 3.6 + qt

https://gitlab.kitware.com/cmake/cmake/issues/16209 > > We will have to revert the offending changes until another > solution is found. > > -Brad > > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake

<    2   3   4   5   6   7   8   9   10   11   >