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
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
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
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
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
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
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