Am Montag, 13. August 2012, 14:30:36 schrieb Brad King:
> On 08/13/2012 08:35 AM, Brad King wrote:
> > On 08/10/2012 09:27 AM, Brad King wrote:
> >> Since the first step involves making 'master' and 'next' consistent
> >> we plan to disable merge access to 'next' for the first couple days
> >> of n
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=13468
==
Reported By:Viktor Dubrovsky
Assigned To:
Brad King wrote:
> In the future "git blame" may report one of these sweeping
> commits. In that case, change the blame line to
>
> git blame 7bbaa428~1 -- path/of/file/to/blame.txt
You could also tag this commit somehow. 'pre_style_fixup' ?
> We will let this run through dashboard testing ton
Brad King wrote:
> On 06/11/2012 11:27 AM, Brad King wrote:
>> I've started a local topic branch and implemented $<0:...>,
>> $<1:...>, and $. When I get a chance I'll add
>> some of the other queries, documentation, and tests for the
>> generator expression features.
>
> I've been making occasi
Brad King wrote:
> That was specifically for conditionals in generator expressions,
> not the whole feature:
>
>
http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/3615/focus=3965
Right. I was talking about progress on the overall feature which depends on
the conditionals in gene
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13469
==
Reported By:Stefan Eilemann
Assigned To:
Bill Hoffman wrote:
> On 8/13/2012 10:54 AM, Stephen Kelly wrote:
>> Bill Hoffman wrote:
>>
>>> There is a new failure here:
>>> http://open.cdash.org/testDetails.php?test=156059931&build=2506673
>>>
>>
>> Is the output truncated somehow, or is that really all of it?
> I ran it in a debugger, and
On 08/14/2012 02:59 AM, Rolf Eike Beer wrote:
> The first should have done "s/[ \t]+$//", that would have removed the
> trailing
> tab in Modules/NSIS.template.in, line 484.
Thanks. It looks like that was the only case it missed so I just
added it by hand:
http://cmake.org/gitweb?p=cmake.git;
On 08/13/2012 02:30 PM, Brad King wrote:
> Three sweeping style change commits have been merged to 'next':
>
> http://cmake.org/gitweb?p=cmake.git;a=commit;h=7bbaa428
> http://cmake.org/gitweb?p=cmake.git;a=commit;h=77543bde
> http://cmake.org/gitweb?p=cmake.git;a=commit;h=9db31162
>
> The fir
On 08/14/2012 08:50 AM, Brad King wrote:
> Finally I merged the topic back into master:
>
> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=cd3bd232
We've completed the sweeping changes and are ready for normal
development to resume.
After the 2.8.9 release and completion of the development
On 08/14/2012 07:04 AM, Stephen Kelly wrote:
> Why do you think that's not the correct fix?
> Is there really no C compiler available?
> Do you have a backtrace?
> If you comment out the run_tests("C") in the GenerateExportHeader unit test,
> does the problem go away?
As a side effect of the 'n
On 08/14/2012 05:20 AM, Stephen Kelly wrote:
> With that aside, any other feedback on the proposal for qt4_use_modules?
The concept is fine with me. From a quick glance the implementation
appears to be along the right lines. More testing will be needed by
people more familiar with Qt development
On 8/14/2012 7:04 AM, Stephen Kelly wrote:
Why do you think that's not the correct fix?
Not sure...
Is there really no C compiler available?
Do you have a backtrace?
If you comment out the run_tests("C") in the GenerateExportHeader unit test,
does the problem go away?
No commenting all of th
Brad King wrote:
> On 08/14/2012 07:04 AM, Stephen Kelly wrote:
>> Why do you think that's not the correct fix?
>> Is there really no C compiler available?
>> Do you have a backtrace?
>> If you comment out the run_tests("C") in the GenerateExportHeader unit
>> test, does the problem go away?
>
>
On 8/14/2012 10:34 AM, Stephen Kelly wrote:
Thanks. This is something I probably would not have even known to try.
Bill, aside from the above requests I made previously, could you see if this
makes a difference?
I think you have found a bug in the ninja generator. This fixes the crash:
(not s
Hello,
I missed to reply to all, in my reply, and I only found out after
receiving no reply from David even though he's been replying in the list
(so this must be some policy that I'm not aware of). Here goes:
Original Message
Subject: Re: [cmake-developers] ReactOS: Import
Sorry about that -- I did indeed miss that you were asking to chat with me
by IRC or some other IM.
How about just a G+ chat session? Or can you recommend a Mac or Windows IRC
client I could use?
On Tue, Aug 14, 2012 at 11:12 AM, Amine Khaldi wrote:
> **
> Hello,
>
> I missed to reply to all, i
Even better: http://webchat.freenode.net/ would require just a browser ;)
Otherwise this email is a google account too, so if that upper link
doesn't work (I'm AmineKhaldi on #reactos) then we can easily use google
plus chat.
Regards,
Amine.
--
Powered by www.kitware.com
Visit other Kitware
The following issue is now in status NEW (again)
==
http://www.cmake.org/Bug/view.php?id=13204
==
Reported By:Dave Abrahams
Assigned To:
The following issue is now in status NEW (again)
==
http://www.cmake.org/Bug/view.php?id=13162
==
Reported By:Dave Abrahams
Assigned To:
Colloquy http://colloquy.info/downloads.html works well for me.
On Aug 14, 2012, at 10:18 AM, David Cole wrote:
> Sorry about that -- I did indeed miss that you were asking to chat with me by
> IRC or some other IM.
>
> How about just a G+ chat session? Or can you recommend a Mac or Windows IR
The following issue is now in status NEW (again)
==
http://public.kitware.com/Bug/view.php?id=12373
==
Reported By:Jérôme Vizcaino
Assigned To
An update and clarification of one of my simple facts: :-)
- There are presently 1,207 "open issues" in the CMake bug tracker,
but "open" in this number also includes already "resolved" bugs, of which
there are presently 193.
So, really, there are 1,014 open issues that require work to resol
Amine Khaldi wrote:
> Even better: http://webchat.freenode.net/ would require just a browser ;)
>
> Otherwise this email is a google account too, so if that upper link
> doesn't work (I'm AmineKhaldi on #reactos) then we can easily use google
> plus chat.
Yeah, let's do a developer meeting in #cm
2012/8/13 David Cole :
> Hi everybody,
>
> I need your help. In the next week, if you have time.
Done for me.
--
Erk
Le gouvernement représentatif n'est pas la démocratie --
http://www.le-message.org
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.c
This is a good idea.
How many people would join in if we had a CMake "meeting" in #cmake IRC?
What would be the best day of week and time of day to have one?
I know we have strong representation from Europe and East Coast US --
anybody from time zones far away from those...?
On Tue, Aug 14
26 matches
Mail list logo
