On 06/26/2011 04:12 PM, Owen Shepherd wrote:
On 25/06/2011 07:30, Michael Hertling mhertl...@online.de wrote:
On 06/24/2011 04:16 PM, Owen Shepherd wrote:
I think the appropriate solution here is a project-specific dialect
flag -
perhaps one taking options in the GNU format since it seems
On 06/27/2011 06:34 PM, Todd Gamblin wrote:
On Jun 24, 2011, at 11:30 PM, Michael Hertling wrote:
On 06/23/2011 06:20 PM, Jed Brown wrote:
On Thu, Jun 23, 2011 at 17:50, Michael Hertling mhertl...@online.de wrote:
You need to use a C99 compiler for your project
This is already a problem.
On 06/27/2011 07:07 PM, Rolf Eike Beer wrote:
Michael Hertling wrote:
SET_SOURCE_FILES_PROPERTIES(${CMAKE_BINARY_DIR}/c89.c
PROPERTIES COMPILE_FLAGS ${CMAKE_C_DIALECT_C89})
SET_SOURCE_FILES_PROPERTIES(${CMAKE_BINARY_DIR}/c99.c
PROPERTIES COMPILE_FLAGS ${CMAKE_C_DIALECT_C99})
Sorry about possible double sending, I guess my first mail to this list
didn't come through.
I try to cross compile ppp as an external project. The install command is
INSTALL_COMMAND
make BINDIR=${EXTERNAL_PREFIX}/bin MANDIR=${EXTERNAL_PREFIX}/man
INSTALL='/usr/bin/install
Hi,
I've been using CPack to generate NSIS installers. On my Windows 7 64-bit
development platform this works perfectly. When I started building the release
and generating the packages on our build server (also Windows 7 64-bit) things
aren't quite as smooth. The installer is generated fine,
Hello everybody,
I build a static fortran library using CMake 2.8.0. Once the built is
done I would like to copy the library archive and its related Fortran
mod files stored in say, my_dir1, in another directory say, my_dir2.
Looking on the mailing list and on the web, I tried the following
Hello,
we use CMake to build several libraries and applications for an
embedded Linux target with a cross compile toolchain. Recently we
separated this from one huge source tree to one standalone project for
each library and application, each in its own Git repository. The
classical approach for
Hello everybody,
there is a behaviour I do not understand when using cmake with -D option.
In my project I defined a few CACHE variables. One of them is GUI to
specify whether or not my project should be
built with graphical library support.
So in my main CMakeLists.txt I wrote something
I have just started using some externally supplied cmake projects in my
cmake project. To do this I added these lines to my top level
CMakeLists.txt file:
include(ExternalProject)
ExternalProject_Add(external_proj
PREFIX${CMAKE_BINARY_DIR}/external_proj
SOURCE_DIR
Hi,
I'm currently trying to write a cmake script, which downloads some
source code and compile it during the configuration step. In my case
this I want to try it with BLAS from netlib.org because it represents
the problem in a good way ( and I need it for BLAS and similar
structured source code).
On 07/01/2011 01:48 PM, Martin Köhler wrote:
Hi,
I'm currently trying to write a cmake script, which downloads some
source code and compile it during the configuration step. In my case
this I want to try it with BLAS from netlib.org because it represents
the problem in a good way ( and I
Looking at the following file may be helpful ..
SuperBuild/External_CLAPACK.cmakehttp://viewvc.slicer.org/viewvc.cgi/Slicer4/trunk/SuperBuild/External_CLAPACK.cmake?view=markup
There are also other examples in the
Superbuildhttp://viewvc.slicer.org/viewvc.cgi/Slicer4/trunk/SuperBuild/folder.
Hth
Dear all,
I am trying to change the default behavior of cmake which installs
MODULE to the LIBRARY destination. For example:
...
add_library(test MODULE test.c)
install(TARGETS test
RUNTIME DESTINATION bin
LIBRARY DESTINATION lib
ARCHIVE DESTINATION lib/static
)
...
Will install
Hi all,
I was wondering if there is an easy/automated way that I can get CMake
or CPack to add a license to every source file prior to distribution
of the source. Of course, I mean that I would provide the wording of
the license and all it does is copy this license to the top of each
source file
Sounds like more of a job for perl, python or ruby to me.
On Fri, Jul 1, 2011 at 12:17 PM, Raymond Wan r@aist.go.jp wrote:
Hi all,
I was wondering if there is an easy/automated way that I can get CMake
or CPack to add a license to every source file prior to distribution
of the source.
On Fri, Jul 1, 2011 at 7:23 AM, Glenn Coombs glenn.coo...@gmail.com wrote:
I have just started using some externally supplied cmake projects in my
cmake project. To do this I added these lines to my top level
CMakeLists.txt file:
include(ExternalProject)
ExternalProject_Add(external_proj
Those users have been blocked from our wiki.
Let us know if you see any more suspicious activity.
Thanks,
David
On Thu, Jun 30, 2011 at 7:30 PM, David Cole david.c...@kitware.com wrote:
I have forwarded this to our IT team... Hopefully it's not too hard to
recover from for them.
Thanks,
Hi,
We have a project that has a main executable and dozens of utility executables
that may or may not be needed. We can add an executable for each util with
EXCLUDE_FROM_ALL defined so just typing make only does the main code and
something like 'make grid' compiles the grid generator.
But,
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 89ed078226e89a49ebc86c91165d16b1d0e9df66 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via fe9ac70076c6c7a1c4bf4c841cb3d99e8971 (commit)
from
20 matches
Mail list logo
