Hi Brad,
I know that [1] is not supposed to be a "workaround", but the COPY_FILE problem
just does not exist if I try to debug with --debug-trycompile! That's why it
actually IS a workaround :) This was also observed by the user aaron as he
replies in [2]. Therefore I do not have a CMakeError.l
I get the message "CMakePredefinedTarget not available" and then VS
message: "Cannot load CMakePredefinedTarget project".
What does this mean for the work with CMake and VS2010 Express?
Greetings
Micha
___
Powered by www.kitware.com
Visit other Kit
On Thu, Sep 16, 2010 at 7:40 PM, Ryan Pavlik wrote:
> Your "project" command should always be the first or second (after
> cmake_minimum_required) command in your root CMakeLists.txt file, unless you
> have a very good reason.
>
> Then, on the topic of definitions, this is all you need:
> add_defi
Your "project" command should always be the first or second (after
cmake_minimum_required) command in your root CMakeLists.txt file, unless you
have a very good reason.
Then, on the topic of definitions, this is all you need:
add_definitions("-DLIBRARY_NAME=\"${YOUR_CMAKE_VAR_WITH_LIB_NAME}\"")
b
On Thu, Sep 16, 2010 at 6:30 PM, Ryan Pavlik wrote:
> Why are you trying to do this before the project command?
To result in a shorthand that I don't HAVE to copy and paste; because
definition of compiler requirements for passing definitions that are
string literals is lacking?
You can set the
Why are you trying to do this before the project command? You can set the
target name to be something different from the project name, and you can
even set the output name of the executable/library to be different than what
would be automatically set by default from the target name. (I've done
th
I want to define a variablle that I can use later to pass the string
program name or library name so I have something lke...
# have to compare generator because MINGW and CMAKE_COMPILER_IS_GNUCC
are not defined yet...
# would also like to use a more general idea like compier is GCC...
if(CMAKE_GEN
I wanted to try to sneak this into CMake 2.8.3, but I'm not convinced it's
the right fix.
$ENV{ProgramFiles} is "C:\Program Files (x86)" from 32-bit CMake run on
Win64, but it's "C:\Program Files" from 64-bit CMake run on Win64... So to
find "git.exe" we'd need to try both, or determine which one
Hi,
There seems to be very little information online about how cmake handles IDL
files. There is one post on the mailing list <
http://cmake.3232098.n2.nabble.com/Auto-detect-IDL-changes-tp3373183p3377736.html>
which suggests using add_custom_command for running midl, but apart from
that, I couldn
I'm using what is a pretty naive script that does the actual
submission with 'make Nightly' I'll include it at the end of the post.
Using 'ctest -D Nightly'
has the same result.
The quotes on the site and build names are in the
CTestConfiguration.ini They are not quoted in CMakeCache.txt
The bi
Can you point us to a sample script used to submit these dashboard results?
I've never seen dashboard submissions where the "what version of ctest
submitted these results" icon did not show up.
I've also never seen dashboard submissions where the "" appear around the
site names and build names.
Hi Bill,
You are correct. The manifest file is indeed embedded into the binaries.
What confused me was the fact that a .manifest file is also generated, which
is the exact same behavior of Visual Studio when embedding is disabled.
Thanks,
Pedro
On Thu, Sep 16, 2010 at 12:07 PM, Bill Hoffman wro
Consider if you will this dashboard page:
http://testing.psychiatry.uiowa.edu/CDash/index.php?project=BRAINS3&date=2010-09-13
I have several machines submitting Nightly builds to this dashboard
and they all appear to be generating non-empty XML files to upload,
and yet I'm getting blanks where I
On 09/16/2010 05:33 PM, Michael Wild wrote:
>
> On 16. Sep, 2010, at 17:13 , David Aldrich wrote:
>
>> Hi David
>>
>>> Something like this should work:
>>
>>> cmake_minimum_required(VERSION 2.8)
>>> project(MyExe)
>>
>>> add_subdirectory(../Kernel Kernel)
>>> add_subdirectory(../DynLibs DynLibs)
On 09/16/2010 08:11 AM, Molsen, Hannes wrote:
>-- Detecting C compiler ABI info
>CMake Error: Could not COPY_FILE.
> OutputFile: ''
>copyFile:
> 'D:/CCView/binaries/PPC603diab/rat/Framework/CMakeFiles/CMakeDetermineCompilerABI_C.bin'
>
>Unable to find
Hi Michael and David
> True, but some people hate that; We've had this discussion already on this
> list where somebody seemed to be honestly offended by the mere notion of
> an empty dummy file.
I think I can tolerate it ;-)
Thanks for your help.
David
___
On 16. Sep, 2010, at 17:35 , David Cole wrote:
> On Thu, Sep 16, 2010 at 11:33 AM, Michael Wild wrote:
>
>>
>> On 16. Sep, 2010, at 17:13 , David Aldrich wrote:
>>
>>> Hi David
>>>
Something like this should work:
>>>
cmake_minimum_required(VERSION 2.8)
project(MyExe)
>>>
>>
On Thu, Sep 16, 2010 at 11:33 AM, Michael Wild wrote:
>
> On 16. Sep, 2010, at 17:13 , David Aldrich wrote:
>
> > Hi David
> >
> >> Something like this should work:
> >
> >> cmake_minimum_required(VERSION 2.8)
> >> project(MyExe)
> >
> >> add_subdirectory(../Kernel Kernel)
> >> add_subdirectory(.
On 16. Sep, 2010, at 17:13 , David Aldrich wrote:
> Hi David
>
>> Something like this should work:
>
>> cmake_minimum_required(VERSION 2.8)
>> project(MyExe)
>
>> add_subdirectory(../Kernel Kernel)
>> add_subdirectory(../DynLibs DynLibs)
>
>> add_executable(MyExe exe.cxx)
>> target_link_libra
On Thu, Sep 16, 2010 at 11:13 AM, David Aldrich wrote:
> Hi David
>
> > Something like this should work:
>
> > cmake_minimum_required(VERSION 2.8)
> > project(MyExe)
>
> > add_subdirectory(../Kernel Kernel)
> > add_subdirectory(../DynLibs DynLibs)
>
> > add_executable(MyExe exe.cxx)
> > target_lin
Hi David
> Something like this should work:
> cmake_minimum_required(VERSION 2.8)
> project(MyExe)
> add_subdirectory(../Kernel Kernel)
> add_subdirectory(../DynLibs DynLibs)
> add_executable(MyExe exe.cxx)
> target_link_libraries(MyExe Kernel)
I have a problem with add_executable(). Our Kerne
On 9/16/2010 8:39 AM, Pedro d'Aquino wrote:
Hello,
When building my project from Visual Studio 2010, the generated
executables and DLL have their manifest automatically embedded into
them. This does not seem to happen when using nmake (or JOM) - which is
expected behavior, as per
http://msdn.mic
On 16. Sep, 2010, at 14:42 , skippy VonDrake wrote:
> Greetings,
> I have a project most of which is in C but it includes a couple of assembly
> files (.S).
> CMake builds it just fine until I add a preprocessor option meant for gcc -
> and that the assembler
> can't digest.
> Recently I set the
Greetings,
I have a project most of which is in C but it includes a couple of assembly
files (.S).
CMake builds it just fine until I add a preprocessor option meant for gcc -
and that the assembler
can't digest.
Recently I set the COMPILE_FLAGS to include "-H". The compiler did as the
flag specifi
Hello,
When building my project from Visual Studio 2010, the generated executables
and DLL have their manifest automatically embedded into them. This does not
seem to happen when using nmake (or JOM) - which is expected behavior, as
per http://msdn.microsoft.com/en-us/library/ms235591(v=VS.100).as
Hi David,
Thanks for your quick reply and the idea. Unfortunately this does not seem to
be the reason. I am and have always been logged on as an Administrator. But
nevertheless I thought about the permissions idea. Here's what I tried after
your reply:
I copied the complete Project structure l
Thanks Michael
David
> -Original Message-
> From: Michael Wild [mailto:them...@gmail.com]
> Sent: 16 September 2010 12:21
> To: David Aldrich
> Cc: David Cole; cmake@cmake.org
> Subject: Re: [CMake] Question regarding project structure
>
>
> On 16. Sep, 2010, at 13:14 , David Aldrich wr
Hey,
I was wondering whether there was some equivalent to way of getting the
MAKECMDGOALS in the makefile generated by cmake and having targets which
would be dynamic like this
VAR=$(MAKECMDGOALS)
VAREXE=$VAR.exe
$(VAREXE) : DEPEND1 DEPEND2
COMMAND 1
COMMAND 2
is it possible with cm
On 16. Sep, 2010, at 13:14 , David Aldrich wrote:
> Hi David
>
> Thanks very much - I will give that a try. By the way, we are building on
> Linux only.
>
> If I specify compiler flags in my top level CMakeLists file, I guess that the
> lower level ones will inherit those settings and store t
Hi David
Thanks very much - I will give that a try. By the way, we are building on Linux
only.
If I specify compiler flags in my top level CMakeLists file, I guess that the
lower level ones will inherit those settings and store them in their local
caches. Then a lower level CMake may be perfor
On Thu, Sep 16, 2010 at 3:02 AM, Molsen, Hannes
wrote:
> Hello everyone,
>
> Currently I am trying to compile a Software for a PowerPC PPC603 running
> VxWorks. For that I use the Diab-Compilers with mingw32-make on MS Windows
> XP. The makefiles should be created by CMake MinGW Makefile generator
On Thu, Sep 16, 2010 at 6:45 AM, David Aldrich wrote:
> Hi
>
> I have now successfully configured CMakeLists files to create some of our
> static and dynamic libraries using CMake. I would now like some advice on
> how to configure these separate build files as a single project.
>
> Here's what o
Hi
I have now successfully configured CMakeLists files to create some of our
static and dynamic libraries using CMake. I would now like some advice on how
to configure these separate build files as a single project.
Here's what our current folder structure is like:
Trunk --- Kernel <
Hello everyone,
Currently I am trying to compile a Software for a PowerPC PPC603 running
VxWorks. For that I use the Diab-Compilers with mingw32-make on MS Windows XP.
The makefiles should be created by CMake MinGW Makefile generator (I use
Version 2.8.2).
Therefore I started with reading the
34 matches
Mail list logo
