[CMake] cmake, ccache, CCACHE_BASEDIR: wrong paths in compiler error messages

Hi, I hope I can still post here? I don't have a "discourse" account. Let me summarize what we have here. We have projects with some hunderds CMakeLists.txt. The "main" typically use several add_subdirectory directives for the use libraries in form of: add_subdirectory(${path_lib_a} liba)

[CMake] cmake config. error

em, please send your config file to cm...@www.cmake.org so it can be added to cmake -- Check for working C compiler: /mingw64/bin/cc.exe -- works -- Detecting C compiler ABI info System is unknown to cmake, create: Platform/MINGW64_NT-10.0-18362 to use this system, please send your config file to cm

Re: [CMake] [cmake-developers] productbuild: Installing to absolute system path or to user home path

Ok if someone is interested I solved it with a post-install script at the moment. I installed it in the default location and moved it afterwards with the post-install script to the ~/Library... Regards Roman > Am 05.11.2019 um 15:02 schrieb Roman Wüger : > >  > Hello, > > The main wish is

[CMake] CMake on host executing compiler inside docker

IDE would be a good idea. At that point, compiling and packaging for the host platform is probably easier. So what I tried was to take the docker images, and let my local CMake (CMake on the host, not in docker), use the compiler in the docker image. This would have following advantages

Re: [CMake] CMake link to external library

On Tue, Nov 12, 2019 at 7:39 AM . wrote: > Hi, > I used instruction for CMake linking external library from > https://stackoverflow.com/questions/8774593/cmake-link-to-external-library(for > example) > And it works on Ubuntu 16 only. > > When I try it made on Ubuntu 18 I got problem during start

[CMake] CMake link to external library

Hi, I used instruction for CMake linking external library from  https://stackoverflow.com/questions/8774593/cmake-link-to-external-library(for example) And it works on Ubuntu 16 only. When I try it made on Ubuntu 18 I got problem during start application:  error while loading shared libraries:

Re: [CMake] CMake Error Flagged in MSVC Toolchain File

Yeah, I typed it correctly in the actual command and missed the C when copy-pasting it here. Sorry about that. I also want to know if it's possible to use LLVM 10 with the ClangCl toolset in VS2019. The toolchain file itself uses LLVM 8.0.1, but I also have LLVM 10 installed on my computer

[CMake] CMake Error Flagged in MSVC Toolchain File

I tried to configure a FLTK build with this: "make .. -G "Visual Studio 16 2019" -A x64 -T "ClangCl" -DCMAKE_INSTALL_PREFIX=../install -DCMAKE_CXX_COMPILER=C:/llvm-project/install/bin/clang-cl.exe -DCMAKE_C_COMPILER=C:/llvm-project/install/bin/clang-cl.exe -DCMAKE_BUILD_TYPE=Release

[CMake] CMake variable to set stack size

Hi, Is there a CMake variable to set the stack size of a target? Upon searching the issues, I came across this one - https://gitlab.kitware.com/cmake/cmake/issues/17572 . It says that there is a CMake variable CMAKE_CXX_STACK_SIZE, but it isn’t clear whether CMAKE_CXX_STACK_SIZE can be used

Re: [CMake] [cmake-developers] productbuild: Installing to absolute system path or to user home path

According to the docs, the INSTALL command uses the absolute path if it is given as the DESTINATION, so it should work. https://cmake.org/cmake/help/latest/command/install.html Did you try using a double quoted string, instead of escaping the space with a backslash? I think this should work

Re: [CMake] CMake link order

Hello, I have always used all of the libraries at once to the TARGET_LINK_LIBRARIES command. In the following example, the link line order appears the same as the libraries are listed on the line. TARGET_LINK_LIBRARIES(devsim_tcl ${LIBRARIES} ${TCL_ARCHIVE} ${SUPERLU_ARCHIVE} ${BLAS_ARCHIVE}

Re: [CMake] CMake link order

Hey all, I face a similar problem when constructing a correct (and predictable) link order for Linux and Cygwin. It would be of great help, if there is some documentation. In particular, I would raise two question     1) when does the link order change?     2) when does a clean up happen and in

Re: [CMake] CMake link order

On Fri, Oct 18, 2019, at 11:55 AM, Fred Baksik wrote: > > In target_link_libraries it states that "The library dependency graph is > normally acyclic (a DAG)". I recall from my own experience that the DAG is > not always created the same way when generating the project. It has to do > with

Re: [CMake] CMake link order

On Fri, Oct 18, 2019, at 6:24 AM, Bon, William wrote: > Hello, > > we are facing an issue while using cmake and we have no idea how to solve or > debug it. > We have a complex and huge project (about 50 subdirectories and dependencies > everywhere), and we are facing issue regarding the link

[CMake] CMake link order

Hello, we are facing an issue while using cmake and we have no idea how to solve or debug it. We have a complex and huge project (about 50 subdirectories and dependencies everywhere), and we are facing issue regarding the link order. There is a lot of dependencies between those projects, and to

Re: [CMake] CMake 3.15 fails to install on OS X

is not recommended). See this Wikipedia article <https://en.wikipedia.org/wiki/System_Integrity_Protection> for more information on SIP. Am 15.10.19 um 07:05 schrieb Jeffrey Walton: I'm building CMake cmake-3.15.4.tar.gz on OS X 10.12. The machine is stripped down, and only has the COmman

[CMake] CMake 3.15 fails to install on OS X

I'm building CMake cmake-3.15.4.tar.gz on OS X 10.12. The machine is stripped down, and only has the COmmand Line tools. No Xcode and friends. I configured with: ./configure --prefix=/usr Configure appears OK. Make appears OK. Install is failing: $ sudo make install VERBOSE=1

Re: [CMake] cmake end user vs. developer rpath handling

On Thu, 10 Oct 2019, Eric Noulard wrote: ... > with patchelf is works with an intriguing warning: > warning: working around a Linux kernel bug by creating a hole of 2093056 > bytes in ‘/path/to/executable’ > > which seems to be a resolved issue: > https://github.com/NixOS/patchelf/issues/92 > >

Re: [CMake] cmake end user vs. developer rpath handling

On Thu, 10 Oct 2019, Eric Noulard wrote: ... > No rpath and using "only" LD_LIBRARY_PATH is not feasible in that case? > Removing rpath is easy; chrpath -d lib_or_exe You could but, to avoid a maintenance headache, you'd normally end up getting the environment module to load any prereq

Re: [CMake] cmake end user vs. developer rpath handling

From: Eric Noulard Sent: 10 October 2019 14:43 To: Zakrzewski, Jakub Cc: cmake@cmake.org Subject: Re: [CMake] cmake end user vs. developer rpath handling > So I was wrong, thank you for your honest question Jakub. > I learned something usefull thanks

Re: [CMake] cmake end user vs. developer rpath handling

.@gmail.com> >> *Sent:* 10 October 2019 12:05 >> *To:* DIXON, MARK C. >> *Cc:* cmake@cmake.org >> *Subject:* [DKIM] Re: [CMake] cmake end user vs. developer rpath handling >> >> >> > No they can't because the maximum size is burried into the binary

Re: [CMake] cmake end user vs. developer rpath handling

e@cmake.org > *Subject:* [DKIM] Re: [CMake] cmake end user vs. developer rpath handling > > > > No they can't because the maximum size is burried into the binary ELF > file, > > that why CMake "reserve" some space with many "" in order to replace > B

Re: [CMake] cmake end user vs. developer rpath handling

From: CMake on behalf of Eric Noulard Sent: 10 October 2019 12:05 To: DIXON, MARK C. Cc: cmake@cmake.org Subject: [DKIM] Re: [CMake] cm?ake end user vs. developer rpath handling > No they can't because the maximum size is burried into the binary ELF file, >

Re: [CMake] cmake end user vs. developer rpath handling

Le jeu. 10 oct. 2019 à 13:08, DIXON, MARK C. a écrit : > On Thu, 10 Oct 2019, Eric Noulard wrote: > ... > > No they can't because the maximum size is burried into the binary ELF > file, > > that why CMake "reserve" some space with many ";;;" in order to replace > > BUILD_RPATH with INSTALL_RPATH

Re: [CMake] cmake end user vs. developer rpath handling

On Thu, 10 Oct 2019, Eric Noulard wrote: ... > No they can't because the maximum size is burried into the binary ELF file, > that why CMake "reserve" some space with many ";;;" in order to replace > BUILD_RPATH with INSTALL_RPATH when doing > 'install'. Hi Eric, Interesting - any ideas on how

Re: [CMake] cmake end user vs. developer rpath handling

Le jeu. 10 oct. 2019 à 10:36, DIXON, MARK C. a écrit : > On Wed, 9 Oct 2019, Aaron Cohen wrote: > > > Is it not feasible to just let the build system do whatever it is going > to > > and use "chrpath" or "patchelf" to change the rpath after-the-fact? > > Thanks for the suggestion, but I need to

Re: [CMake] cmake end user vs. developer rpath handling

On Wed, 9 Oct 2019, Aaron Cohen wrote: > Is it not feasible to just let the build system do whatever it is going to > and use "chrpath" or "patchelf" to change the rpath after-the-fact? Thanks for the suggestion, but I need to add directories to the rpath: I believe that neither utility allows

Re: [CMake] cmake end user vs. developer rpath handling

Am 9. Oktober 2019 08:09:19 MESZ schrieb "Zakrzewski, Jakub" >That "something" seems to be line 257: >set(CMAKE_INSTALL_RPATH "${CMAKE_INSTALL_PREFIX}/${LIB_INSTALL_DIR}") IMHO setting this to something based on CMAKE_INSTALL_PREFIX is rarely a good idea if it can be relative to the runtime

Re: [CMake] cmake end user vs. developer rpath handling

Is it not feasible to just let the build system do whatever it is going to and use "chrpath" or "patchelf" to change the rpath after-the-fact? On Wed, Oct 9, 2019 at 11:48 AM DIXON, MARK C. wrote: > On Wed, 9 Oct 2019, Craig Scott wrote: > ... > >>> Is there a way to reliably add to, or at

Re: [CMake] cmake end user vs. developer rpath handling

On Wed, 9 Oct 2019, Craig Scott wrote: ... >>> Is there a way to reliably add to, or at least override, the developer's >>> rpath in any cmake-built software? >> >> Short of editing the build system scripts? I doubt... > > The CMAKE_INSTALL_RPATH variable is used to initialise the INSTALL_RPATH >

Re: [CMake] cmake end user vs. developer rpath handling

On Wed, 9 Oct 2019, Zakrzewski, Jakub wrote: ... > That "something" seems to be line 257: set(CMAKE_INSTALL_RPATH > "${CMAKE_INSTALL_PREFIX}/${LIB_INSTALL_DIR}") There's a second something that's adding boost's library directory. I'm guessing this is maybe coming from my copy of cmake's boost

Re: [CMake] CMake and Ninja, RERUN_CMAKE useless?

The default generator and all other associated information ( '-D' ) is kept in the CMakeCache.txt file in the root of the build directory. The execution of `cmake -S -B ` will reload this cache before doing anything else. Have you verified that your build directory hasn't deleted this file? On

Re: [CMake] cmake end user vs. developer rpath handling

On Wed, Oct 9, 2019 at 5:24 PM Zakrzewski, Jakub < jakub.zakrzew...@scheer-group.com> wrote: > > > From: CMake on behalf of DIXON, MARK C. < > mark.c.di...@durham.ac.uk> > Sent: 08 October 2019 17:25 > To: cmake@cmake.org >

Re: [CMake] cmake end user vs. developer rpath handling

From: CMake on behalf of DIXON, MARK C. Sent: 08 October 2019 17:25 To: cmake@cmake.org Subject: [CMake] cmake end user vs. developer rpath handling >Sometimes, this does the trick. When it does, I'm very happy: > > cmake -D CMAKE_INSTALL_R

[CMake] CMake and Ninja, RERUN_CMAKE useless?

Hi all, My question comes from a Ninja generator build system, and is specifically about an internal rule generated by cmake. What is the purpose of the RERUN_CMAKE rule generated by CMake with a Ninja generator? In the current repo, the only reference to this rule is in

[CMake] cmake end user vs. developer rpath handling

Hi, I install lots of software packages under Linux and, increasingly, they use cmake instead of other methods (congratulations!) Frustratingly for me, I seem to keep ending up in a fight with the various developer's cmake config files over what rpath should be set, among other things.

Re: [CMake] CMake removes /DEF: option in CMAKE_SHARED_LINKER_FLAGS

Hi Craig, Thank you for this information. I never tried this way with the own CMakeLists.txt and I should try it. I found one efficient workaround however which is the option -DCMAKE_CXX_STANDARD_LIBRARIES=/DEF:additionalDefFile.def. It turned that the content of CMAKE_CXX_STANDARD_LIBRARIES is

Re: [CMake] CMake removes /DEF: option in CMAKE_SHARED_LINKER_FLAGS

On Sat, Oct 5, 2019 at 12:59 AM Alexander wrote: > Dear Cristian, > > It would better for me not modifying CMakeFiles.txt, because as I wrote it > is 3rd party stuff (we just download it and build, but some different way). > My concern is why the command line option -DCMAKE_SHARED_LINKER_FLAGS >

Re: [CMake] CMake removes /DEF: option in CMAKE_SHARED_LINKER_FLAGS

Dear Cristian, It would better for me not modifying CMakeFiles.txt, because as I wrote it is 3rd party stuff (we just download it and build, but some different way). My concern is why the command line option -DCMAKE_SHARED_LINKER_FLAGS deliberately ignores /DEF: option. It this behavior expected?

Re: [CMake] CMake removes /DEF: option in CMAKE_SHARED_LINKER_FLAGS

Hi, You should simply add the my_defs.def file as a source files to add_library/add_executable. CMake will automagically pass /DEF: to the linker with my_defs.def Cheers, Cristian. On Fri, Oct 4, 2019 at 4:45 PM Alexander wrote: > Hello, > > I would like to add an extra .defs file for linking

[CMake] CMake removes /DEF: option in CMAKE_SHARED_LINKER_FLAGS

Hello, I would like to add an extra .defs file for linking of a DLL on Windows. I want to use the CMake command line option -DCMAKE_SHARED_LINKER_FLAGS="/DEF:my_defs.defs". I expect that besides the automatically generated /bin/.dir/Release/exports.def i see additionally /DEF:my_defs.defs in the

[CMake] Cmake error

Dear all, I'm trying to install LLVM with all the projects because I need Clang and the SPIR-V target. I am using cmake like the llvm manual says and it give me this error, could you help me to solve it? I am following the steps from this page: https://llvm.org/docs/GettingStarted.html CMAKE

Re: [CMake] cmake for GHS

On Thu, Aug 29, 2019, at 1:51 AM, Deepan Muthusamy (RBEI/ESP-IS44) via CMake wrote: > I want to compile c and c++ code in GHS compiler for renesas controller. > > For Mingw compiler, My code is compiling successfully. But I want to compile > for GHS. > > I have compiler available at this

[CMake] cmake for GHS

I want to compile c and c++ code in GHS compiler for renesas controller. For Mingw compiler, My code is compiling successfully. But I want to compile for GHS. I have compiler available at this path "C:/ghs/comp_201255_RH850". When generate, I gave option as "specify native compiler". C

[CMake] CMAKE+WIX RUN A PROGRAM AFTER INSTALL SUCCEEDS

Hi how do I configure cpack in cmake to execute a custom command in the install directory. I want to install windows service that is packaged within my installer and extracted to specific install location. Thanks in advance Sent from Mail for Windows 10 -- Powered by www.kitware.com Please

[CMake] Cmake Path Please

THere's (some) error messages that don't include the full path of the CMakeLists.txt, so I don't know what 'top level' is. It would be nice if CMakeLists.txt had the full ${CMAKE_SOURCE_DIR} (?) prepended to it. This is built as an external project of another top level project, which itself is

Re: [CMake] cmake + ninja how to use several CPU cores?

On 2019-07-29 15:32-0400 Brad King wrote: [...]We don't know what `main.cpp` includes until after compiling it, by which point it is too late. It could have `#include "anything.txt"` for example. CMake must add these pessimistic dependencies to ensure a correct build. Is this the real

Re: [CMake] cmake + ninja how to use several CPU cores?

OUTPUT is shared library, and in my case it would be strange to '#include' it into some source file. So what about EXPLICIT_DEPENDS_ONLY mentioned https://gitlab.kitware.com/cmake/cmake/issues/17097 to mark something that no way to be included into source file? -- Powered by www.kitware.com Please ke

Re: [CMake] cmake + ninja how to use several CPU cores?

On 2019-07-29 13:24-0400 Brad King wrote: On 7/29/19 11:50 AM, Dave Milter wrote: Only source code are generated, so main.cpp -> main.cpp.o doesn't depend on anything. But generated by cmake build.ninja still require link of extern_lib before starting main.cpp -> main.cpp.o If there are any

Re: [CMake] cmake + ninja how to use several CPU cores?

On 7/29/19 3:22 PM, Dave Milter wrote: >> Since then all objects in a target can start compiling independently >> so long as that target does not depend on any targets with custom >> commands. See also https://gitlab.kitware.com/cmake/cmake/issues/17097 > Is

Re: [CMake] cmake + ninja how to use several CPU cores?

On Mon, Jul 29, 2019 at 8:24 PM Brad King wrote: > > CMake 3.9 made this much better than it used to be: > > https://gitlab.kitware.com/cmake/cmake/merge_requests/430 > > Since then all objects in a target can start compiling independently > so long as that target does not

Re: [CMake] cmake + ninja how to use several CPU cores?

On 2019-07-29 18:50+0300 Dave Milter wrote: On Mon, Jul 29, 2019 at 1:48 PM Bruce Stephens wrote: I think it's reasonable for CMake/Ninja to require the headers be generated, especially since main.cpp does include one of them (though CMake/Ninja doesn't know that until later). lib/lib1.cpp

Re: [CMake] cmake + ninja how to use several CPU cores?

ed to be: https://gitlab.kitware.com/cmake/cmake/merge_requests/430 Since then all objects in a target can start compiling independently so long as that target does not depend on any targets with custom commands. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the C

Re: [CMake] cmake + ninja how to use several CPU cores?

On Mon, Jul 29, 2019 at 1:48 PM Bruce Stephens wrote: > > I think it's reasonable for CMake/Ninja to require the headers be > generated, especially since main.cpp does include one of them (though > CMake/Ninja doesn't know that until later). lib/lib1.cpp is more > arguable, but I imagine there's

Re: [CMake] cmake + ninja how to use several CPU cores?

You might find it interesting to look at build.ninja. By the looks of it there's a (phony) target guving the dependencies of the library. (That's called cmake_object_order_depends_target_internal_lib) and CMakeFiles/app.dir/main.cpp.o is depending on that. Presumably the idea is that there's no

Re: [CMake] cmake + ninja how to use several CPU cores?

On 2019-07-28 23:39-0700 Alan W. Irwin wrote: @Both: I also plan to look at whether this issue exists for the internal library case so more later when I get that corresponding simple test project implemented. @Brad and David: I have now implemented a simple test project for the internal

Re: [CMake] cmake + ninja how to use several CPU cores?

Hi to Dave and Brad: @Dave: As you are probably already aware Brad is one of the primary CMake developers so I think he should be in on this discussion. @Brad: Using Dave's simple test project I confirmed the compilation delay issue below in detail for both the -G"Ninja" case AND the -G"Unix

Re: [CMake] cmake + ninja how to use several CPU cores?

Hi, On Mon, Jul 29, 2019 at 12:01 AM Alan W. Irwin wrote: > > On 2019-07-28 19:03+0300 Dave Milter wrote: > > To help answer your question, I see no fundamental issues with your code > above. > > If the latter is really true, that appears to me to be a CMake bug > (although I cannot make the

Re: [CMake] cmake + ninja how to use several CPU cores?

On 2019-07-28 19:03+0300 Dave Milter wrote: Hi, I heard that ninja has great feature it allows build continue without wainting full link. So if you have library Lib and executable App, source code of App may build in parallel with source code of Lib, and sync only link stage. While other

[CMake] cmake + ninja how to use several CPU cores?

Hi, I heard that ninja has great feature it allows build continue without wainting full link. So if you have library Lib and executable App, source code of App may build in parallel with source code of Lib, and sync only link stage. While other build systems force build of Lib, and only then

[CMake] CMake (cmake-gui) silently crashes on Windows 10

After months of working correctly I've found that running CMake in GUI form on Windows 10 suddenly began silently crashing on every launch. It does not appear to be the fault of a recent Windows update given an associate of mine has experienced the same issue in an older version of Windows 10. I

Re: [CMake] cmake - two targets that depends on single static library that should be compiled based on the target that is being built

> > > I have a static library and two target executables, let's call them > **libA**, **EXE1**, **EXE2**. > > If I am building EXE2, I need to disabled the macros in libA and don't > link to another library. > [...] > I don't want to create two targets with same source files. > I'm curious why

Re: [CMake] CMake guidelines and design patterns - recommendations?

https://pabloariasal.github.io/2018/02/19/its-time-to-do-cmake-right/ On Thu, Jul 11, 2019 at 1:56 PM hex wrote: > hello community, > > > Does anyone have a book recommendation for modern CMake with focus on > design patterns? > > > thank you > > -- > > Powered by www.kitware.com > > Please

Re: [CMake] CMake guidelines and design patterns - recommendations?

https://crascit.com/professional-cmake/ And search for Daniel Pfeifer's talk on YouTube Mateusz Loskot, mate...@loskot.net (Sent from mobile, may suffer from top-posting) On Thu, 11 Jul 2019, 12:56 hex, wrote: > hello community, > > > Does anyone have a book recommendation for modern CMake

[CMake] CMake guidelines and design patterns - recommendations?

hello community, Does anyone have a book recommendation for modern CMake with focus on design patterns? thank you -- 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 APT Repository Signing Key

All, The new 2020 signing key for the APT repository (https://apt.kitware.com/) has been generated for 2020, with fingerprint A8E5EF3A02600268. The 2019 key, with fingerprint C1F34CDD40CD72DA, will remain in effect until the beginning of 2020, at which point the 2020 key will go into effect. The  

Re: [CMake] cmake - two targets that depends on single static library that should be compiled based on the target that is being built

Ok, seems there is no other way then. Thank you for the clarification. On Tue, Jul 2, 2019 at 3:44 PM Kyle Edwards wrote: > On Tue, 2019-07-02 at 14:18 +0200, ugesh reddy wrote: > > Hello, > > > > I couldn't find any solution's for this problem even after posting > > the question on

Re: [CMake] cmake - two targets that depends on single static library that should be compiled based on the target that is being built

On Tue, 2019-07-02 at 14:18 +0200, ugesh reddy wrote: > Hello, > > I couldn't find any solution's for this problem even after posting > the question on Reddit/stack overflow, so I am posting it here. > > My question is as follows: > > I have a static library and two target executables, let's

[CMake] cmake - two targets that depends on single static library that should be compiled based on the target that is being built

Hello, I couldn't find any solution's for this problem even after posting the question on Reddit/stack overflow, so I am posting it here. My question is as follows: I have a static library and two target executables, let's call them **libA**, **EXE1**, **EXE2**. **libA** has pre-processor

Re: [CMake] CMake with FetchContent instead of Git Submodules

Wow, how did I miss that when I was looking through the page yesterday? That's exactly what I need ; ) I may try going one step further and adding a flag _USE_CLONE=ON that will do the full checkout to a repos directory, initialize the repo to the target tag, and then set FETCHCONTENT_SOURCE_DIR_

Re: [CMake] CMake with FetchContent instead of Git Submodules

On Fri, Jun 28, 2019 at 12:18 PM Dustyn Blasig wrote: > Hi All, > > I'm attempting to replace our use of git submodules with FetchContent > flows instead so we can pull pre-built packages if they already exist > instead of buildings locally. > > However, I need to support a flow similar to Git

[CMake] CMake with FetchContent instead of Git Submodules

Hi All, I'm attempting to replace our use of git submodules with FetchContent flows instead so we can pull pre-built packages if they already exist instead of buildings locally. However, I need to support a flow similar to Git submodules where developers can edit a submodule and then rebuild the

Re: [CMake] cmake on MinGW64; which generator

The problem is the time required to upstream such work. Unfortunately I do not have that time. On Tue, Jun 25, 2019, 12:15 AM Alan W. Irwin wrote: > On 2019-06-24 07:39-0600 Christopher Webster wrote: > > > Thank you Benjamin, that [install and use mingw-w64-x86_64-cmake in the > mingw64 shell]

Re: [CMake] cmake on MinGW64; which generator

On 2019-06-24 07:39-0600 Christopher Webster wrote: Thank you Benjamin, that [install and use mingw-w64-x86_64-cmake in the mingw64 shell] fixed it. I was happy to hear that Benjamin solved this first issue for you. Just to follow up on what he said, I confirm the good PLplot results for

Re: [CMake] cmake on MinGW64; which generator

Am 24.06.2019 um 16:42 schrieb Christopher Webster: On 6/24/19 8:03 AM, Volker Enderlein wrote: Am 24.06.2019 um 15:39 schrieb Christopher Webster: Hi Christopher, did you followed the instructions from https://bitbucket.org/Coin3D/coin/wiki/BuildWithCMake and cloned the repo, e.g. ran hg

Re: [CMake] cmake on MinGW64; which generator

On 6/24/19 8:03 AM, Volker Enderlein wrote: > Am 24.06.2019 um 15:39 schrieb Christopher Webster: > > Hi Christopher, > > did you followed the instructions from > https://bitbucket.org/Coin3D/coin/wiki/BuildWithCMake > and cloned the repo, e.g. ran hg clone > https://bitbucket.org/Coin3D/coin coin

Re: [CMake] cmake on MinGW64; which generator

Am 24.06.2019 um 15:39 schrieb Christopher Webster: Hi Christopher, did you followed the instructions from https://bitbucket.org/Coin3D/coin/wiki/BuildWithCMake and cloned the repo, e.g. ran hg clone https://bitbucket.org/Coin3D/coin coin ? As coin uses subrepositories the Download the

Re: [CMake] cmake on MinGW64; which generator

Thank you Benjamin, that fixed it.  Now to figure out the cpack.d error. Is there a way to search the archives?  I had looked through the last several months of threads, but that is not practical for searching back a over a year Chris On 6/23/19 11:46 PM, Benjamin Eikel wrote: > Dear

Re: [CMake] cmake on MinGW64; which generator

Dear Christopher, Am 23. Juni 2019 23:31:01 MESZ schrieb Christopher Webster : >On 6/23/19 9:22 AM, Alan W. Irwin wrote: >> >> There are a lot of different platforms that use the MinGW-w64 >compiler >> so you should probably >> describe the platform where you are attempting to use that compiler

Re: [CMake] cmake on MinGW64; which generator

On 6/23/19 9:22 AM, Alan W. Irwin wrote: > > There are a lot of different platforms that use the MinGW-w64 compiler > so you should probably > describe the platform where you are attempting to use that compiler in > more detail.  For example, > it sounds like you are simply taking a normal Window

Re: [CMake] cmake on MinGW64; which generator

On 2019-06-23 07:49-0600 Christopher Webster wrote: Greetings,   I am trying to figure out which generator to use on MinGW64 on Windows10, the 2-3 I have tried fail. cmake version is 3.14.5 If I try "Unix Makefiles" I get: $ cmake -S coin -B coin_build -G "Unix Makefiles"

Re: [CMake] cmake on MinGW64; which generator

Hi, You are most probably using MSys2, which means that you are using CMake from MSys2, and they patch CMake for their platform. This also means that CMake upstream doesn't support it. Here are the differences between upstream CMake 3.14.3 and MSys2 CMake

[CMake] cmake on MinGW64; which generator

Greetings,   I am trying to figure out which generator to use on MinGW64 on Windows10, the 2-3 I have tried fail. cmake version is 3.14.5 If I try "Unix Makefiles" I get: $ cmake -S coin -B coin_build -G "Unix Makefiles" -DCMAKE_INSTALL_PREFIX=C:\Tools\Packages\Coin3D -- The C compiler

Re: [CMake] CMake Digest, Vol 182, Issue 32

On Wed, Jun 19, 2019 at 11:30 AM Innokentiy Alaytsev wrote: > Hello! > > Are the header files of the shared library (DLL) listed as INTERFACE_SOURCES > for the library target? AFAIK, the only reason for header files to be > processed by AUTOMOC is to be part of the project. The only way that I

[CMake] CMake now available to Linux users as a snap

Hi all. For those of you working on Linux, I'm pleased to announce that CMake is now available as a snap. This can be a great way to conveniently keep up with the latest CMake releases, even on Linux distributions that are no longer updating their own CMake packages. You can find a brief blog post

Re: [CMake] CMake Release Candidate Builds Available for Ubuntu

ion 3.14.5-0kitware1ubuntu18.04.1 runs just fine out of the box. Cheers, -Andrew From: CMake on behalf of Kyle Edwards via CMake Sent: June 7, 2019 3:05 PM To: CMake Subject: [CMake] CMake Release Candidate Builds Available for Ubuntu All, I am pleased to announce that

Re: [CMake] CMake is Converting lists to strings

You are wrongly using the STRING(REPLACE …) command. The right way to use it to avoid list conversion is to expand the list inside  quotes (to preserve list items separators): STRING (REPLACE "../" "" SIMPLE_LIST "${SIMPLE_LIST}") Without the quotes, all list elements are concatenated in the

Re: [CMake] CMake is Converting lists to strings

I know... just need to rebuild a new list... something like set( _ALL_INCLUDES ) foreach( INC ${ALL_INCLUDES}) string(REPLACE "../" "" INC ${INC}) LIST( APPEND _ALL_INCLUDES ${INC} ) endforeach( INC ) set( ALL_INCLUDES ${_ALL_INCLUDES}) On Wed, Jun 12, 2019 at 3:10 AM J Decker

[CMake] CMake is Converting lists to strings

I'm collecting sources and includes into a parent scope variable, and then attempting to use that variable to reference the right sources. Sources get added to the list as ../(theirpath)/(source) so in the parent level I can simply replace "../" with "" and then they are relative in the right

[CMake] CMake Release Candidate Builds Available for Ubuntu

All, I am pleased to announce that we are now offering Ubuntu builds of the CMake release candidates, in addition to the production releases. The first available release candidate build is 3.15.0~rc1-0kitware2. If you would like to receive release candidate builds, follow the instructions at

Re: [CMake] CMake | CMake/CPack do not print out messages as they progress (#19343)

running |ninja -v bundle| shows |[0/1] cd ... && /.../bin/cpack -C Release --config /.../BundleConfig.cmake| followed by incremental output. — Reply to this email directly or view it on GitLab <https://gitlab.kitware.com/cmake/cmake/issues/19343#note_581122>. You're receiving this

Re: [CMake] Cmake/Cpack creates a corrupt .rpm

El 30/5/19 a las 22:16, Gonzalo Garramuño escribió: El 30/5/19 a las 21:36, Zan Lynx escribió: RPM files are not cpio. They contain a cpio. Use rpm2cpio as a filter. Thanks for that.  Using: rpm2cpio mrViewer-v5.0.7-Linux-64.rpm | cpio -idmv I can extract all the contents of the archive

Re: [CMake] Cmake/Cpack creates a corrupt .rpm

El 30/5/19 a las 21:36, Zan Lynx escribió: RPM files are not cpio. They contain a cpio. Use rpm2cpio as a filter. Thanks for that.  Using: rpm2cpio mrViewer-v5.0.7-Linux-64.rpm | cpio -idmv I can extract all the contents of the archive with no errors. However, rpm -i bails out with a cpio:

Re: [CMake] Cmake/Cpack creates a corrupt .rpm

On May 30, 2019 5:21:59 PM MST, "Gonzalo Garramuño" wrote: > >El 30/5/19 a las 12:51, Gonzalo Garramuño escribió: >> rpm -ql mrViewer-v5.0.6-Linux-64.rpm > >If I run cpio -i < mrViewer-v5.0.6-Linux-64.rpm > >I get a bunch of warnings of Incorrect numbers (and garbage) and Cannot > >make mknod:

Re: [CMake] Cmake/Cpack creates a corrupt .rpm

El 30/5/19 a las 12:51, Gonzalo Garramuño escribió: rpm -ql mrViewer-v5.0.6-Linux-64.rpm If I run cpio -i < mrViewer-v5.0.6-Linux-64.rpm I get a bunch of warnings of Incorrect numbers (and garbage) and Cannot make mknod: the multibyte or extended character is incomplete or invalid, and

Re: [CMake] cmake rewrites part of -S argument depending on the current directory!

On 5/30/19 1:25 PM, Marc Herbert wrote: > I suspect the behaviour I described is also considered a bug Yes, it is a bug and is related to 16228. The problem is that there is a poor implementation of support for the use case described in that issue, and the details of that implementation leak out

Re: [CMake] cmake rewrites part of -S argument depending on the current directory!

f the -S argument AND > > one component of the current directory is a symbolic link THEN > > the leading part of the -S argument is overridden using that > > symbolic link. > > See this issue: > > https://gitlab.kitware.com/cmake/cmake/issues/16228 > > -Brad > --

Re: [CMake] Cmake/Cpack creates a corrupt .rpm

El 30/5/19 a las 12:51, Gonzalo Garramuño escribió: I have a CMakeLists.txt (extract) with the following commands: SET(CPACK_GENERATOR DEB RPM TGZ ) # SET the installation directory. SET(CPACK_SET_DESTDIR true) # Needed SET(CPACK_INSTALL_PREFIX /usr/local/${mrViewerShortName})

[CMake] Cmake/Cpack creates a corrupt .rpm

I have a CMakeLists.txt (extract) with the following commands: SET(CPACK_GENERATOR DEB RPM TGZ ) # SET the installation directory. SET(CPACK_SET_DESTDIR true) # Needed SET(CPACK_INSTALL_PREFIX /usr/local/${mrViewerShortName}) SET(CPACK_RPM_PACKAGE_NAME mrViewer)

[CMake] CMake install doesn't find binary that CMake built?

Using CMake 3.12.2. Consider the following project: project(myproject) set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib) set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib) set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin) set(CMAKE_INSTALL_PREFIX

  1   2   3   4   5   6   7   8   9   10   >