On 14/06/2013 03:24, Bill Hoffman wrote:
On 6/13/2013 7:35 PM, Alan W. Irwin wrote:
If anyone here is game to do a quick fix for the Ninja generator so
that is supports Fortran, I would be happy to help out by testing the
fix using the build_projects project on the Linux and Wine platforms
On 21/12/12 11:19, Alan W. Irwin wrote:
On 2012-12-21 09:43+0100 Eric Noulard wrote:
2012/12/21 Alan W. Irwin
irwin-ICHe1znInSgulI1VNbnaeCwD8/ffd...@public.gmane.org:
Obviously for my use case it does look like a
reasonable alternative is to use file(GLOB...) followed by a check of
the
On 22/12/12 13:02, Stephen Kelly wrote:
Hi there,
GenerateExportHeader has a bug where if the target name is kde-config, for
example, it generates content like
#ifndef KDE-CONFIG_EXPORT_H
#define KDE-CONFIG_EXPORT_H
This is not as intended. The problem is that the target name is used with
CTEST_USE_LAUNCHERS is a feature that allows better reporting of
compilation errors to a dashboard.
Unfortunately, it only works with the Makefile generator.
Since ninja is significantly faster and just plain better, I use ninja
on all the builders in my test farm.
I'd like to know if there
On 12/10/2012 00:05, Morne' Chamberlain wrote:
Hi
My name is Morné Chamberlain and this is my first post to this list. I
recently started using Sublime Text 2 as a text editor and light
development environment. I use CMake in many of my projects and felt the
need for a Sublime Text 2 project
On 09/12/2012 11:23 PM, Mathias Gaunard wrote:
On 12/09/2012 22:39, Mathias Gaunard wrote:
I'd be content with just interpreting a return value of 77 as a Not
Run status; this is a fairly trivial change that should work well in
any existing setups.
I don't think it is really needed to make
On 09/18/2012 11:37 PM, David Cole wrote:
I don't like it. Existing tests that run and return, for example, a
number of errors that occurred, will magically appear as not run when
that number just so happens to be 77.
If there are enough people who think this is simple and works and are
not
I'd be content with just interpreting a return value of 77 as a Not
Run status; this is a fairly trivial change that should work well in
any existing setups.
I don't think it is really needed to make things as complex as in the
bug report. Any intelligence, if required, can go in the test
I had filed a few bugs that were relatively major, but they were moved
to the backlog. I haven't been able to find the procedure to move them
out of it.
I believe a lot of major bugs were moved to the backlog without their
authors being able to do anything, including bugs with patches ready
I had filed a bug that were relatively major, but they were moved to the
backlog. I haven't been able to find the procedure to move it out of it.
I believe a lot of major bugs were moved to the backlog without their
authors being able to do anything, including bugs with patches ready to
10 matches
Mail list logo
