Hi all,
Is there a difference in precedence between INTERNAL and STATIC cache
variables?
For example, what happens if I (accidentally) define an INTERNAL cache
variable that is already or will be defined by CMake? Will the STATIC
variable always have precedence? Or am I entering the realm of unde
Hello,
Is there any way to tell cmake to use relative paths when linking an
executable? Here some info about a sample exec:
$ otool -L ./rtmpserver/rtmpserver
./rtmpserver/rtmpserver:
/Users/shiretu/work/crtmpserver/trunk/builders/cmake/thelib/
libthelib.dylib (compatibility version 0.0.0,
With CMake you can do something like:
add_library(foo )
add_executable( bar .. )
target_link_libraries (bar foo)
and CMake will make sure all the link paths are correct. There
generally should not be a need to set the "install_name" of built
libraries _within_ a build tree.
Now, s
> Again, to me it looks like FindSubversion is for *using* Subversion, not
> for building it. As such, setting up include paths and link libraries is
> not appropriate in that module.
Does a naming convention exist for configuration scripts?
How should names be distinguished between scripts which
Is there a way to test if one file is newer than another file? Something
along the lines if "cmake -E compare_files", but for time stamps?
I need to copy dlls into the binary directory, but I want to do it
conservatively. Also I need different versions for Debug and Release, so
add_custom_comman
See also the "IS_NEWER_THAN" clause of the IF command.
http://www.cmake.org/cmake/help/cmake2.6docs.html#command:if
On Fri, Sep 25, 2009 at 1:47 PM, James Bigler wrote:
> Is there a way to test if one file is newer than another file? Something
> along the lines if "cmake -E compare_files", but
I am testing for SSE2/SSE3 functionality and am having some issues
getting things correct.
After I properly detect that SSE2/3 is available I need to set the
COmpiler Flags. For GCC it seems I should use "-msse2" or -msse3
flags. For MSVC it seems I should use /arch:SSE2. So I am trying to
Hi,
I am having intermittent trouble executing
$ cmake -E copy_directory /full/path/to/large/directory /new/path
Originally, the copy_directory was failing deep in my build system
(add_custom_command), but the failure is repeatable from the command line
(exactly as shown above). The failure mes
Sweet. Thanks!
Missed that one after all these years.
James
On Fri, Sep 25, 2009 at 11:53 AM, David Cole wrote:
> See also the "IS_NEWER_THAN" clause of the IF command.
> http://www.cmake.org/cmake/help/cmake2.6docs.html#command:if
>
>
> On Fri, Sep 25, 2009 at 1:47 PM, James Bigler wrote:
>
2009/9/25 Kelly (KT) Thompson :
> Hi,
>
> I am having intermittent trouble executing
>
> $ cmake -E copy_directory /full/path/to/large/directory /new/path
>
> Originally, the copy_directory was failing deep in my build system
> (add_custom_command), but the failure is repeatable from the command li
On Friday 25 September 2009, Marcel Loose wrote:
> Hi all,
>
> Is there a difference in precedence between INTERNAL and STATIC cache
> variables?
>
> For example, what happens if I (accidentally) define an INTERNAL cache
> variable that is already or will be defined by CMake? Will the STATIC
> vari
I am happy to announce that CMake 2.8.0 has entered the beta stage! You
can find the source and binaries here: http://www.cmake.org/files/v2.8/.
I am sure I am leaving something out, but here is the list of changes
that I came up with. (If you notice something missing please let me
know and I wi
On Fri, Sep 25, 2009 at 01:57:26PM -0400, Michael Jackson wrote:
> set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} "-msse3")
> set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} "-msse3")
>
> for NON MSVC compilers and
>
> set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} /arch:SSE2")
> set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /arch:SS
I'm using the NSIS generator to create a package. Is there a CPACK variable
that can be set to add a particular executable to the start menu? I noticed
that the start menu is populated with "uninstall" only.
--
Shane
___
Powered by www.kitware.c
Nope.
I get something like
/G";"/arch:SSE2 as part of the command line options that are set in
the MSVC solution.
_
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Softwarewww.bluequartz.net
On Fri, Sep 25, 2009 at 4:36 PM, Dixon, Shane wrote:
> I’m using the NSIS generator to create a package. Is there a CPACK variable
> that can be set to add a particular executable to the start menu? I noticed
> that the start menu is populated with “uninstall” only.
>
This works for me. Here is
Michael Jackson wrote:
Does it work if you just drop the quotes from the second half of the
set()?
set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} /arch:SSE2)
or, slightly more pedantically:
set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} "/arch:SSE2")
Nope, this variable is a string and not a list.
It has to b
I tried that also and it didn't work either. I am not at my windows
box at the moment to get the exact error. I now have
if (AIMBLADE_USE_SSE)
set_source_files_properties(${SymmetryFilter_SOURCE_DIR}/
FFThread.cpp
${SymmetryFilter_SOURCE_DIR}/
FFNormalizeThread
Hello,
Wow, this is really a surprise. I was not expecting CMake 2.8.0 until
at least mid-2010! What's the expected release date for 2.8.0 final ?
On Fri, Sep 25, 2009 at 10:07 PM, Bill Hoffman wrote:
> I am happy to announce that CMake 2.8.0 has entered the beta stage! You
> can find the source
I was too fast I forgot the list
2009/9/25 Bill Hoffman :
> I am happy to announce that CMake 2.8.0 has entered the beta stage! You
> can find the source and binaries here: http://www.cmake.org/files/v2.8/.
Just built and tested on somes projects.
Awesome, works like a charm.
For those of you wh
Where can I find more info on
- Fortran/C mixed language projects made much easier. CMake now
automatically can compute the run time libraries for a compiler.
Does that mean there is a variable I can use instead of manually specifying
libgfortran, libg2c and others depending on the compiler
On Fri, Sep 25, 2009 at 12:06 PM, Eric Noulard wrote:
2009/9/25 Kelly (KT) Thompson :
> > Hi,
> >
> > I am having intermittent trouble executing
> >
> > $ cmake -E copy_directory /full/path/to/large/directory /new/path
> >
> > Originally, the copy_directory was failing deep in my build system
> >
On Fri, Sep 25, 2009 at 5:31 PM, Pau Garcia i Quiles
wrote:
> Hello,
>
> Wow, this is really a surprise. I was not expecting CMake 2.8.0 until
> at least mid-2010! What's the expected release date for 2.8.0 final ?
>
As soon as the major issues with 2.8.0 rc's are worked out. Nothing
really sho
23 matches
Mail list logo