Hi,
normally I just do
add_definitions( /wd4996 )
http://www.cmake.org/cmake/help/
cmake2.6docs.html#command:add_definitions
Despite its name you can also add compiler flags. Compile your program
with
nmake VERBOSE=1
so that you can see if the compiler flags was successfully added.
On 10/5/08, Alexander Neundorf [EMAIL PROTECTED] wrote:
On Sunday 05 October 2008, Oliver Dole wrote:
Hello,
I have a link problem with cmake on Linux.
I work on owb, a webkit based browser, which uses cmake as build
system. Here is how my cmake system works:
- build balwtf.a,
2008/10/2 user790 user790 [EMAIL PROTECTED]
Disabling specific warnings is a simple task so I thought I could do it
myself but I must admit defeat. A simple CMakeLists.txt like this won't
work.
project(testcmake)
# None of this works
#set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} /wd4669)
On Fri, Oct 3, 2008 at 1:22 AM, 0xd34df00d [EMAIL PROTECTED] wrote:
2008/10/2 Eric Noulard [EMAIL PROTECTED]:
2008/10/2 0xd34df00d [EMAIL PROTECTED]:
Hi there!
I have a project which consists of main application, few helper
libraries and some plugins, each of them is in its own
Attached is an attempt at a FindPETSc module. Since PETSc is often
linked to many libraries (more than 40, configuration dependent, in many
different directories) it is unreasonable to ask the user to provide all
libs. This module uses PETSC_DIR and PETSC_ARCH (when using the PETSc
build system
Jason Eubank schrieb:
Hello,
I am wondering if it is possible to set the target property
'WIN32_EXECUTABLE' on a per-config basis (i.e. you can set link-flags
on a per-config basis using LINK_FLAGS_Config). From reading the
documentation this does not seem possible and if you set this
Are there any plans or WIP for support XCode 3.0-3.1 projects? To
support the build targets in parallel option.
Also is there an easy way to set the GCC version that is used by the
XCode project? so the projects will use the latest version of GCC
rather then 4.0.
-Neal
CMake should be supporting Xcode through 3.1 when run on Leopard. Are
you having some issues with this?
Xcode will automatically select the best number of compile processes
to use when compiling. There are over rides that you can do using the
defaults system. Google around for them.
With a new-style ctest script like this, you should set CTEST_BUILD_COMMAND
and CTEST_BUILD_FLAGS to specify the make executable and arguments to it if
you need values different than those ctest uses by default. If you set
those, there is no need to set the MAKECOMMAND in the cache.
HTH,
David
The following code is in WXDialog:
SET( wxWidgets_USE_LIBS
std
html adv xml xrc )
FIND_PACKAGE(wxWidgets REQUIRED)
This failed.
I replace std with base core and it configured (though I haven't built it).
Is support for WXDialog current? It's in the source distribution.
Thanks,
James
Hello,
I have come across a problem using CMake with SVN.
I have a src/shaders directory containing files with extension .glsl. I
need to create a rule to copy these files in my build directory, since my
program will need them at runtime.
For now, i have:
ADD_CUSTOM_TARGET( install_shaders ALL
Thanks Stefan, this worked well.
My exact usage using your recommendations was as follows:
if(WIN32)
set_target_properties(WindowApplicationExample PROPERTIES
LINK_FLAGS_DEBUG /SUBSYSTEM:CONSOLE)
set_target_properties(WindowApplicationExample PROPERTIES RELWITHDEBINFO
/SUBSYSTEM:CONSOLE)
12 matches
Mail list logo