Re: [CMake] getting paths of header files

Some additional info. Here is my cmakelists.txt for the vector3_scalar module: PROJECT(vector3_scalar) SET(CMAKE_MACOSX_RPATH 1) INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}/../common) SET(HEADER_FILES ${CMAKE_CURRENT_SOURCE_DIR}/../common/common_structs.h) SET(SRC_FILES

Re: [CMake] getting paths of header files

Hej, A quick glance doesn't show anything out of the ordinary, except that * I'd prevent any use of `..` in your folder references (by using things like $ and $ * I think it is more

Re: [CMake] getting paths of header files

Damn. send the unfinished message, I'll repeat what I had, and type the rest: Hej, A quick glance doesn't show anything out of the ordinary, except that * I'd prevent any use of `..` in your folder references (by using things like $ and

[cmake-developers] [CMake 0015799]: Way to pass git options for cloning in ExternalProject_Add

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15799 == Reported By:gonzalob...@gmail.com Assigned To:

Re: [CMake] Known issues with Xcode 6.x and CMake

Hello, On 17/10/15 18:28, Michael Jackson wrote: Are there any known issues with Xcode 6.4 and CMake 3.3.x? I ask because in our project when we generate the Xcode project we end up with 2 or 3 executables listed in the drop down combo box. We also end up with lots of duplicate targets in

Re: [CMake] CMake on 64-bit Visual Studio

2015-10-19 13:01 GMT+03:00 Peter Hull : > > I have been trying to compile the Allegro library (http://liballeg.org/) on > Windows 64-bit using Visual Studio 2015. > I am running into a problem where CMake 3.3.2 doesn't correctly locate the > 64-bit version of gdiplus.lib. >

Re: [CMake] linking hared libraries

You made a few points that I have not seen before specifically using $ and $ Where are these commands, I just did a search and found a mailing list that said they will override

[CMake] linking hared libraries

Hi guys Can I get some help with this question I have. I did a really thorough writeup here on SO: http://stackoverflow.com/questions/33209659/cmake-no-rule-to-make-target-for-internal-shared-library?noredirect=1#comment54224377_33209659 -- Powered by www.kitware.com Please keep messages

[CMake] CMake on 64-bit Visual Studio

I have been trying to compile the Allegro library (http://liballeg.org/) on Windows 64-bit using Visual Studio 2015. I am running into a problem where CMake 3.3.2 doesn't correctly locate the 64-bit version of gdiplus.lib. I've got a minimal example: cmake_minimum_required(VERSION 3.3)

Re: [CMake] linking hared libraries

Ray Thanks, removing them from the sub projects didn't cause any issues, although I am still having the issue with either a no rule to make target error or if I remove the header I get a linking error:

Re: [CMake] linking hared libraries

also one more question. I have a few header only files one in common/common_structs.h and core_math/core_math.h These files aren't compiled anywhere, they are just used as header only files that I will eventually use to link in different versions of the matrix and vector classes. For example I

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-687-ga478b43

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

Re: [cmake-developers] [Review Request] New module: IncludeUrl

Hello Brad, On 12/10/2015 17:00, Brad King wrote: >> I understand this is a quite controversial module, but I would like to >> stress that this is something that can already be done using CMake just >> by executing file(DOWNLOAD) and include(), this module just makes it >> easy to do it. Whether

[cmake-developers] [CMake 0015801]: FindCUDA.cmake incorrectly includes cu file dependencies

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15801 == Reported By:tomwar Assigned To:

Re: [cmake-developers] Add command line options for deprecation message control

On 10/18/2015 07:59 AM, Michael Scott wrote: > I was thinking of coming back to issue of the deprecation and author > message options, now that CMake 3.4 has been released, is now a suitable > time for it? Yes. Early in the development cycle is best. > We modify cmake::IssueMessage to check

Re: [cmake-developers] Filesystem timestamp checks

On 10/15/2015 03:58 PM, Ruslan Baratov wrote: > 3. Apply changes to CMakeLists.txt "immediately", CMakeLists.txt modification > time 105 > 4. Run rebuild: `cmake --build _builds`. Since CMakeLists.txt (105) is not > "newer" > then Makefile (105) there will be no regenerate command run and

Re: [CMake] linking hared libraries

Hi Owen, On Mon, Oct 19, 2015 at 8:43 PM, Owen Alanzo Hogarth wrote: > Also you said the PROJECT() should only be defined once, but shouldn't each > cmakelists.txt contain a project() or else cmake complains at me. According to the last paragraph of:

Re: [CMake] providing host binary and target library cmake-package when cross compiling

This is the entire project as it stands right now. I have tried changing from using relative to more absolute directory names in my project but I still get the same build errors. This pastebin has all the relevant code: http://pastebin.com/BnVTnegP Anyone can see anything wrong with this? On

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-698-g6569d40

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

Re: [cmake-developers] CMakeForceCompiler

On 10/19/2015 10:46 AM, Brad King wrote: > CMakeForceCompiler: Deprecate this module and its macros > https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5908dcb6 After fixing a typo in the commit message: CMakeForceCompiler: Deprecate this module and its macros

[CMake] providing host binary and target library cmake-package when cross compiling

Hello I'm working on CMake support for Apache Thrift [1]. It is currently already buildable using CMake. However while trying to add support for generating a ThriftConfig.cmake I ran into some issues related to cross compilation. Thrift has the following components relevant to the problem: C++

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-694-gf89d719

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-692-g770cf22

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

Re: [cmake-developers] CMakeForceCompiler

On 09/22/2015 04:39 PM, Brad King wrote: > I think it should be deprecated if possible. First we must > provide alternatives for all its use cases though. I'm not familiar with any cases that cannot be supported in other ways so I decided to deprecate the module now: CMakeForceCompiler:

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-696-g2dae101

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

Re: [CMake] providing host binary and target library cmake-package when cross compiling

Sorry I don't see how this relates to my question? On Mon, Oct 19, 2015 at 5:33 PM, Owen Alanzo Hogarth wrote: > This is the entire project as it stands right now. I have tried changing > from using relative to more absolute directory names in my project but I > still get

Re: [CMake] Creating relocatable packages

Thank you for your reply, Guillaume. I understand that this is the expected behavior. I even linked to the documentation that says this is the expected behavior. What I don't understand is how to resolve it. Are you saying it is not possible to create a relocatable package unless all

Re: [cmake-developers] CMakeForceCompiler

On 10/19/2015 10:46 AM, Brad King wrote: > This will at least call attention to the problems with this > module and hopefully bring to light any remaining use cases > that require it. For reference, an additional problem is discussed here: https://cmake.org/Bug/view.php?id=15797#c39641 The

Re: [CMake] Creating relocatable packages

Hello, Use ExternalProject to build libpcap as part of your project. Make sure you use $ORIGIN in rpath everywhere. Install your application (and your bundled libpcap) to /opt to avoid polluting the system. On Mon, Oct 19, 2015 at 10:37 PM, Zac Bergquist wrote: > Thank

Re: [CMake] Creating relocatable packages

Well, that's one answer. But if you want to use system libpcap, it's not a very satisfying one. It's odd that pcap doesn't ship with a .pc file. I guess the pcap folks are hostile to pkgconfig because it's LGPL; see https://github.com/the-tcpdump-group/libpcap/issues/374 - Dan On Mon, Oct 19,

Re: [CMake] Creating relocatable packages

Hi Dan, On a second read, it seems Zac's problem was actually finding the dependency (libpcap) of a dependency. Or rather, making if findable, because the second depenency contains an absolute path which is broken due to cross-compilation. I have never used it but this page contains information

Re: [cmake-developers] CMakeForceCompiler

Brad King wrote: > On 10/19/2015 10:46 AM, Brad King wrote: >> CMakeForceCompiler: Deprecate this module and its macros >> https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5908dcb6 > > After fixing a typo in the commit message: > > CMakeForceCompiler: Deprecate this module and its macros

Re: [cmake-developers] CMakeForceCompiler

On 10/19/2015 03:02 PM, Stephen Kelly wrote: > You're using message(DEPRECATION) - no one will see the warning message you > added. At least now we can point at the documentation when someone asks about it. > I think message(DEPRECATION) is broken by design and should not be used > until it

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-717-ge17e6c2

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-711-g09ea169

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

Re: [CMake] providing host binary and target library cmake-package when cross compiling

You didn't answer my points b and c, only a. Am 19. Oktober 2015 18:45:25 MESZ, schrieb Owen Alanzo Hogarth : >this is not an in source build. > >to do matrix vector multiplication matrix module needs to have access >to >the vector class. > > >I'll add the source code for

Re: [CMake] Creating relocatable packages

Yes, Pau, this is exactly my problem. Or more specifically, as the author of a library that uses CMake and depends on libpcap, how can I best structure and distribute the library to make it easy to use (and cross compile)? I would say using the system libpcap is strongly preferred over

Re: [CMake] Creating relocatable packages

I had a look at his example, but stopped at the 'export' line. That's just black magic to me :-) CMake user package registry? Yikes. I stopped trying to use cmake for uberbuilds several years ago. - Dan On Mon, Oct 19, 2015 at 2:35 PM, Pau Garcia i Quiles wrote: > Hi

Re: [cmake-developers] Filesystem timestamp checks

On 19-Oct-15 19:30, Brad King wrote: On 10/15/2015 03:58 PM, Ruslan Baratov wrote: 3. Apply changes to CMakeLists.txt "immediately", CMakeLists.txt modification time 105 4. Run rebuild: `cmake --build _builds`. Since CMakeLists.txt (105) is not "newer" then Makefile (105) there will be no

Re: [CMake] Creating relocatable packages

Hello, In your case, what you need to do is to modify the config file generation in the library (i. e. you will need to patch the third-party library) so that the generated config file is relative. As an alternative, if you do not want to patch the third-party library, try modifying the

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-256-g693141c

_VERSION_MINOR 4) -set(CMake_VERSION_PATCH 20151019) +set(CMake_VERSION_PATCH 20151020) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] Creating relocatable packages

Hi Zac, Sorry I read your post very quickly the first time... If your library uses its own FindPCAP.cmake then you can define an imported target for the PCAP libraries like so: # FindPCAP.cmake find_path(PCAP_INCLUDE_DIR pcap.h ... ) find_library(PCAP_LIBRARY pcap ... )

Re: [CMake] cmake_check_build_system is causing a rebuild at "make install"

Thanks for the response, James. Our workaround finally was to do "make install/fast". A colleague pointed out that there is a bug report, https://cmake.org/Bug/view.php?id=15801, likely related to this. Is there something about CUDA that requires dependency generation at build time? (I am

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-252-g919f26f

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-700-g752c301

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-704-g6f61eae

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

[Cmake-commits] CMake branch, release, updated. v3.4.0-rc1-21-g22bfb39

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

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-255-g383abcd

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-709-gd21ed9a

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

Re: [CMake] providing host binary and target library cmake-package when cross compiling

Am 19. Oktober 2015 17:33:55 MESZ, schrieb Owen Alanzo Hogarth : >This is the entire project as it stands right now. I have tried >changing >from using relative to more absolute directory names in my project but >I >still get the same build errors. > >This pastebin has all

Re: [CMake] providing host binary and target library cmake-package when cross compiling

this is not an in source build. to do matrix vector multiplication matrix module needs to have access to the vector class. I'll add the source code for these modules here: http://pastebin.com/aj01ycRQ I think the structure should be a little clearer with all that I've provided. This is the