The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15733
==
Reported By:M. Schneider
Assigned To:
Hi Brad,
I fail on implementing the test cases, I'm not familiar with testing this way
in general. How can we finish this change?
Best regards
Roman
> Am 31.08.2015 um 21:19 schrieb Brad King :
>
>> On 08/31/2015 07:36 AM, "Roman Wüger" wrote:
>> Attached you will find the corrected patch.
>
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15735
==
Reported By:Pavel Solodovnikov
Assigned To:
The first 100 views!
The interest is there (though not great), but where are the questions and
suggestions?
09.09.2015, 21:12, "Konstantin Podsvirov" :
> Hi, Dear Developers!
>
> Want to advertise a development environment that I am developing.
> The emergence of this environment would be impossi
10.09.2015, 16:06, "Curtis Mitch" :
> What is it, really?
>
> Personally I read the email and had no idea, and it didn't make me want to
> follow the link to find out.
By clicking on the link, you will be able to get the installer is the same as
the QtSDK and a few clicks
to get the binaries,
On 09/09/2015 05:48 PM, Gilles Khouzam wrote:
> Even though GetVersionEx is deprecated,
> it is the right way to get the system version, loading ntdll and
> getting RtlGetVersion is not a good practice as those are private
> APIs that could change.
The change was contributed recently:
Windows: F
On 09/10/2015 05:40 AM, Roman Wüger wrote:
> I fail on implementing the test cases, I'm not familiar with
> testing this way in general. How can we finish this change?
We need to have proper testing or the feature will break in the
future. You may not even need the new options. Have you tried
se
10.09.2015, 16:41, "Curtis Mitch" :
>> From: Konstantin Podsvirov [mailto:konstan...@podsvirov.pro]
>>
>> By clicking on the link, you will be able to get the installer is the same
>> as the QtSDK and a few clicks to get the binaries, libraries and linking
>> headers of any of the participating mod
I don't know where to set the variables nor where to set the command line
parameters.
How can I then test that the maximum passed size is 40 bytes and the failed
size is 60 for example?
Where can I produce such test data (test.xml) with the expected size?
Thanks
Best Regards
Roman
> Am 10.09.2
Hi Konstantin,
Thanks for sharing your work with the community.
Given the exhaustive list of modules provided within the installers, I
can appreciate the effort.
That said, as you may know, downloading unsigned binaries to build
applications is not an option for a lot of us.
Here are few initia
On 09/10/2015 10:57 AM, Roman Wüger wrote:
> I don't know where to set the variables nor where to set the command line
> parameters.
> How can I then test that the maximum passed size is 40 bytes and the failed
> size is 60 for example?
> Where can I produce such test data (test.xml) with the exp
On 09/09/2015 12:21 PM, Robert Goulet wrote:
> Here’s the patch to add generator expressions to the install
> command DESTINATION option.
Thanks for the update.
>>This should not be needed if things are factored correctly.
>>Everything in that block already passes "config" through as a parameter.
I've tested it in the visual studio debugger/ide, not as a test case with ctest.
Regards
> Am 10.09.2015 um 17:02 schrieb Brad King :
>
>> On 09/10/2015 10:57 AM, Roman Wüger wrote:
>> I don't know where to set the variables nor where to set the command line
>> parameters.
>> How can I then tes
I know what you mean, sure I have tested it on a developer machine but not as
part of a "ctest unit test". I've tested it on a real world example.
My problem is to add a "ctest unit test case".
> Am 10.09.2015 um 17:06 schrieb Roman Wüger :
>
> I've tested it in the visual studio debugger/ide,
On 09/10/2015 11:11 AM, Roman Wüger wrote:
> I've tested it on a real world example.
>
> My problem is to add a "ctest unit test case".
The patch I last sent earlier in this thread adds a unit test
that produces and reads the Test.xml file. I left a comment:
# TODO: actually check the content
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15736
==
Reported By:Felix Geyer
Assigned To:
Hi, Jean-Christophe Fillion-Robin (the short name?)!
Thanks for Your reply. You gave a lot of valuable advice.
10.09.2015, 17:59, "Jean-Christophe Fillion-Robin"
:
> Hi Konstantin,
>
> Thanks for sharing your work with the community.
I'm glad to be helpful.
Thank You for giving the community su
Brad,
>From my understanding GetVersionEx was causing a nightmare of app
>compatibility issues where developers would make the wrong comparison or
>assumption based on the version and applications would break on new releases.
>I don't know that deprecating the API and making it require a manife
I added an extra line for Mac OS X. So for iOS, the
MACOSX_PACKAGE_LOCATION line adds a "Copy Bundle Resource". For OSX, the
"TARGET ALL" line copies the shader folder to the build folder. Linux &
Windows will probably do the same thing as OSX, and probably Emscripten
too. Android will probably
On 09/10/2015 02:37 PM, Gilles Khouzam wrote:
> I don't know that deprecating the API and making it require a
> manifest was a better solution, but it does require more
> intentional work on the developer before just using the API.
The API should not be deprecated if there is any use case for
whic
On 09/10/2015 03:04 PM, Brad King wrote:
> On 09/10/2015 02:37 PM, Gilles Khouzam wrote:
>> I can split it up in multiple patches if that makes it easier.
>
> Yes, please. That makes review and future reading of history easier
> because we see a commit message associated with each corresponding
>
Brad King wrote:
> Steve,
>
> The topic merged here:
>
> Merge topic 'use-generator-target'
> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6e5953e9
>
> regressed handling of the buildsystem-aware properties.
> I fixed some of the problems and added test cases.
Thanks for those!
> Ho
On 09/10/2015 04:03 PM, Stephen Kelly wrote:
>> One possible fix to the problems is to avoid allowing empty
>> values to be appended at all as is done for non-buildsystem
>> properties.
>
> I'm sure that's possible. Is it acceptable to fix it?
Yes. The inconsistency with non-buildsystem proper
On Thursday, September 10, 2015 16:02:23 Konstantin Podsvirov wrote:
> The first 100 views!
> The interest is there (though not great), but where are the questions and
> suggestions?
the web page is quite short on details...
It's not an IDE, is it a set of scripts ?
Alex
--
Powered by www.kitw
It is set of modules (now tools and libraries) for development and deployment.23:11, 10 сентября 2015 г., Alexander Neundorf :On Thursday, September 10, 2015 16:02:23 Konstantin Podsvirov wrote: The first 100 views! The interest is there (though not great), but where are the questions and suggestio
On 09/01/2015 12:54 PM, Stephen Kelly wrote:
> I made the attached patch to make
> cmState::GetBuildsystemDirectoryParent always return the last snapshot
> for a directory, which will make sense anyway when properties are
> versioned.
Does that make sense for all the other callers of
GetBuildsyste
This patch fixes the issue where on Windows 8 and above, by default the system
version returned is always Windows 8.
More info on this can be found on
http://blogs.msdn.com/b/cjacks/archive/2009/03/27/manifesting-for-compatibility-on-windows-7.aspx
In order for GetVersionEx to work properly, a
Here is the patch for Windows 10 Support which would be issue 15686.
This is dependent on the patch for issue 15674 which is the version detection
change.
>From the commit message:
This change adds support for Windows 10 Universal Applications.
A Windows 10 Universal Application can be targeted
28 matches
Mail list logo
