> One cmInstallTargetGenerator seems to install one file only and there
> seems to be one per cmGeneratorTarget. Is that correct? How does the
> installation of targets with multiple artifacts work?
Just to clarify/muddy the waters. Once
https://gitlab.kitware.com/cmake/cmake/merge_requests/574
On 03/23/2017 11:37 AM, Tobias Hunger wrote:
> cmInstallTargetGenerator has std::string GetDestination(std::string
> const& config) const, too, which might have what I need. Unfortunately
> that is not static, so I need to figure out how to get the right
> instance of cmInstallTargetGenerator.
>
On 03/23/2017 12:08 PM, Robert Dailey wrote:
> Crystax NDK (on master branch) has a toolchain.cmake which invokes
> enable_language()
That is not something we expected to be done or intended to support.
A toolchain file should configure information about the toolchain,
not inject functionality
On Thu, Mar 23, 2017 at 10:50 AM, Brad King wrote:
> On 03/23/2017 11:35 AM, Robert Dailey wrote:
>> Thanks Brad. For future reference, are these changes documented
>> anywhere? I searched for "enable_language" in the 3.6 release notes,
>> and there is no 3.6 entry for
On 03/23/2017 11:35 AM, Robert Dailey wrote:
> Thanks Brad. For future reference, are these changes documented
> anywhere? I searched for "enable_language" in the 3.6 release notes,
> and there is no 3.6 entry for policy changes.
The release notes are for new features, deprecations, and major
On Thu, Mar 23, 2017 at 10:33 AM, Brad King wrote:
> On 03/23/2017 11:16 AM, Robert Dailey wrote:
>> I remember around cmake v3.6, the behavior of enable_language()
>> changed so that if you did it too many times, you'd get the error:
>>
>> Language 'C' is currently being
On 03/23/2017 11:16 AM, Robert Dailey wrote:
> I remember around cmake v3.6, the behavior of enable_language()
> changed so that if you did it too many times, you'd get the error:
>
> Language 'C' is currently being enabled. Recursive call not allowed.
>
> I need to implement some backward
On 03/23/2017 11:15 AM, Wesley Smith wrote:
> the solution here is to add something like the VS_GLOBAL_
> prefix or somehow attach custom flags to a target config
> e.g. attach a flag to the Debug|x64 config of target X.
Once could either try to add a property prefix like that
or add dedicated
I remember around cmake v3.6, the behavior of enable_language()
changed so that if you did it too many times, you'd get the error:
Language 'C' is currently being enabled. Recursive call not allowed.
I need to implement some backward compatibility code to check of CMake
version less than 3.6
The only reference I've been able to find to this property is via the
VisualStudio SDK https://msdn.microsoft.com/en-us/library/hh710870.aspx .
It doesn't seem to be part of any compiler configuration. The conclusion
here being that none of the flags in the VS tables map to this XML tag. I
On 03/23/2017 10:41 AM, Wesley Smith wrote:
> Specifically, I'm trying to add these tags:
>
> ..\..\add-in.ruleset
> true
>
> per-config tags are added via Flag arguments,
What are the corresponding command-line flags that these add?
If they appear in `Source/cmVS*CLFlagTable.h` then adding
Hi,
I'm trying to figure out if it's possible to add user defined XML entries
to the project config section of a visual studio file. From what I can see
it's not, but maybe someone here know of a code path I haven't come across.
Specifically, I'm trying to add these tags:
..\..\add-in.ruleset
12 matches
Mail list logo