Betsubetsu wrote:
I found out that the file CMakeFiles/IsMapVariables.dir/depend.make
generated by version 2.2.3 contains the lines below while the same file
generated by version 2.2.2 generated only the first 2 lines (the
commented ones)!
I noticed that the depend.make file is filled in with
Matt England wrote:
At 4/13/2006 10:42 AM, Matt England wrote:
I see that CMake does provide a single-binary set for all Linux
platforms:
http://www.cmake.org/files/v2.2/cmake-2.2.3-x86-linux.tar.gz
How is this done?
After a few days' posting and research, some references I found follow.
Silvano Imboden wrote:
I am writing (maybe another J) some cmake code
in order to compile the latest wxWindows using Cmake.
The library names should use this form
wx{platform}{version}{unicode}{debug}_{toolkit}.[lib|dll]
In CVS CMake (and soon in the upcoming 2.4 release) you can use
Matt England wrote:
At 4/18/2006 09:43 AM, Brad King wrote:
We have a least-common-denominator Linux system. We build the needed
system libraries statically (such as curses). We build our own gcc
using the --disable-shared configure script option to avoid getting a
shared C++ library
Matt England wrote:
At 4/18/2006 11:56 AM, Brad King wrote:
I think it's a Mandrake 10 box.
There is a bit of a trick needed for CMake due to support for loaded
commands. We link statically against everything but libc and libdl.
In order to work with the system libc on every other machine
Karr, David A (Titan) @ TITAN wrote:
From: Kristian Nielsen [EMAIL PROTECTED]
This generates the following long line in mysqld.vcproj:
I have not yet encountered the line length limit in Visual Studio, but I
have found the length of the directory list makes it hard sometimes to
debug problems
Phillip Hellewell wrote:
Why does CMake version 2.4.0 cause VS7 to compile header files?
That's really weird. I don't even understand what it means to compile a
header file, but sure enough, it is doing it. I think VS7 is dumb for
trying to compile a header file, but I know it never had
Carlos Capdepon wrote:
What I have to do to my CMakeLists.txt files to have this tree:
/build
/build/bin
/build/lib
And names of the debug and release files are equal but adding a d in
the names of debug files.
You can change the names, but you cannot remove the per-configuration
Xavier Delannoy wrote:
hi all,
it would be great to have the '-C' option
example :
cmake -E tar xvzf mytar.tgz -C mydestdir
Feature requests may be submitted here:
http://www.cmake.org/Bug
For now try this:
cmake -E chdir mydestdir cmake -E tar xvzf /path/to/mytar.tgz
-Brad
Lin, Lan wrote:
I have a strange problem for configuring ITK using CMake. This
has been done successfully before I reinstall the windows system. Today
I try to do this, but there is a problem. I use CMake 2.2.3-win32, and
ITK toolkit2.4.0.
Here is what I do. I put ITK in the
Michael Biebl wrote:
Hi all,
I got project where I create a lib (libfoo) and a binary (bar) where
bar links against libfoo.
If I run objdump -p bar on the uninstalled binary in $builddir/src I
get RPATH=$builddir/src.
If I run make install the resulting binary still has RPATH set to
Xavier Delannoy wrote:
Hi all,
I use cmake 2.3 (KDE release).
I'm not able to force /MD in release build and /MDd in debug build. here is how I proceed:
in my CMakeLists.txt
IF(WIN32)
SET(PLATFORM_C_FLAGS /W3 /MD /O2 /Gs)
SET(PLATFORM_C_FLAGS_DEBUG /W3 /MDd /Zi /Od)
Xavier Delannoy wrote:
Brad King [EMAIL PROTECTED] wrote:
Xavier Delannoy wrote:
I use cmake 2.3 (KDE release).
I'm not able to force /MD in release build and /MDd in debug build. here is how I proceed:
Is this a C or C++ project file? If it is C++ you need to use
CMAKE_CXX_FLAGS* instead
Alexander Neundorf wrote:
Hi,
how does CMAKE_INCLUDE_CURRENT_DIR behave ?
Let's say I do
SET(CMAKE_INCLUDE_CURRENT_DIR ON)
in my toplevel src/CMakeLists.txt.
If a src/sub1/CMakeLists.txt contains
add_executable(hello main.cpp)
src/sub1/ will be part of the include path.
Axel Roebel wrote:
Thanks, in fact I found the problem!
It is due to the repeated call of CollapseFullPath () which is used to
determine the current absolute path cmDependsC.cxx
for each dependency file with absolute path.
This call is extremely costly on the mac. And it seems completely
Christian Lang wrote:
Then link them together into an executable:
ADD_EXECUTABLE(exe ...)
TARGET_LINK_LIBRARIES(exe ${START_WHOLE_ARCHIVE} ${SOURCE_LIBS}
${END_WHOLE_ARCHIVE} ${LIBS})
where SOURCE_LIBS are the static libs built in step one and LIBS are
some shared libs. (START_WHOLE_ARCHIVE
Christian Lang wrote:
Christian Lang wrote:
Alexander Neundorf schrieb:
my first problem is solved: To link against foo/libbar.a, the link
line options -Lfoo -lbar are produced. This works. But what if for
some reason I do not want to use it this way, but want to directly
specify
Axel Roebel wrote:
I just tried the cpack program. It failed when executing
a post_install_script which is configured to access the installed libraries
and to rename them. Unfortunately this seems to be required if one wants to
install a static and a shared library of the same name.
In CMake
Reggie Burnett wrote:
I've discovered the problem. the cmakelists.txt files, as they sit on
my system, have lowercase names. When I change them to mixed case
(CMakeLists.txt), they work. Given that Windows is not case sensitive,
this is baffling. I have had SFU installed on this system and
Reggie Burnett wrote:
Brad King wrote:
Reggie Burnett wrote:
I've discovered the problem. the cmakelists.txt files, as they sit
on my system, have lowercase names. When I change them to mixed case
(CMakeLists.txt), they work. Given that Windows is not case
sensitive, this is baffling
Alexander Neundorf wrote:
The following CMakeLists.txt:
include_directories( foo ${CMAKE_CURRENT_SOURCE_DIR}/bar)
add_executable(hello main.c)
produces the flags:
gcc ... -I/home/alex/src/test/bar -Ifoo
I would have expected that foo is also interpreted as relative to
Alexander Neundorf wrote:
Von: Brad King [EMAIL PROTECTED]
Alexander Neundorf wrote:
I would have expected that foo is also interpreted as relative to
CMAKE_CURRENT_SOURCE_DIR, but apparently it isn't.
Bug or feature ?
It's a bug. This is just another command that hasn't been
Brandon J. Van Every wrote:
How can I make a file depend on a target? I have a lexer SILEX.EXE that
I generate. I need other files to depend on the existence of SILEX.EXE,
so that I can lex and create new output. It seems like
target-depends-on-target is dealt with, and
Michael Biebl wrote:
On 5/15/06, Xavier Delannoy [EMAIL PROTECTED] wrote:
it's possible with CMake greater to 2.3.4. I used two diferent
destination directories for the static and shared libs.
Thanks Xavier for this detailed (and lengthy) instructions. But they
are way too complicated and
Laurentiu Nicolae wrote:
My project requires the generation of DLLs and executables with
different postfixes for different configurations. Therefore I am setting
the config_OUTPUT_NAME accordingly. However, when I try to add a
post-build step to the build (as described in the manual), the
Steve Johns wrote:
Is this right-click procedure available in MS VS .NET 2003, do you
know? If so, I'm not clear on where to find it.
Yes, it is. If you look at the Solution tab and select any target,
such as ALL_BUILD, use the + to open the target. There is a
CMakeLists.txt file listed.
Steve Johns wrote:
CMake considers upper-case C to be a C++ extension by default
because is a common convention on UNIX, and Windows is
case-insensitive. Try adding the files like this:
ADD_LIBRARY(NRC206 addint.c ...)
Thanks for the suggestion.
I tried this, but the result was still:
Steve Johns wrote:
Once it is implemented properly you could do something like
SET(NRC206_SRCS ADDINT.C ...)
SET_SOURCE_FILES_PROPERTIES(${NRC206_SRCS} PROPERTIES COMPILE_LANGUAGE C)
ADD_LIBRARY(NRC206 ${NRC206_SRCS})
to override the default choice of compile language for capital .C
Brandon J. Van Every wrote:
What I really want is a simple text substitution macro, of the form:
MACRO(SIMPLE_SCM_TO_C root)
${VALID_CHICKEN} ${Chicken_SOURCE_DIR}/${root}.scm -output-file
${Chicken_BINARY_DIR}/${root}.c ${CHICKEN_FLAGS})
ENDMACRO(SIMPLE_SCM_TO_C)
[snip]
If there's no way
Brandon J. Van Every wrote:
DEPLIST(chicken build chicken-ffi-macros chicken-more-macros tweaks)
SIMPLE_SCM_TO_C(chicken)
You could take advantage of variable macro arguments. The token
${ARGN} will be replaced by arguments beyond those explicitly named.
Try something like this (untested):
Laurentiu Nicolae wrote:
Hi all,
I just noticed that the postfix I use for the debug build is not used
for the pdb and idb files. Namely, I get:
QBase_D.dll
QBase_D.exp
QBase_D.ilk
QBase_D.lib
QBase.idb
qbase.pdb
I'm guessing this should be fixed in the generator. Note also that the
pdb file
frederic heem wrote:
The pwlib library has recently changed its linux debug flags to -g3 -ggdb -O0,
it is believed that it makes debugging easier, is there a way to integrate it
into cmake ?
What do you mean by integrate it into cmake?
If you want to build a project with these flags just
Michael Biebl wrote:
what's the the correct way to do the following:
1) Compile and install a binary foo to /usr/bin/foo
2) Create a link /usr/bin/bar - /usr/bin/foo
3) On make uninstall remove /usr/bin/foo and /usr/bin/bar
For 1+2, I used
SET_TARGET_PROPERTIES(foo PROPERTIES
Asmodehn Shade wrote:
I am using Cmake to find few dependencies for some personal projects.
I setup correctly the CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH to get all my
SDL_* dependencies found and working fine.
But I also in my script do a simple : FIND_PACKAGE(OpenGL)
And when doing a
Thomas Zander wrote:
On Friday 26 May 2006 16:28, you wrote:
If you only want to build a target, then run make targetname/fast it
will skip all of the depend steps, and only build that target.
Doesn't seem to work here on my 2.4-p2
Try it in the top level instead of the subdir. It looks
Thomas Zander wrote:
On Friday 26 May 2006 16:24, you wrote:
I am not sure I understand what you want to type to do the build?
williamMake would do; of wmake if you want. :)
Bottom line; I don't care what the name is as long as it _can_ be made
more usable. Which is impossible with make.
Steve Johns wrote:
Excellent! Thanks very much for this info.
I'm seeing a problem, though.
CMake is not finding my config file, even though it does exist.
CMake announces its search with forward-slash paths, but I'm in the VS
C++ IDE.
Is CMake not actually looking for:
Steve Johns wrote:
What is the exact CONFIGURE_FILE call you are using?
Here it is, cut and pasted:
IF(CMAKE_CONFIGURATION_TYPES)
# Handle multi-configuration generators.
FOREACH(config ${CMAKE_CONFIGURATION_TYPES})
CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/traps_config.txt,
Doug Henry wrote:
actually, I have found if I change the following entry (add expat to the
linker flags) in cmxmlrpc/CMakeLists.txt this problem goes away:
TARGET_LINK_LIBRARIES(xrtest cmXMLRPC cmexpat expat ${CMAKE_DL_LIBS})
From where is that other expat library coming? I bet the build of
Doug Henry wrote:
Has there been any resolution to this issue? I receive a variety of
mod.proxy errors when compiling fortran using cmake 2.4.2.
No one has had time to investigate the problem.
-Brad
___
CMake mailing list
CMake@cmake.org
Ben Larson wrote:
Is the correct way to tell MSVC6 to build a release version of my
project to use the command SET (CMAKE_BUILD_TYPE Release) in the
CMakeLists.txt file?
No. CMAKE_BUILD_TYPE is used to select the configuration for
single-configuration generators such as Makefiles. The VS6
James Mansion wrote:
I'd like to create a library from a mix of
assembler and C files.
I'm reading the book to try to determine how
to achieve this. There seems to be perhaps two
possible approaches.
(Initially this is for Win32, and I have files for NASM
and MASM with extensions .nasm and
Jan Woetzel wrote:
is there a way to compile/link only the libs (ADD_LIBRARY)
but skip linking the executables (ADD_EXECUTABLE)
using a global option/switch on cmake level?
I want to save compilation time when I need only the libraries for
linking my client project.
But we have about 200
Dan White wrote:
Hi all,
Doing an OSX VTK build on intel core duo platform
OSX10.4
Cmake 2.4 patch2
VTK CVS yesterday
trying to use intel compilers for OSX intel
ccmake . configure changes intel compiler selection from icc back to
gcc! Why? Anyone know?
also it changes icpc back to g++
Thomas Zander wrote:
btw; does that include a /fast on install?
Good idea.
-Brad
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Brandon J. Van Every wrote:
I have investigated, and I'm not convinced that the -ldl is coming from
my code. My code is:
CHECK_INCLUDE_FILE(dl.h HAVE_DL_H)
IF(HAVE_DL_H)
ADD_DEFINITIONS(-DHAVE_DL_H)
SET(EXTRA_LIBS ${EXTRA_LIBS} ldl)
ENDIF(HAVE_DL_H)
There is no dl.h on any hard drive of
Brandon J. Van Every wrote:
Brad King wrote:
Brandon J. Van Every wrote:
I have investigated, and I'm not convinced that the -ldl is coming
from my code. My code is:
CHECK_INCLUDE_FILE(dl.h HAVE_DL_H)
IF(HAVE_DL_H)
ADD_DEFINITIONS(-DHAVE_DL_H)
SET(EXTRA_LIBS ${EXTRA_LIBS} ldl)
ENDIF
Brandon J. Van Every wrote:
I need some stylistic advice on handling global state. I'm starting to
break my monolithic CMakeLists.txt up into subdirectories. I'm building
the Chicken compiler and I need to do staged builds. A lot of
essentially the same operations, done on itself multiple
Brandon J. Van Every wrote:
I suppose CACHE INTERNAL docstring is for if I want to pass
values back up from the subdirectories, or across subdirectories?
See GET_DIRECTORY_PROPERTY to get variables from subdirs.
-Brad
___
CMake mailing list
Jan Woetzel wrote:
Brad King wrote:
IF(BUILD_EXAMPLES)
Thanks Brad,
that's almost the approach we currently use except
IF (BUILD_EXAMPLES OR BUILD_TESTING)
for ctest ADD_TEST executable targets.
However,
we are not satisfied with this approach because:
(1) If someone has built only
Alexander Neundorf wrote:
Ok, we need a solution here.
Now that cmake is going to enter the center stage :-) things are going to
change in this regard.
Until now cmake comes with FindFoo.cmake modules for all other software packages.
Once other software packages will also use cmake as their
frederic heem wrote:
It has been suggested to use the following command to set different debug
compiler flags:
SET(CMAKE_CXX_FLAGS_DEBUG -g3 -ggdb -O0 CACHE STRING Debug options.)
Unfortunately, it no longer works with cmake 2.4.2. It is ignored, only -g is
present.
Did this work in any
Alexander Neundorf wrote:
In this solution FindFoo.cmake contains only a few lines like
find_path(QtDBUS_DIR FindQtDBUS.cmake PATHS ...)
if(EXISTS ${QtDBUS_DIR}/QtDBUSConfig.cmake)
include(${QtDBUS_DIR}/QtDBUSConfig.cmake)
else(EXISTS ${QtDBUS_DIR}/QtDBUSConfig.cmake)
# ...report not
Alexander Neundorf wrote:
Hi,
although cmake now supports RPATH very flexible, we still have a problem.
The install RPATH has to be constructed manually. In KDE we set it to the Qt
libdir, the KDE libdir and the install libdir.
Now the problem is, what to do if the app links to a library which
Patrick Noffke wrote:
I'm using cmake 2.4.2 on windows, with Visual Studio 2005 Express Edition.
I have a Qt class in a subdirectory from my top-level project. I don't want to
build the class as a library, but rather include the source code in the
top-level project. But I can't get moc to
Bennett Smith wrote:
Hello,
I am trying to use cmake for building a project on Windows. This
project is currently built using Visual Studio 6.0, and it uses the
ATL libraries to produce some COM components. Part of this is the
invocation of the MIDL compiler to process a file with the .IDL
[EMAIL PROTECTED] wrote:
hi, all
I am using GUISupport/Qt come with the vtk5.0 and try to compile with
cmake but get the following error message:
CMake Error: Error in cmake code at
/home/me/vtk/VTK/GUISupport/Qt/CMakeLists.txt:183:
INSTALL_TARGETS called with incorrect number of arguments
Bernd Schubert wrote:
Hello Alex, hello Brad,
thanks a lot for your help.
You are trying to put the build tree of the try-compile test on top of
the main build tree. Try this:
Ah, I begin to understand.
TRY_COMPILE(C_MAKE_COMPILER_WORKS
${CMAKE_BINARY_DIR}/CMakeTmp
Manuel Klimek wrote:
Hi,
i'm trying to use cmake with g++ to build template using code
with -frepo for shared libraries.
With -frepo g++ automatically includes the object code only for
template instantiations that are needed at link time. If
you link an executable with g++, say
g++ -frepo -o
Alexander Neundorf wrote:
Attached you can find a patch against current cvs which adds an option with the
nice name CMAKE_USE_EXTERNAL_RPATH_FOR_INSTALL, which if enabled has the effect
that lib dirs which are outside the build- and source tree are added to the
install RPATH.
Okay, I've
Vikas Kumar wrote:
I understand that it is currently not possible.
But take the case where you as a software product developer, are given
a proprietary .dll/.so file and you are creating a library that links
with that file.
If ld -o foo.so -static bar.so foo.o , can be written in a
makefile
Filipe Sousa wrote:
The fallowing code is making me crazy. I can't understand why the output is
always FALSE
MACRO(FOO1 x)
IF(x)
This is the same as writing
IF(x)
outside the macro.
MACRO(FOO2 x)
IF(${x})
This is the same as writing
IF(hello)
outside the macro.
MACRO(FOO3
Alexander Neundorf wrote:
Would it be possible to apply it also to the 2.4 branch, but maybe keep it
undocumented until it has proven its usefulness ?
I can test it on my machine, but it can get wider testing (KDE) only if it goes
into the 2.4 branch.
We'll merge it to the 2.4 branch for the
Karl Merkley wrote:
Does CPack have any ability to help with the install_name_tool on the
Mac? Mac applications avoid DLL hell by creating an application bundle
that is really a directory structure that includes the application, the
resources, and the shared libraries used by the
Karl Merkley wrote:
On Jun 16, 2006, at 11:47 AM, Brad King wrote:
Karl Merkley wrote:
Does CPack have any ability to help with the install_name_tool on
the Mac? Mac applications avoid DLL hell by creating an
application bundle that is really a directory structure that
includes
Vikas Kumar wrote:
Hi
Is there a way that I can change compile flags based on the target I
am building. I have played around with all the cmake command options
given and I am kinda out of ideas. So it seems that the CmakeCache.txt
variables are my only hope. But I do not have enough knowledge
Vikas Kumar wrote:
Hi
There is a difference in the way these two versions handle the
installation part.
Here is the snippet from the cmake_install.cmake file generated with
cmake-2.4.2.
IF(NOT DEFINED CMAKE_INSTALL_PREFIX)
SET(CMAKE_INSTALL_PREFIX /home/vikas/installer/)
ENDIF(NOT DEFINED
Philippe Poilbarbe wrote:
Hello,
I am trying to compile fortran code under Windows.
When the Fortran language is enabled, the fortran checking routine shows
the following error:
Determining if the Fortran compiler works failed with the following output:
nmake -f
Andrew Maclean wrote:
Bill, If you think it is generally OK and useful to people, tell me what
improvements are needed before it would be eligible for inclusion in the
modules directory of CMake.
This will definately be a useful contribution.
I have had a go at writing a FindBoost.cmake file
Daniel Sands wrote:
I have some static libraries and need to link them into my CMAKE
project's shared libraries. Is there a platform-independent way to
specify this? What I want can be expressed by the following:
g++ -shared -o libmylib.so my_obj_files.o -Wl,-whole-archive
-lmy_static_lib
Vikas Kumar wrote:
I agree.
But even though I do not set the install prefix with a trailing /,
the leading slash becomes necessary. That REGEX expression is
generated anyway, and the fault is not with the REGEX expression. The
fault is with the fact that I need to add a leading slash if i use
Jan Woetzel wrote:
Jan Woetzel wrote:
The REQUIRED flag checking in
FIND_PACKAGE(Foo REQUIRED)
is not checking the result of FOO_FOUND anymore.
[snip]
In 2.0.6 each find script just had to set _FOUND and the FIND_PACKAGE
command was handling teh rest automatically.
I cannot find any code
Steve Johns wrote:
Hi.
I have a project that links to an external library that I've build
successfully (in MSVC 7.1) using
LINK_LIBRARIES()andLINK_DIRECTORIES()
in my CMakelists.txt file.
When I delete one or both of these directives, the project still
builds! I don't see how it
Steve Johns wrote:
I'm wondering, could someone kindly explain the relationship between the
.vcproj and .vcproj.cmake files (in the MSVC build environment)?
I understand that the .vcproj is the actual project file as used by the
MSVC IDE, but what is the purpose of the .vcproj.cmake file
Hans J. Johnson wrote:
Cmake Experts,
I am running into a problem with static libraries and conflicting frameworks
on MacOSX. I need to statically build my own version of tcl and tk with X11
bindings and link it to my application. The problem is that the linker is
preferring to bind to the
Jan Woetzel wrote:
Miguel A. Figueroa-Villanueva and I rewrote the find script for
wxWidgets (formerly known as wxWindows).
The work is based on Jorgen Boddes FindwxWin.
Great, thanks. Please submit the files in a feature request on the bug
tracker:
http://www.cmake.org/Bug
Thanks,
-Brad
William A. Hoffman wrote:
At 11:09 PM 6/24/2006, Hans Johnson wrote:
Thanks for all your suggestions. They put me onto the correct path to
figuring out what was going on. Close inspection of the man page for ld on
MacOSX indicates why the strange behavior was occuring.
-search_paths_first
Scott Amort wrote:
Hello,
I am in the process of converting my C++ library project from autotools
to CMake. So far, things are working very well. However, I have come
across a strange problem. I have written a cmake module that attempts
to detect if ANTLR is installed, by checking
David Somers wrote:
For a cmake project, it it possible to get a list of all its targets; and for
the targets to get their dependencies?
There is no official interface for this. You could try using
get_cmake_property to get the CACHE_VARIABLES property. Look for
variables of the form
Scott Amort wrote:
Hi Brad,
Thanks for the quick response.
Brad King wrote:
What is the output value of antlr-config --libs? What is the command
you are using to store the value in the cache?
The output value is: /usr/lib64/libantlr.a on my AMD64 gentoo box. I'm
not doing anything
David Akdikmen wrote:
Success with latest from CVS!!! Both make and make install seems to
work, Thanks,
Great.
I added the option by setting the environment variables before running
configure.
(At the bash prompt before running configure)
export CFLAGS=+p
export CXXFLAGS=+p
What was the
Kris Dekeyser wrote:
Hi,
I was running my build macros in the latest CMake (2.4.2) and encountered very strange errors. With some debug printing I discovered that the new CMake version behaves differently regarding RegEx testing compared to the version 2.0.6 that we currently use.
This is a
Jan Woetzel wrote:
Hi,
I expected
INSTALL(FILES subdir/foo.h DESTINATION include )
to install foo.h into
include/subdir but it installs into:
include
Thus the subdirectory structure is lost.
(1) This is a bug or am I missing something ?
It works if I put the approppritae DESTINATION into
Laurentiu Nicolae wrote:
Hello CMake users,
I have noticed that the ExceptionHandling flag is not fully handled for
VC8 projects. Namely, in VC7 this option could only be set to TRUE or
FALSE. In VC8, we have the following options:
Enable C++ exceptions :
No - ExceptionHandling=0
Yes (/EHsc)
David Somers wrote:
On Friday 30 June 2006 19:07, William A. Hoffman wrote:
At 12:26 PM 6/30/2006, David Somers wrote:
BTW, one hiccup I still have is this: for the COMMENT, how can I get it to
print out the $ character?
\$ should work.
That's what I would have expected too... but it
Kris Dekeyser wrote:
I just ran your example with 2.4.2 and got the latter output.
Then, is there any configuration setting that could influence the regex behavior ?
No. Did you build CMake 2.4.2 yourself or use a pre-compiled binary?
-Brad
___
Amitha Perera wrote:
In the VXL project, we use FIND_PACKAGE to allow internal code to use
the public VXL code. As currently set up, this causes a call to
CMAKE_IMPORT_BUILD_SETTINGS, which in turn checks that the internal
project uses the same generator, compiler, and compiler flags as the
Kris Dekeyser wrote:
I'm pretty sure something changed in the the interpretation of variables. I
attached a simple CMakeLists.txt file that shows the difference along with a
configuration file to read in.
Yes, this did change, but the original behavior was not intended or
documented. Note
Remi Denis-Courmont wrote:
Hello,
I am trying to port a project to CMake, but I couldn't find anyway to specify
C preprocessor defines on a per-target (or alternatively, per-source) basis.
The project is compiling the same source files multiple times with different
defines, resulting in
Brandon J. Van Every wrote:
I have put ADD_DEFINITIONS(-DCMAKE_BUILD) in CMakeLists.txt and
statements such as #if !defined(CMAKE_BUILD) in my .h files. Is there a
canonical definition for this? I didn't see any canonical flag being
passed to the C compiler, so I'm guessing there isn't one,
Andriy Rysin wrote:
Hi
I've got a question about PKGCONFIG usage
Let's say I've got SOMELIB_CFLAGS and SOMELIB_LD_FLAGS from PKGCONFIG by
this:
PKGCONFIG(somelib SOMELIB_INCLUDE_DIR SOMELIB_LINK_DIR SOMELIB_LD_FLAGS
SOMELIB_CFLAGS)
I could use
SET(CMAKE_CXX_FLAGS ${SOMELIB_CFLAGS}
Manuel Klimek wrote:
Hi there,
Here's a got a completely reworked version of my patch.
For me this is a killer feature when working with Visual
Studio 2005 and cmake: It automatically generates
workspaces for projects in subdirectories that contain
all required visual studio projects to compile
Alex Makarenko wrote:
High all,
I'm struggling with build configurations in VC-80. I have two specific
questions:
1) Does ${OutDir} get resolved for arbitrary paths (other than to targets)?
E.g. I want to specify the path to a text config file generated during the
build. The cmake command and
Daniel Sands wrote:
I'm not a Fortran programmer, but I have some code to compile into my
program. It came up with false dependencies when I tried to compile it
in the CMAKE framework though. The problem is traced to comment lines
such as
C use cross product of vectors ...
Should a 'use'
Alexander Neundorf wrote:
Hi,
it would be nice if it would be possible to have for each object file also a
target which only preprocesses the file and one which preprocesses and
compiles, but not assembles the file (so that you get the assembler code).
Is there a way to do this with macros ?
John Ellson wrote:
Brad King wrote:
Alexander Neundorf wrote:
Hi,
it would be nice if it would be possible to have for each object file
also a target which only preprocesses the file and one which
preprocesses and compiles, but not assembles the file (so that you
get the assembler code
Steve Johns wrote:
Hi.
What I would like to accomplish:
In the MS VC7.1 .Net IDE
In the Solution Explorer, inside my project's folder, at the same level
as the 'Source Files' folder, I would like to create a 2nd folder
'Include Files' that would contain/display the .hpp files for my
John Ellson wrote:
how do I reference a symbol defined
in CMakeLists.txt in another directory for a list of source files?
e.g. in lib/graph/CMakeLists.txt I have:
SET(graph_SRCS attribs.c agxbuf.c edge.c graph.c
graphio.c lexer.c node.c parser.c refstr.c trie.c
)
and I
Steve Johns wrote:
ProjDir
src
incl
lib
into which directory's CMakelists.txt file should I put the
SOURCE_FILES( Include Files FILES x.hpp y.hpp )
command, and could this:
ADD_LIBRARY( MyLibProj x.cpp y.cpp x.hpp y.hpp )
The source and header files will not magically be
Sagnes, Frederic wrote:
Hello,
I'm using the STLport library on several targets on my project, and need to
define the _STLP_DEBUG flag on the debug configuration of each target. I looked
at :
SET_TARGET_PROPERTIES ( PROPERTIES COMPILE_FLAGS -D_STLP_DEBUG )
... but it doesn't seem to be able
701 - 800 of 15210 matches
Mail list logo
