Re: [cmake-developers] Imported Locations in FindBoost.cmake

On 6/19/2016 9:17 PM, Mike Gelfand wrote: > > The suggested way to deal with this seems to be to use > MAP_IMPORTED_CONFIG_ target properties, but I suppose it should > only (?) be used when imported target (or target it's being linked to) > has non-standard configurations, which isn't so in this

Re: [cmake-developers] How to set startup project in Visual Studio

The setting is in a different file that's .vcproj.user (or .user.vcproj) and cmake doesn't write that... would be nice if it could at least write those entiries required... nice thing about xml should be that what's there can be read and used and filled in with the rest of the settings? Well I

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-177-gf4c35c3

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

Re: [CMake] MinGW and sh.exe

I was searching for 'cmake disable check sh.exe' which is not a problem (anymore?) If I do cmake -G "MinGW Makefiles" /some/path it complains; then the same command again succeeds; so it's not a problem... it only causes a stutter in startup; which is a problem; and the project builds and

[CMake] Why a foo.dll.a generated when i build shared lib foo.dll or foo.exe file?

Hi,all, I am working on transferring an existed make project into cmake, and the platform is MinGW(32 bit) on windows. The make flow to build foo.dll or foo.exe would not generate foo.dll.a, but when i use CMake, this generated. I was wondering if this foo.dll.a is necessary, and if it is not

Re: [CMake] cmake install target doesn't run ldconfig after installing library

Thanks :) I think there should be better solutions. But It's the best solution I know so far. On Fri, Jun 17, 2016 at 9:07 PM, Matthew Keeler wrote: > So I did some experimenting. It would seem there are a few rules to the > order installs are executed > > 1 - installs are

Re: [cmake-developers] How to set startup project in Visual Studio

Hello, On 06/18/2016 03:15 PM, Stephen Kelly wrote: > a DIRECTORY property VS_STARTUP_PROJECT which sets the start up project in > Visual Studio. I tried it in the 3.6 RC and it works fine if I set the > property in the top-level directory, so thanks for that. > > However, the documentation

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-418-gb661d4a

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

Re: [cmake-developers] Imported Locations in FindBoost.cmake

Hello, On 06/19/2016 02:00 PM, Andreas Weis wrote: > After fiddling around with the issue, I found that reversing the order > in which the IMPORTED_LOCATION_* fields on the imported target are being > set resolves the issue. It seems that the first configuration that's > added here will be used

Re: [cmake-developers] CMake daemon-mode

Hi Brad, Am 17.06.2016 22:09 schrieb "Brad King" : > Then I applied the patches with some revisions: > > cmGeneratorTarget: Adopt Fortran module directory generation > https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=49f10f0d > > cmLocalGenerator: Add method to get

Re: [cmake-developers] daemon-mode: Infrastructure

Hi Brad, Am 17.06.2016 22:24 schrieb "Brad King" : > > On 06/13/2016 08:00 PM, Tobias Hunger wrote: > > * There will always be 1 client talking to a server. > > * Client/Server communicate using JSON messages > > Yes. IIRC it is using stdin/stdout (I haven't checked the

[cmake-developers] Imported Locations in FindBoost.cmake

Hi there, I ran into a small issue with the new imported target interface of FindBoost.cmake. Just like the old variable-based interface, the script only detects Debug and Release configurations of installed Boost binaries. In the old interface, the debug binaries where used only for debug

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-414-g828c035

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-412-gfb6d383

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