On 08/13/2010 02:45 PM, J Decker wrote:
On Fri, Aug 13, 2010 at 11:24 AM, Brad King brad.k...@kitware.com wrote:
On 8/12/2010 8:36 PM, J Decker wrote:
cmake -G MinGW Makefiles /test
The path /test is not a valid full path on windows.
yes it is. and the forward slash or backslash
On 8/12/2010 8:36 PM, J Decker wrote:
CMake Error: The source directory C:/build/test does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
Makefile:118: *** [cmake_check_build_system] Error 1
I found it. CMake actually is preserving the path as /test until
the
On 08/13/2010 06:03 PM, J Decker wrote:
Yes, this patch fixes the problem thank you.
Thanks for testing it. I've committed upstream.
-Brad
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
On 08/11/2010 07:04 PM, Andreas Pakulat wrote:
On 11.08.10 16:07:21, Brad King wrote:
What source file is it compiling when it fails to find the header?
reviewpatchdialog.cpp which has #include ui_reviewpatch.h
In what target is its object file?
kdevreviewboard is the target
On 08/18/2010 01:01 AM, Andreas Pakulat wrote:
On 17.08.10 14:53:02, Brad King wrote:
The source file is being compiled in a target that does not
wait for the header to be generated before compiling. We can
add a dependency on the target the does provide the header.
Instead I've added
On 08/18/2010 02:59 PM, Robert Goulet wrote:
I would like to submit the following changes to the cmake repository
until someone finds a better solution.
Looks good. I've put it in 'next':
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e2341226
Thanks,
-Brad
On 08/21/2010 03:31 AM, Claus Klein wrote:
can you please check if this may related also to this BUG:
http://cmake.org/Bug/view.php?id=11153
It happens on Windows only at a root dir.
That looks like the same problem. Please try our nightly build
version cmake-2.8.2.20100819-gc7c6:
On 09/07/2010 04:27 PM, Andreas Mohr wrote:
Or well, ideally there would be a way to have a nice clean chain between
starting CMake execution, realizing that vcproj2cmake needs to process an
update,
_then_ realizing that CMakeLists.txt changed and starting a configure
run, and then
On 09/08/2010 05:47 AM, Marcel Loose wrote:
I would like to inform you that I'm volunteering to become the
maintainer of FindSubversion.cmake.
Thanks! I've updated the wiki page to credit your role:
http://www.cmake.org/Wiki/CMake:Module_Maintainers
It looks like your cmake.git next access
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
On 09/17/2010 03:35 AM, Molsen, Hannes wrote:
In CMakeTestCCompiler.cmake I found a flag called CMAKE_C_COMPILER_FORCED.
This is meant to be set by cross compiling toolchain files that explicitly
set the compiler ABI information. It is not set by --debug-trycompile.
So I still want to get the
On 09/17/2010 07:19 AM, Pere Mato Vila wrote:
I am using the nice feature of exporting targets from one CMake
project to another. This works really nicely since it avoids
explicitly linking my executables and shared libraries with the
dependent libraries of the imported library target. The
On 09/17/2010 09:31 AM, Pere Mato Vila wrote:
The problem I have is that when have already built and
installed B I can not move anymore the location of the A. This
is because the libraries created in B contains the absolute
path to exported libraries in A.
The binaries in B would at most
Hi Pere,
What platform are you using (uname -a)? Does it use ELF binaries?
On 09/17/2010 11:24 AM, Pere Mato Vila wrote:
$ ldd libLHCbMathLib.so
/build/mato/GAUDI/GAUDI_v21r10p1/InstallArea/x86_64-slc5-gcc43-opt/lib/libGaudiKernel.so
(0x2afdec07d000)
...
$ ldd
On 09/17/2010 12:31 PM, Pere Mato Vila wrote:
Thanks for your interest. In fact your questions made me think
in the direction that the problem must be in the way the
library libGaudiKernel.so was built or installed. In fact I
remembered that I have a soft link in the installation
path. The
On 09/17/2010 01:06 PM, Brad King wrote:
In the case of an imported target it checks
for the IMPORTED_NO_SONAME property:
[snip]
Try setting that for your imported target (to value 1). It looks
like this property is missing from the documentation though! I'll
fix that.
Documentation added
On 09/17/2010 06:49 PM, Pere Mato Vila wrote:
You are completely right, the library I was using to import has
no SONAME field. I know exactly what I am doing wrong.
Great. I'm glad you got it working.
Thanks very much for your patience.
You're welcome. It paid off for me because I found
On 09/20/2010 04:45 AM, Molsen, Hannes wrote:
Therefore I don't have a CMAKE_EXECUTABLE_SUFFIX set, because actually I do
not build executables at all.
The real project consists of libraries as libFramework.a.
The builds of the CMake test files stop after assembly, only object files are
On 09/23/2010 12:20 PM, Clinton Stimpson wrote:
I've got a source files for a mixed C/fortran going into one library.
If the library is shared, -lgfortran is added to the link line, and I'm good
to go.
If it is static, -lgfortran is not added to any executable or shared library
that links
On 09/24/2010 12:40 AM, Clinton Stimpson wrote:
If I have these two cmake files
=== CMakeLists.txt
project(prj)
add_subdirectory(sub)
add_executable(main main.cpp)
target_link_libraries(main sub)
===
=== sub/CMakeLists.txt
project(sub C Fortran)
add_library(sub hello.f hello2.c)
===
On 9/28/2010 6:35 AM, Arjen Markus wrote:
for the PLplot project (http://plplot.sf.net) I have tried to use
the Visual Studio 2008 generator in combination with Intel Fortran
(version 11.1). Generating the solution and the project files
works fine, but when I try to build it all, I get error
On 10/05/2010 08:34 AM, Verweij, Arjen wrote:
For some reason bootstrap on a plain SuSE 9.3 fails to find sys/wait.h.
Manually defining HAVE_SYS_WAIT_H to 1 in config.h allows cmake and friends
to be built.
-rw-r--r-- 1 root root 6620 2005-06-11 00:58 /usr/include/sys/wait.h
--
On 11/8/2010 3:54 PM, Allen D Byrne wrote:
The projects do differ in the VFFortranCompilerTool option of the project
file
DEBUG:
AdditionalOptions= /W1 /libs:dll /threads /dbglibs instead of
AdditionalOptions= /dbglibs
RELEASE:
AdditionalOptions= /W1 /libs:dll /threads instead
On 11/09/2010 08:03 AM, Brad King wrote:
I think this regression was an existing bug that was exposed
by the other fix.
It was, and here is the fix to the exposed bug:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3d79e7d5
I also added the runtime library selection flag mapping
Hi Noel,
On 11/16/2010 01:11 PM, K. Noel Belcourt wrote:
I've attached my project's top-level Makefile. I'm trying to force
all the modules in the project to build first so I created a single
library called modules that contains all my Fortran 90 module files.
I'm invoking the
On 11/16/2010 04:24 PM, Belcourt, K. Noel wrote:
which is the same list of libraries in these SUBDIRS commands in the
top-level CMakeLists.txt file (in reverse order). There's a single
library in each of these subdirs of the same lower-cased name.
...
SUBDIRS(Modules)
SUBDIRS(MP)
On 11/16/2010 04:52 PM, Belcourt, K. Noel wrote:
On Nov 16, 2010, at 2:50 PM, Brad King wrote:
On 11/16/2010 04:24 PM, Belcourt, K. Noel wrote:
which is the same list of libraries in these SUBDIRS commands in the
top-level CMakeLists.txt file (in reverse order). There's a single
library
On 11/17/2010 11:32 AM, K. Noel Belcourt wrote:
On Nov 16, 2010, at 3:49 PM, Brad King wrote:
Run make -d to get debugging output. It is *very* verbose but can
tell you why make chooses to run certain rules.
It's definitely related to the presence of the SUBDIRS. Make never
considers
On 11/17/2010 11:51 AM, K. Noel Belcourt wrote:
It's attached.
Hmm..I don't see anything jumping out at me there.
On 11/17/2010 11:32 AM, K. Noel Belcourt wrote:
This works, but moving SUBDIRS(Modules) into it's lexical ordering
fails with the reported error.
Do these libraries have
On 11/17/2010 12:15 PM, K. Noel Belcourt wrote:
On Nov 17, 2010, at 10:02 AM, Brad King wrote:
This tells CMake to print some verbose target dependency
information. I bet it will report modules in a non-trivial
connected component with a bunch of other libraries. Please
send me the output
On 11/22/2010 08:34 AM, Michael Wild wrote:
On 11/22/2010 07:56 AM, ycollette.nos...@free.fr wrote:
I have a fortran project and I use the fortran intel compiler under windows
XP 64 bits with cmake 2.8.2.
I added include(CMakeDetermineFortranCompiler) in my project and the intel
fortran
On 11/22/2010 11:51 AM, Bill Hoffman wrote:
On 11/22/2010 11:18 AM, Verweij, Arjen wrote:
-rdynamic is used for linking with pgf90 even though it is not
supported. The flag is imported from Linux-GNU.cmake and I guess it
is included because cmake (2.8.3) checks for C and C++ compilers by
On 11/22/2010 10:42 AM, ycollette.nos...@free.fr wrote:
I have tried to launch cmake from the visual studio console and from a fresh
dos console in which I set the paths to intel fortran bin directory and the
result is that cmake doesn't detect xilink.
In the first case (visual console),
On 11/29/2010 6:52 AM, Michael Hertling wrote:
Perhaps, this is a good opportunity to ask a related question: Some
time ago, there has been an issue with special linker scripts which
are part of a project. Of course, one would like to see the linker
triggered when these scripts change, and the
On 12/1/2010 9:45 AM, Gary%20G.%20Little%20%40%20comcast wrote:
I have a Visual Studio 2010 solution and I am trying to set the
Configuration Properties - General - Platform Toolset of one
particular project to use V90 to allow this project to build with the VS
2008 tool set. I followed an older
On 12/09/2010 08:06 AM, pellegrini wrote:
I would like to build a Fortran static library using the Lahey Fortran
Compiler.
[snip]
- why the compiler identification is unknown as Lahey compiler is
normally supported by CMake ? Is it really supported ?
As of CMake 2.8.3 there is no support
On 12/10/2010 06:36 AM, Marcel Loose wrote:
Is there a way to let FIND_LIBRARY prefer static over shared
libraries?
I know of one, but that's a bit hack-ish:
SET(CMAKE_FIND_LIBRARY_SUFFIXES .a)
Are there other options?
Ideally, I would like to be able to specify this per library
On 12/15/2010 11:10 AM, Mario Rodríguez wrote:
Intel Fortran Composer 12.0 32b
Not currently supported:
http://www.cmake.org/Bug/view.php?id=11517
Sorry,
-Brad
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
On 12/16/2010 01:07 PM, Campbell Barton wrote:
My question is why this is needed?
set(CFLAG_TEST CFLAG_TEST)
CHECK_C_COMPILER_FLAG(${_FLAG} CFLAG_TEST)
The CHECK_C_COMPILER_FLAG macro stores its result in the CMake cache so
that it persists across multiple runs in the same build
On 12/22/2010 04:21 PM, Cochran, Bill wrote:
So, I guess the problem is cmake is incorrectly guessing my compiler? I'm
not using intel, I'm using gnu.
Both Darwin-GNU and Darwin-icc need the fix.
IIRC, Apple's port of GCC documented the -headerpad_max_install_names
flag as the way pad install
On 01/04/2011 07:44 AM, Martin Nielsen wrote:
Would it be possible to direct CMake to use absolute filenames in the
project files instead of the relative path?
Put the build directory somewhere that is not inside the source directory.
-Brad
___
On 1/12/2011 12:43 PM, David Cole wrote:
Are you using CMake 2.8.3? If not, you should upgrade. There were some
improvements made w.r.t. ctest_update and git repos in that release. I
think the submodule update was one of them...
Among the improvements was the submodule update command:
On 01/13/2011 04:54 PM, Nico Schlömer wrote:
about half a year ago, there's been a discussion here about C++
linking with dependencies to libgfortran present which did not
automatically get resolved. The issue evolved around the Trilinos
toolkit.
I think you're referring to this:
On 1/18/2011 2:12 PM, Nick Kledzik wrote:
When I use cmake to create a Makefile, the resulting main executable
is placed in the build directory tree next to the Makefile.
This is where CMake puts files in single-configuration generators.
When I use cmake to create a xcode project, the
On 01/19/2011 10:32 AM, Tony Goelz wrote:
My apologies in advance if this is not the correct place to start my inquiry.
This is a good place to start. This was discussed briefly:
http://www.cmake.org/pipermail/cmake/2009-August/031688.html
but left off here:
On 01/20/2011 12:22 PM, Alexander Neundorf wrote:
On Thursday 20 January 2011, Michael Wild wrote:
On 01/19/2011 07:24 PM, Alexander Neundorf wrote:
Wow, good summary.
Can you please put that in a wiki page on http://www.cmake.org/Wiki/CMake?
On 01/20/2011 01:36 PM, Alexander Neundorf wrote:
On Thursday 20 January 2011, Brad King wrote:
This all has been documented on the Wiki for years:
http://www.cmake.org/Wiki/CMake_2.6_Notes
It is more of a tutorial/reference format than an example/template though.
Yes, it's just hard
On 01/27/2011 03:08 PM, Clinton Stimpson wrote:
add_library(A SHARED a.cpp)
add_library(B SHARED b.cpp)
target_link_libraries(B A)
set_target_properties(B PROPERTIES LINK_INTERFACE_LIBRARIES )
export(TARGETS B FILE B-exports.cmake)
that gives me an error
export called with target B which
On 2/2/2011 6:10 AM, Micha Renner wrote:
Am Mittwoch, den 02.02.2011, 12:00 +0100 schrieb Emmanuel Blot:
Hello,
How to disable the new warnings CMake 2.8.4-rc2 emits, such as the
following ones?
I support this question too.
There should be a way to switch off this feature of CMake,
On 2/2/2011 9:21 AM, Michael Jackson wrote:
On Feb 2, 2011, at 9:08 AM, Brad King wrote:
cmake --help:
--warn-uninitialized= Warn about uninitialized values.
--warn-unused-vars = Warn about unused variables.
--no-warn-unused-cli= Don't warn about command line
On 02/05/2011 11:33 AM, Johan Björk wrote:
Hi Guys,
I ran into a very similar issue, It seems that CMAKE_TOOLCHAIN_FILE does
not trigger the whatever mark as used code in question, so even if it
actually *does* use the variable, you still get a warning.
Example output:
Hi Johan,
Let's move this over to the developers' list. I'm cc-ing the users' list
just for this transition message. Thanks.
On 02/05/2011 06:50 PM, Johan Björk wrote:
The fix is extremely simple, in cmCTestGIT.cxx:266
char const* git_submodule[] = {git, submodule, update, 0};
modify to
On 03/07/2011 03:59 PM, kent williams wrote:
Looking at the difference between FindITK.cmake in 2.8.3 and 2.8.4 it
looks like someone replaced trusting the ITK_DIR variable and using it
directly if defined, with
FIND_PACKAGE(ITK QUIET NO_MODULE
NAMES ITK InsightToolkit CONFIGS
On 03/08/2011 02:53 AM, Andreas Kelle-Emden wrote:
I set the variable CMAKE_PREFIX_PATH on the command line
so that CMake can find some Config files installed in a
non-standard directory.
The makefile generator prints the following warning:
CMake Warning: The variable, 'CMAKE_PREFIX_PATH',
On 03/07/2011 09:54 PM, Tim Gallagher wrote:
How can I get it to drop the -rdynamic option?
That option appears because the host system name is probably Linux on which
that option is supported. You need to set up a cross-compiling toolchain
file that sets the correct name of the target
On 03/08/2011 11:05 AM, Andreas Kelle-Emden wrote:
It happens every time when I generate the makefile structure with ccmake.
I didn't set the *_DIR variable manually, neither does the CMakeLists.txt.
The culprit might be the fact that I have to configure at least
twice before I can generate on
On 03/10/2011 03:48 AM, Ilias Miroslav wrote:
By default, the current CMAKE_Fortran_LINK_EXECUTABLE consists of several
variables:
CMAKE_Fortran_COMPILER CMAKE_Fortran_LINK_FLAGS LINK_FLAGS FLAGS
OBJECTS -o TARGET LINK_LIBRARIES
[snip]
selected variables only: LINK_FLAGS OBJECTS -o
On 03/08/2011 11:17 AM, Andreas Kelle-Emden wrote:
Am 08.03.2011 17:11, schrieb Brad King:
Does it happen even if you don't pass -D... on ccmake's command line
when regenerating an existing build tree?
No, it runs perfectly on an existing tree.
Okay, I can reproduce this:
$ cmake
Andrew Sayman wrote:
There were other potential ways to resolve the dependencies other than
such a massive static library, but I don't know of a good CMake-style
way to integrate the --start-group and --end-group flags without
resorting to a bunch of really terse coding in my CMakeLists.txt.
Brad King wrote:
Andrew Sayman wrote:
It definitely fixed the problem. Thanks a bunch.
Okay, I'll look at using these everywhere possible by default.
Done:
/cvsroot/CMake/CMake/Modules/CMakeCInformation.cmake,v --
Modules/CMakeCInformation.cmake
new revision: 1.22; previous revision: 1.21
Mathieu Malaterre wrote:
On Mon, Aug 4, 2008 at 4:16 PM, Brad King [EMAIL PROTECTED] wrote:
It definitely fixed the problem. Thanks a bunch.
Okay, I'll look at using these everywhere possible by default.
Does this means 'make VERBOSE=1' will not be verbose anymore ?
No, the archiving rules
Mathieu Malaterre wrote:
I can reproduce my infinite dependencie problem. Every time I type
'make' it redoes the swig step, using cmake 2.4.5 I cannot reproduce
the issue.
How do I track this thing down ? Otherwise steps are simply:
svn co
Mathieu Malaterre wrote:
In order to support -interface, one would need to fix the MACRO in
UseSWIG.cmake:
MACRO(SWIG_GET_EXTRA_OUTPUT_FILES language outfiles generatedpath infile)
GET_SOURCE_FILE_PROPERTY(SWIG_GET_EXTRA_OUTPUT_FILES_module_basename
${infile} SWIG_MODULE_NAME)
Iker Arizmendi wrote:
I've run into some trouble with how CMake 2.4.2 (and perhaps
later) handles the string $ORIGIN when it appears as part of
an RPATH. I've gotten around the trouble (see below), but would
appreciate any pointers on the correct way to use $ORIGIN.
This will work with CMake
[EMAIL PROTECTED] wrote:
might there be a maximum path length limitation in CMake (or perhaps in
nmake)? Trying to compile a library I have to comment out every source
file that leads to a CMakeFiles/... object file with a total path length
of over 200.
Is that a known problem and can I
[EMAIL PROTECTED] wrote:
Here is a directory layout example which produces errors for me (actual names
replaced for confidence reasons)
Thanks for the simplified example and analysis of character counts.
C:\a\bb\CMake_Environment\c\CMakeLists.txt
mentions
Arfrever Frehtes Taifersar Arahesis wrote:
2008-08-06 14:06:47 Bill Hoffman napisał(a):
Arfrever Frehtes Taifersar Arahesis wrote:
Can you do a find in your build tree and find CMakeError.log?
`find -name CMakeError.log` doesn't return anything.
Can you do this:
cmake --debug-trycompile
Andrew Maclean wrote:
Putting it succintly, I want to glob all files in some directory not
part of the cmake source or binary directories and create a variable
containing these files to be copied to the binary build location.
file(GLOB ... ) only seems to work on the current directory.
The
Arfrever Frehtes Taifersar Arahesis wrote:
2008-08-06 21:05:50 Brad King napisa?(a):
The trick is to convince the compiler to put the string in the final
binary. Getting this to happen on all compilers has required a few
iterations. Basically we have to make sure the program return value
Brad King wrote:
[EMAIL PROTECTED] wrote:
Important: Compiling a file in the same directory as
j.cpp but with a three characters longer filename will
compile fine.
That's probably because it pushes it over CMake's 250 character limit
which switches to the md5-hashed
[EMAIL PROTECTED] wrote:
Hi again,
I have some trouble linking to libraries shipped with the sdk.
1. There is a
c:/Symbian/9.2/S60_3rd_FP1/EPOC32/RELEASE/ARMV5/UREL/usrt2_2.lib
[snip]
2. the original linker command produced by the Symbian make system
involves .dso files:
:
temp wrote:
Bill Hoffman wrote:
Ross, Thomas wrote:
That is a new feature of 2.6.X, any library that is linked into
something is included, even if it is excluded from all. The
sub-projects are also now complete. The reasoning is that you could get
incomplete builds if we don't do this.
Rupert Brooks wrote:
1. Does the name of this file appear in a variable somewhere, so that
i can use configure file to write it into the ITKConfig.cmake script.
Previously, there was this
SET(ITK_LIBRARY_DEPENDS_FILE @ITK_LIBRARY_DEPENDS_FILE@)
where ITK_LIBRARY_DEPENDS_FILE is set by the
Rupert Brooks wrote:
One last question. Is there a way to retrieve the list of objects
that have been put in the EXPORT parameter of various install
commands? Basically i would like to use
EXPORT(TARGETS FILE ...)
to get a file in the build directory equivalent to the file i would
Óscar Fuentes wrote:
The script examines library interdependencies dumping the symbol
definitions and references they contain. For this, you need to build the
libraries first. Later on the build, the executables just provide names
of components, the script maps this names to actual libraries
Óscar Fuentes wrote:
thinking on a two-phase build, something like this:
$ cmake -G Unix Makefiles # as llvm-config is not available, the
executables are ignored.
$ make # this builds the libs and llvm-config and stops.
$ make # This implicitly invokes cmake, which now can use
Philip Lowman wrote:
So I submitted a patch to add a new unset() command to CMake. The
command will unset normal or cache variables (causing them to become
undefined). The command also supports unsetting environment variables,
in case anyone has to do that.
The primary use case that drove
Philip Lowman wrote:
So I submitted a patch to add a new unset() command to CMake. The
command will unset normal or cache variables (causing them to become
undefined). The command also supports unsetting environment variables,
in case anyone has to do that.
The primary use case that drove
Alan W. Irwin wrote:
if(FOO)
still gives different results depending on whether there has ever been a
set command executed for the variable.
Really? Can you provide example code demonstrating this?
-Brad
___
CMake mailing list
CMake@cmake.org
Alan W. Irwin wrote:
However, I would like to point out there is still a documentation concern
here.
Yes, I will look at updating the documentation of the set() and if()
commands to address this.
-Brad
___
CMake mailing list
CMake@cmake.org
Philip Lowman wrote:
On Wed, Aug 20, 2008 at 10:54 AM, Brad King [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
The set command already supports unsetting:
set(FOO xyz)
set(FOO) # unsets
if(DEFINED FOO)
message(This message does not appear.)
endif(DEFINED
Philip Lowman wrote:
On Thu, Aug 21, 2008 at 9:01 AM, Brad King [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
However, this:
unset(MY_CACHE_VARIABLE)
should not remove the cache entry. It should only unset the CMake
variable. In order to remove the cache entry, we
Martin Costabel wrote:
Martin Costabel wrote:
[]
Now I only have to find out why another user gets the error
find_package cannot find package FREETYPE because FREETYPE_DIR is
set to /sw/lib/freetype219 which is not a directory containing a
package configuration file (or it is not for the
cyril_wobow wrote:
Unfortunately, there is a showstopper : when it comes to linking, tell
me if I am wrong, there is no way to express which configuration type
should link against which library. In particular, all my configuration
types end up linking against the release version of my 3rd
Brad King wrote:
Use an IMPORTED library. This is supported in CMake 2.6:
add_library(xx_lib STATIC IMPORTED)
set_target_properties(xx_lib PROPERTIES
IMPORTED_CONFIGURATIONS DEBUG;RELEASE
IMPORTED_LOCATION_GUIDEBUG ${XX_DEBUG}
IMPORTED_LOCATION_GUIRELEASE ${XX_RELEASE}
Oops
Yuri V. Timenkov wrote:
On Tuesday 26 August 2008 03:59:04 Brad King wrote:
http://www.cmake.org/Wiki/CMake_2.6_Notes#Importing_Targets
http://www.cmake.org/HTML/cmake-2.6.html#command:add_library
http://www.cmake.org/HTML/cmake-2.6.html#prop_tgt:IMPORTED_LOCATION_CONFIG
http://www.cmake.org
Philip Lowman wrote:
On Mon, Aug 25, 2008 at 9:27 AM, cyril_wobow [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Philip Lowman a écrit :
Does LINK_INTERFACE_LIBRARIES_CONFIG do what you want to do?
See
Philip Lowman wrote:
Ultimately, TARGET_LINK_LIBRARIES() works just fine the way it is with
the debug/optimized keywords satisfying normal use cases. The
debug/optimized keywords are in the lexicon and they aren't going
anywhere. What is the harm in accepting a patch (if a user submitted
Alexander Neundorf wrote:
On Friday 05 September 2008, Yann Cointepas wrote:
1) Why do I need Foo_FIND_QUIET in FooConfig.cmake ?
First, I would like to display a message with the Foo version found if
QUIET is not used.
Okay.
2) Why do I need Foo_FIND_REQUIRED in FooConfig.cmake ?
Alexander Neundorf wrote:
On Friday 05 September 2008, Brad King wrote:
...
Brad, any objections to set these two variables always, also in Config
mode ? If not I can do that if you're not faster.
It doesn't hurt to have them available. Please send me a proposed patch.
See attached.
It also
see it before), is there
any thoughts on an effort to expand this to more than just optimization
and debug flags?
I can not seem to find the bug entry, but there is a long term goal of
having a more feature based set of options. Things like
CMAKE_WARN_LEVEL. Brad King might want to comment
Server Levent Yilmaz wrote:
I have an outdated version of Mastering CMake book (for CMake version
2.2). Referring to section 6.7 Creating a PackageConfig.cmake
file, the configure step contains the following:
GET_TARGET_PROPERTY( GROMIT_LIBRARY Gromit LOCATION )
where Gromit is the
Dieter Rosch wrote:
I've finally had time to play with this a bit.
It turns out that in cmake-2.6.1/Modules/Platform/AIX.cmake, the following
line is missing
SET(CMAKE_C_COMPILE_OBJECT
CMAKE_C_COMPILER DEFINES FLAGS -o OBJECT -c SOURCE)
That is supposed to be set by default in
Óscar Fuentes wrote:
Several libraries depends on a generared header file. For enabling
parallel builds I need to state that dependency, and I do it with
set_source_files_properties. This happens inside a macro:
macro(add_llvm_library name)
if( LLVM_SOURCE_COMMON_DEPENDS )
Luis Ibanez wrote:
If you have got this to work in your local build, please feel free
to commit the changes to ITK. In that way we can test them early
enough before the release of ITK 3.10.
[snip]
Brad for pointing me to this). I'm using CMake 2.6.1 - I THINK its
supported in 2.4, but again,
Rupert Brooks wrote:
Checking this in would
break every test running against a build tree. Not only does this
approach require an install tree, it unfortunately destroys the
ability to link against the build tree. I spent some effort trying to
figure out how to get around this, and i
Wheeler, Frederick W (GE, Research) wrote:
To make sure A.dll is loaded before
B.dll we use the following line in CMake ...
TARGET_LINK_LIBRARIES( A B )
I'm surprised that works. Consider the case when there really is a
dependency. That says that A depends on B, so that B should be loaded
John Giordano wrote:
Hello:
I have been trying desperately to get CMake to configure my system
with no luck.
I am hoping someone can help me.
I have the gcc compiler running as a cross compiler producing code for
a coldfire V2 chip.
The Netburner company has supplied me with
Werner Smekal wrote:
recently I found out (make VERBOSE=1) that when an executable is
compiled with MinGW Makefiles some linker options are in the command
line, which should be in my opinion only necessary for libraries:
-Wl,--out-implib,libtest.dll.a
Alan W. Irwin wrote:
On 2008-10-07 10:22+0200 Martin Apel wrote:
Hi all,
I'm experiencing the following problem with ADD_CUSTOM_COMMAND:
The commands defined for it are executed multiple times, if multiple
targets depend on it and I run a parallel make afterwards.
An example makes this
101 - 200 of 15210 matches
Mail list logo
