Hi,
I didn't time it, but I was able to use ninja with kdelibs and grantlee (my
smaller Qt project).
Clifford Yapp wrote:
> In case anybody else wants to give ninja a spin, here's what I did to
> test it (using bash as a shell):
>
> git clone git://github.com/martine/ninja.git
> git clone -b
On Fri, Jan 06, 2012 at 02:08:24PM -0500, Clifford Yapp wrote:
> Peter,
>
> FYI, I'm seeing a problem with the BRL-CAD build on the Mac with CMake
> + ninja using the latest git versions - when I try to run tclsh, I get
> a problem with it trying to link
> TARGET_INSTALLNAME_DIRlibtcl.8.5.dylib in
On 01/09/2012 07:56 PM, Óscar Fuentes wrote:
> Michael Hertling
> writes:
>
>> On 01/09/2012 02:34 PM, David Cole wrote:
>>> No trick, but to avoid this, perhaps we should change the "--build"
>>> handler to run the cmake configure & generate step before calling out
>>> to MSBuild. You can easily
there are .user files generated by newer versions of Visual Studio (since
2005 I believe) that contain per-machine or per-workspace information. For
all intents and purposes these are temporary files that are not checked
into version control.
The normal file naming convention for these are:
proje
On 2012-01-07 18:16+0100 Bram Kouwenberg wrote:
I'm looking for someone with a mingw32 install next to Cmake. I have a problem
compiling probably because of mingw32 --look below if
you want.
shout out if you have mingw32
Hi Bram:
From time to time on a MinGW/MSYS/Wine platform, I have suce
Thanks Brad. Much appreciated.
I can see that cmake has some relevant properties but I wasn't quite sure how
to set them.
I'll give this a shot.
From: Brad King [brad.k...@kitware.com]
Sent: Monday, January 09, 2012 2:28 PM
To: Mitchell, John A
Cc:
On 1/9/2012 3:44 PM, Mitchell, John A wrote:
add_executable(demo_cf_pointer demo_cf_pointer.F90)
target_link_libraries(demo_cf_pointer I_Fortran -lstdc++)
CMake prefers to use the C++ compiler to link when any C++ is involved.
Some toolchains use a "prelinker" step that actually runs the C++ co
Hi,
I am trying to link a fortran/c++ executable. main() is in the fortran file.
cmake is choosing to "Link CXX executable" rather than fortran executable?
Based upon my current CMakeLists.txt file, cmake is choosing the wrong linker.
I can in fact cut and paste the cmake link line and repla
Some more info. When running cmake I get the following output when looking for
Qt4:
cmake 2.8.7
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - not found.
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found.
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found.
-- Looking for Q_WS
On Mon, Jan 9, 2012 at 1:56 PM, Óscar Fuentes wrote:
> Michael Hertling
> writes:
>
>> On 01/09/2012 02:34 PM, David Cole wrote:
>>> No trick, but to avoid this, perhaps we should change the "--build"
>>> handler to run the cmake configure & generate step before calling out
>>> to MSBuild. You ca
We tried with CMake 2.8.7 and had the same results. I installed on my own
machine and was able to compile successfully so it must be something add with
their setup. I guess. Thanks for the sanity check.
--
Mike Jackson
On Jan 9, 2012, at 2:10 PM, Clinton Stimpson wrote:
> On Monday, January 0
On Monday, January 09, 2012 11:26:15 am Michael Jackson wrote:
> I am having an issue with my project compiling against the Official Nokia
> Qt4 downloaded from Nokia. The issue (I think) is that for some reason
> when FindQt4 is running it determines that QT_USE_FRAMEWORKS is false and
> so I don'
Michael Hertling
writes:
> On 01/09/2012 02:34 PM, David Cole wrote:
>> No trick, but to avoid this, perhaps we should change the "--build"
>> handler to run the cmake configure & generate step before calling out
>> to MSBuild. You can easily do this yourself from the command line by
>> adopting
I am having an issue with my project compiling against the Official Nokia Qt4
downloaded from Nokia. The issue (I think) is that for some reason when FindQt4
is running it determines that QT_USE_FRAMEWORKS is false and so I don't get all
of the proper include directories. Namely the -F/Path/To/F
2012/1/9 Hauke Heibel :
> 2012/1/9 Michael Stürmer :
>> Awesome! Sometimes you just need to know what's already available to solve
>> your problems in a very elegant way. I'll have a look at these bundles and
>> probably switch to them instead of maintaining my own stuff!
>
> When looking at the
2012/1/9 Michael Stürmer :
> Awesome! Sometimes you just need to know what's already available to solve
> your problems in a very elegant way. I'll have a look at these bundles and
> probably switch to them instead of maintaining my own stuff!
When looking at the initial problem, I am pretty muc
> Awesome! Sometimes you just need to know what's already available to solve
> your problems in a very elegant way. I'll have a look at these bundles and
> probably switch to them instead of maintaining my own stuff!
>
Same here. I have spent a few hours writing scripts that keep a list
of neces
Awesome! Sometimes you just need to know what's already available to solve your
problems in a very elegant way. I'll have a look at these bundles and probably
switch to them instead of maintaining my own stuff!
-Ursprüngliche Nachricht-
Von: David Cole [mailto:david.c...@kitware.com]
Ge
Not directly... Not with existing ctest.
But after the ctest_coverage call, there should be a file in your
binary tree called something like "Testing/20120109-0100/Coverage.xml"
-- it is the xml file that will be submitted to CDash reporting what
files have what percent coverage. Near
2012/1/9 Michael Stürmer :
> I have found some topics related to my issue on the web, but none so far
> helped me to fix it:
>
>
>
> I use Visual Studio 2010 on Windows 7 64Bit.
>
>
>
> During my build, all binaries are collected in one folder, which makes it
> easier for me to debug the project. B
Hi,
Did you try FixupBundle from the BundleUtilities module ?
I use it on windows, at install time, to copy all the dll required by an
executable, just next to the executable.
Very usefull to generate a standalone installer. The good thing is that
it introspects your executable (via the window
On 01/09/2012 10:05 AM, Michael Stürmer wrote:
> I have found some topics related to my issue on the web, but none so far
> helped me to fix it:
>
> I use Visual Studio 2010 on Windows 7 64Bit.
>
> During my build, all binaries are collected in one folder, which makes it
> easier for me to de
On Mon, Jan 9, 2012 at 4:11 PM, Michael Jackson
wrote:
> The only issue I really have with this is that this macro requires there to
> be BOTH debug and Release libraries available and will copy BOTH no matter
> which configuration is being built. I am thinking that the
> "yourCopyDlls.cmake" c
I was going to chime in with my own macro:
#
#-- Copy all the Qt4 dependent DLLs into the current build directory so that
#-- one can debug an application or library that depends on Qt4 libraries.
macro (CMP_COPY_QT4_RUNTIME_LIBR
2012/1/9 Hauke Heibel :
> Hi Michael,
>
> What I do is running a custom command which itself executes a CMake
> script. Usually similar to
>
> add_custom_command(TARGET CopyDlls
> COMMAND ${CMAKE_COMMAND}
> -DMSVC_BUILD_CONFIG_DIR=${CMAKE_CFG_INTDIR}
> -DCMAKE_RUNTIME_OUTPUT_DIRECTOR
Hello Hauke,
thanks for the answer! I already got some workaround which is very similar to
your suggestion: as I have this problem only in windows/msvc mode I use a
batch-script now which takes the $ variable as an argument.
Within the bat-script I check the content of %, i.e.
"Release","Debug
Hi Michael,
What I do is running a custom command which itself executes a CMake
script. Usually similar to
add_custom_command(TARGET CopyDlls
COMMAND ${CMAKE_COMMAND}
-DMSVC_BUILD_CONFIG_DIR=${CMAKE_CFG_INTDIR}
-DCMAKE_RUNTIME_OUTPUT_DIRECTORY=${CMAKE_RUNTIME_OUTPUT_DIRECTORY}
On 01/09/2012 02:34 PM, David Cole wrote:
> On Sun, Jan 8, 2012 at 11:59 PM, Óscar Fuentes wrote:
>> When MSBuild.exe is used (typically by "cmake --build") for building a
>> VS2010 project generated by cmake, it correctly invokes cmake for
>> regenerating the project files if changes to the CMake
Hello list,
Is there a way when doing a coverage build and test run(with bullseye)
to make the build fail when the total coverage percentage is below a
certain treshold? for example getting the resulting percentage in your
ctest script after the "ctest_coverage()" call.
Best regards
Tom,
--
On Mon, Jan 9, 2012 at 6:49 AM, Eric Noulard wrote:
> 2012/1/9 Daniel Dekkers :
>> Hi,
>>
>> In Xcode, can I change build settings at "PROJECT" level via CMake?
>> SET_TARGET_PROPERTIES() always seems to work on "TARGETS" level.
>
> What kind of settings?
>
> Properties have a scope:
> - global
On Sun, Jan 8, 2012 at 11:59 PM, Óscar Fuentes wrote:
> When MSBuild.exe is used (typically by "cmake --build") for building a
> VS2010 project generated by cmake, it correctly invokes cmake for
> regenerating the project files if changes to the CMakeLists.txt files
> are detected. However, the bu
2012/1/9 Daniel Dekkers :
> Hi,
>
> In Xcode, can I change build settings at "PROJECT" level via CMake?
> SET_TARGET_PROPERTIES() always seems to work on "TARGETS" level.
What kind of settings?
Properties have a scope:
- global
- directories
- target
- tests
- source files
se
Hi,
In Xcode, can I change build settings at "PROJECT" level via CMake?
SET_TARGET_PROPERTIES() always seems to work on "TARGETS" level.
Thanks,
Daniel Dekkers
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please
--
Message: 2
Date: Sun, 8 Jan 2012 21:52:05 -0700
From: James Bigler
Subject: Re: [CMake] Some issues with visual studio
To: Renato Utsch
Cc: cmake@cmake.org
Message-ID:
Content-Type: text/plain; charset="iso-8859-1"
On Sun, Jan 8, 2012 at 7:29 AM, Renato U
I have found some topics related to my issue on the web, but none so far helped
me to fix it:
I use Visual Studio 2010 on Windows 7 64Bit.
During my build, all binaries are collected in one folder, which makes it
easier for me to debug the project. But to be able to run the program actually,
35 matches
Mail list logo
