Nice example, good job.
I'm trying mostly the same.
I don't understand why you want to run test on target platform. I guess
(because tests are platform independent) it is ok to run tests only on host. Or
I miss something?
CppUTest supports also memory leaks detection. When you include (#include
Peter,
i had 2.8.9-pre3 before, i upgraded to 2.8.9. But only after deleting
the CMakeLists user file from qtcreator, deleting the build directory
and restarting qtcreator I was able to get the option to build with Ninja.
Anyway, it seems to work fine now, and the building is much faster.
Awesome!
I was really looking forward to this:
https://bugreports.qt-project.org/browse/QTCREATORBUG-7720
Thank you!
Nils
On 09/17/2012 06:08 PM, Peter Kümmel wrote:
Qt Creator 2.6 is beta now.
On github I've uploaded a patched version with Ninja support for CMake
based projects:
htt
Hi all,
when building a library with CMake, I can decide whether its shared or
static by specifying the appropriate keyword,
ADD_LIBRARY( foobar {SHARED,STATIC} ...)
If this library uses a system library, and if I'm lucky enough that
there's a FindCMake of some sort available for it, I can usual
On a practical matter though: if the file is not listed someplace, then your
IDE may not pick it up. Thus while it is legal to not list all files, it is a
good idea to list them anyway.
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Brett
On 18 September 2012 22:38, David Cole wrote:
> On Tue, Sep 18, 2012 at 5:37 PM, Leif Walsh wrote:
>>
>>
>> On 18 Sep, 2012, at 5:34 PM, Brett Delle Grazie
>> wrote:
>>
>> > Hi,
>> >
>> > Is it necessary to specify header files in add_executable /
>> > add_library entries in CMakeLists.txt?
>>
>
On Tue, Sep 18, 2012 at 5:37 PM, Leif Walsh wrote:
>
> On 18 Sep, 2012, at 5:34 PM, Brett Delle Grazie <
> brett.dellegra...@gmail.com> wrote:
>
> > Hi,
> >
> > Is it necessary to specify header files in add_executable /
> > add_library entries in CMakeLists.txt?
>
> nope
> >
> > i.e. does CMake
On 18 Sep, 2012, at 5:34 PM, Brett Delle Grazie
wrote:
> Hi,
>
> Is it necessary to specify header files in add_executable /
> add_library entries in CMakeLists.txt?
nope
>
> i.e. does CMake automatically do dependency analysis making this unnecessary?
yup
>
> Thanks,
>
> --
> Best Regar
Hi,
Is it necessary to specify header files in add_executable /
add_library entries in CMakeLists.txt?
i.e. does CMake automatically do dependency analysis making this unnecessary?
Thanks,
--
Best Regards,
Brett Delle Grazie
--
Powered by www.kitware.com
Visit other Kitware open-source proj
On Mon, Sep 17, 2012 at 1:02 PM, Glenn Coombs wrote:
> Hi,
>
> I just installed the Visual Studio 2012 Express edition for Windows
> Desktop and cmake 2.8.9 is having some issues with it. Initially when I
> ran the cmake configure step it failed to find the devenv or msbuild
> program:
>
> CMake
On 9/18/12, Stefan Reuschl wrote:
> How do you crosscompile for iOS?
> If using a CMake toolchain you could simply set a variable in that file, I
> which you could check later...
Right now I'm not brave enough to try using CMake for iOS and Android.
I maintain separate projects. But someday I wou
On 9/18/12, Doug wrote:
> Just idly though, I've never yet encountered a situation where:
>
> if(APPLE)
> ...
> elseif(UNIX)
> ...
> endif()
>
> Wasn't sufficient.
I have plenty of these situations :P
The most common case though is that 3rd party dynamic libraries are
not allowed on iOS so g
You're right. It was partly because I had my build tree as a subdirectory
of my source tree. Just used to that from autotools. I also failed to
ignore my .git directory, which also contributed to the slowness. With both
fixed, the speed and tarball size are fine.
Thanks
On Tue, Sep 18, 2012 at 1:
Just idly though, I've never yet encountered a situation where:
if(APPLE)
...
elseif(UNIX)
...
endif()
Wasn't sufficient. The only time I've come close is having to build
automake projects with different flags depending on the os base, and
then (since it only worked under cygwin or msys anywa
As far as I'm aware the only real way to detect OSX itself is by something like:
#if __APPLE__
#include "TargetConditionals.h"
#if TARGET_OS_IPHONE
...
#elif TARGET_IPHONE_SIMULATOR
...
#elif TARGET_OS_MAC
...
#endif
#endif
__APPLE__ is the only constant attached to compiler
15 matches
Mail list logo