Hi
I'm suspecting that this block in FindCurses
https://github.com/Kitware/CMake/blob/master/Modules/FindCurses.cmake#L182-L185
should go away, unless there is something I have missed.
if (NOT CURSES_TINFO_HAS_CBREAK)
find_library(CURSES_EXTRA_LIBRARY cur_colr HINTS ${_cursesLibDir})
On 15/11/14 12:36, Gregor Jasny wrote:
the current version now properly checks for proper nesting
of the continue keyword. To detect new scope blocks like
for example a function() I hoked into the Push/PopScope
functions.
I just noticed that return() handling is broken. I'm also
working on a
On 11/15/2014 03:34 AM, Rolf Eike Beer wrote:
Ruslan Baratov wrote:
Done. Also I've found parse issue which is based on `sscanf` behaviour,
e.g. string '123xyz' will be successfully parsed as a integer (%d). Same
issue for example in file(STRINGS) command:
I use strtol()/strtoul() for this
On 11/16/2014 04:12 AM, ゑ wrote:
I tried to 'FIND_PACKAGE(MFC)' on VS2013(community), but MFC not found.
VS2013 has no mfc120.dll but has mfc120u.dll,
so I make a patch for FindMFC.cmake,
This is not just the community edition but any VS 2013. The MBCS
(non-unicode) versions of the MFC
Hi Folks,
Picking up from this old thread:
explicit custom command side-effects (was: Severe regression caused by #14972
fixes)
http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/11207/focus=11225
and this issue:
Add explicit specification of custom command side effect
On 10/08/2014 10:26 AM, Brad King wrote:
Both add_custom_target and add_custom_command can run operations that
produce side-effects. Both commands need a way to specify any side
effects they produce. Perhaps a new option like GENERATES can be
added for this.
For reference in list archives,
Original draft by Doug Barbieri.
Signed-off-by: Gregor Jasny gja...@googlemail.com
---
Help/command/continue.rst | 7 +++
Source/cmBootstrapCommands1.cxx| 2 +
Source/cmContinueCommand.cxx | 21 +
Hello,
the current version now properly checks for proper nesting
of the continue keyword. To detect new scope blocks like
for example a function() I hoked into the Push/PopScope
functions.
I have some questions:
1) The Scope variable stack is held in a 'internal' structure
that gets special
To track the nested loop levels a counter is used.
It gets incremented while entering a loop block
(e.g. foreach or while) and gets decremented when leaving
the block. Because scope borders for example at function
borders must be taken into account the counter is put into
a stack. With every new
Signed-off-by: Gregor Jasny gja...@googlemail.com
---
Help/manual/cmake-policies.7.rst | 1 +
Help/policy/CMP0055.rst| 17 +
Source/cmBreakCommand.cxx | 33 ++
Source/cmPolicies.cxx
FWD to developers list. I think this is a documentation issue.
Luis Felipe Dominguez Vega lfdoming...@estudiantes.uci.cu schrieb am Mon
Nov 17 2014 at 5:42:55 PM:
I can't see into the source code of cmake, into the
cmTargetIncludeDirectoriesCommand.cxx somethink like import the
On 11/17/2014 02:00 PM, Gregor Jasny wrote:
the current version now properly checks for proper nesting
of the continue keyword.
Cool, thanks.
1) The Scope variable stack is held in a 'internal' structure
that gets special treatment in the cmMakefile copy ctor.
I don't know the
Hi there,
First, I would like to thank you for your amazing work on CMake, CPack and
CTest.
I've been trying to make multiple RPMs using components, but it appears
that the component variables such
as CPACK_RPM_componentName_PACKAGE_REQUIRES are not correctly unset.
Worse, they are propagated to
On 11/17/2014 02:09 PM, Daniel Pfeifer wrote:
FWD to developers list. I think this is a documentation issue.
Luis Felipe Dominguez Vega schrieb am Mon Nov 17 2014 at 5:42:55 PM:
I can't see into the source code of cmake, into the
cmTargetIncludeDirectoriesComm__and.cxx somethink
On 11/17/2014 02:46 PM, Gauthier Lamaison wrote:
I've been trying to make multiple RPMs using components, but it appears
that the component variables such as
CPACK_RPM_componentName_PACKAGE_REQUIRES
are not correctly unset. Worse, they are propagated to other components
(that's how I found
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15254
==
Reported By:Jonnhy Fisher
Assigned To:
2014-11-17 21:09 GMT+01:00 Brad King brad.k...@kitware.com:
On 11/17/2014 02:46 PM, Gauthier Lamaison wrote:
I've been trying to make multiple RPMs using components, but it appears
that the component variables such as
CPACK_RPM_componentName_PACKAGE_REQUIRES
are not correctly unset. Worse,
2014-11-17 23:05 GMT+01:00 Domen Vrankar domen.vran...@gmail.com:
2014-11-17 21:09 GMT+01:00 Brad King brad.k...@kitware.com:
On 11/17/2014 02:46 PM, Gauthier Lamaison wrote:
I've been trying to make multiple RPMs using components, but it appears
that the component variables such as
Thanks for the feedback. I made some changes and rebased on the trunk.
The hunk in Modules/CMakeSystemSpecificInformation.cmake is now just removing
a blank line so it should not be needed.
Removed
+message(GHS-DetermineCompiler.cmake)
This looks like a leftover debugging message.
Removed
Gauthier would you also be willing to write a test for this patch?
Sure ! I'll dig into that.
You could extend the test that is already on master branch of git
repository in directory cmake/Tests/CPackComponentsForAll.
MyLibCPackConfig-IgnoreGroup.cmake.in contains the location where you
On 17-Nov-14 18:06, Brad King wrote:
Yes, please change to that so a proper error can be produced for the new
API when 123xyz is given as a timeout, for example.
Function added cmSystemTools::StringToInt
Please look at adding a case to the test suite for this. An outer
process could take the
Hi David,
Can you give me some information on your current setup? What build of VS do you
have installed, which options? I think that the detection logic for the tests
is missing some cases. I'm guessing that this is similar to what I recently
fixed in CMake for the express editions, the same
Hi all,
we want to archive our unittest results, code coverage etc. when we
release a product.
Therefor we want to store the generated XML files in TestLink.
However when we need to look at the results again we need to display
them somehow.
So I have some questions regarding the format:
1.) I
Hi,
I have a project where Qt is used, so I use AUTOMOC.
However I have something special:
My Qt class implementation needs another (external) Qt implemented source, which
I have packed as tar.bz2 file.
I have a rule which shall extract the .tar.bz2 file, which works nicely.
However, the AUTOMOC
That's because the include directory is obtained in dependends. The
documentation say that when the library is imported by dependends of a target,
the dependant target obtain all the PUBLIC and INTERFACE include directories,
so, with the command
target_include_directories(Bar PRIVATE Foo)
Hello!
I'm playing with add_library(OBJECT) operation. Everything works nice
but then I have one library that uses some external library. An
attempt to add target_link_libraries here results in failure, because I
don't build and library, only object files. But now comes the problem,
how do I
Hello,
Just figure it, how cmake can guess that the Bar target depends of Foo
target, you are only telling that add the DIRECTORY Foo to the PRIVATE
INCLUDE_DIRECTORIES of Bar.
Because the docs say so:
Specify include directories or targets to use when compiling a given target..
regards
Hi,
I was able to figure out my first question.
The first two bytes of the binary data was 78 9C.
This is the file header of Zlib data with default compression.
So by adding the correct gzip header manually you can decompress it.
Assume the base64 data from XML is saved in ~/test.base64 you can
Hi,
Today I learned the hard way that cmake does not provide any diagnostic about
unclosed generator expressions.
Consider the following:
add_test(
NAME generator_expression_unclosed
COMMAND
${CMAKE_COMMAND} -E echo $0:Unclosed expression gives a warning?
)
cmake happily accepts this
Hi all,
I am trying to package a set of command line tools and some graphical tools,
sharing the same libraries. Given how Apple wants people to use relocatable
.app bundles, but advises to put command line tools in their usual *nix paths,
I came up with the following intended paths for my
I can't see into the source code of cmake, into the
cmTargetIncludeDirectoriesCommand.cxx somethink like import the
INCLUDE_DIRECTORIES from target passed to target_include_directories, may an
error in the documentation?
---
On Sunday 16
Hi,
after upgrading to cdash 2.2.2 I'm having issues re: the Interactive
Image display for image diffs when there are more than 1 set of images
in a test. Here's an example:
http://visit.cdash.lbl.gov/testDetails.php?test=1028748build=3413
It looks like it may be grabbing the wrong valid
Hey all,
I know that ARGV is all arguments, and ARGN is all arguments past the last
expected argument. I find myself in a weird situation with these, where
identical ARGV's in the same function lead to different ARGN's. The
relevant code in the CMake script is below
FUNCTION(MY_FUNC_NAME
On 11/17/2014 1:44 PM, Joe wrote:
1) How can the same ARGV to the same function give different ARGN's? My
feeling is that the answer is never, it's something in how the MESSAGE
command displays lists.
2) How can we display lists in a way that allows us to see the
differences between them? That
On 11/17/2014 02:09 PM, Daniel Pfeifer wrote:
FWD to developers list. I think this is a documentation issue.
Luis Felipe Dominguez Vega schrieb am Mon Nov 17 2014 at 5:42:55 PM:
I can't see into the source code of cmake, into the
cmTargetIncludeDirectoriesComm__and.cxx somethink
Hey all,
Looks like Bill's got it. Thanks Bill. FYI, this was done as part of doing
parameter sweeps (run tests with all combinations of various parameters and
settings), when it has been made pretty it may get committed back.
Best,
David
On Mon, Nov 17, 2014 at 11:44 AM, Bill Hoffman
Martin Koller wrote:
What rules can I add so that the tar extraction is done BEFORE the moc
generation ?
You can add depends in the AUTOGEN_TARGET_DEPENDS target property of
particular targets.
http://www.cmake.org/cmake/help/v3.0/prop_tgt/AUTOGEN_TARGET_DEPENDS.html
Please try that out.
avo...@mail.ru wrote:
What should I add
to B/CMakeLists.txt to successfully build my executable?
You might be able to add an INTERFACE library and populate its
INTERFACE_SOURCES using the target_sources command:
http://www.cmake.org/cmake/help/v3.1/command/target_sources.html
Hello,
Until recently, I was making use of the 'debug' and 'optimized' keywords to
select the config-specific versions of external dependencies to link in, i.e.
if I wanted to link Bar into Foo, I would use:
target_link_libraries (Foo DEBUG ${Bar_Debug} OPTIMIZED ${Bar_Release})
Now I have
Thanks Brad,
that explains everything.
regards
2014-11-17 20:50 GMT+01:00 Brad King brad.k...@kitware.com:
On 11/17/2014 02:09 PM, Daniel Pfeifer wrote:
FWD to developers list. I think this is a documentation issue.
Luis Felipe Dominguez Vega schrieb am Mon Nov 17 2014 at 5:42:55 PM:
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 c2a87deafe277348e7fba5ffc55d67f7624dce9b (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 545d10cc6793555ab881d27207e4ae378f3caade (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 e943fa8a19a1fbe190e6fe0591d2b509e07b9878 (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 c61efbd684337bafc6388a3e4daff23492d9992d (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, next has been updated
via ffb74d35ace0902289246bb5cd08341effa34cc2 (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 85bafee7eb9a8c9cde16ba5b5099cf33d22d (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, next has been updated
via 29cfa91316a76e6bd5ab5b55bc2d5608bdfa117c (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 350223141073a91c272d303ee45c0d67e15562d3 (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, next has been updated
via 6c3c6fba6665be00517b42bd88554f528d83c072 (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, next has been updated
via 0f0ecd0c41a70e0ffd82ab7f7d15711162adefd5 (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, release has been updated
via 598a316154922f27f987d0f7a78b28ab78a85be6 (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, next has been updated
via f0771cbfc800aa2cba5b25f53eaffac54569a2c7 (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 a42c51b5ab54d8d318f00cf9938ce9fb1e2ac274 (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, next has been updated
via 9c77dc227a7b1505dada93ad9fba777fabc08f8f (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, next has been updated
via f889ba21a6d4688ebeff8cf36e4cd6f9f83f7a26 (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 d903f7ce910879ad5439d642488e508aafd4b049 (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, next has been updated
via 03519a582873578b18afefa74b71a6bab6e4ea02 (commit)
via
20141117)
+set(CMake_VERSION_PATCH 20141118)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
58 matches
Mail list logo
