Hello,
CMake provides an interface for the addition of subdirectories.
https://cmake.org/cmake/help/v3.9/command/add_subdirectory.html
I find it interesting to clarify details which are not described there so far.
* How much does this item influence the capability to construct a consistent
dep
Hello,
CMake provides an interface for the specification of version information
by the command "project".
https://cmake.org/cmake/help/v3.9/command/project.html
Can it be extended a bit more?
1. How do you think about to preserve a software release tag there?
2. Software packages can often evol
Hello,
A variant of the software generation process is described as "superbuild".
Example:
https://cmake.org/Wiki/ParaView/Superbuild
This article mentions the version "2.8.8" as a software dependency for the
tool "CMake". It refers also to the article "Building External Projects with
CMake 2.8"
Hello,
CMake provides an interface for the specification of version information
by the command "project".
http://www.cmake.org/cmake/help/v3.3/command/project.html
I find that there is a growing need to extend it.
1. How do you think about to preserve a software release tag there?
2. Software p
>> http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_avoid_the_error_.22Arg_list_too_long.22_when_running_make.3F
> so both the means suggested on that page dont apply to us.
> the problem is very specifically for some compiler versions,
> and i was looking for a native cmake solution that /does not/ d
> unfortunately i dont quite understand what you mean with "your tool".
How many efforts would you like to invest so that limitations
around software like a fortran preprocessor can be circumvented?
http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_avoid_the_error_.22Arg_list_too_long.22_when_running
> i've recently run into a problem (both windows/mingw and unix/intel) where
> the cmake-generated build files
> create too long command lines that break the overall build. more precisely,
> the build system uses architecture paths etc
> and hence there are long include directories for many packa
Hello,
CMake provides an interface for sub-projects by
the command "add_subdirectory".
http://www.cmake.org/cmake/help/v3.2/command/add_subdirectory.html
The input and output directories will match by default
and will be automatically created by the build system.
Each directory will usually handl
Hello,
I would like to construct a custom command for the tool "Latexmk".
http://www.cmake.org/cmake/help/v3.2/command/add_custom_command.html
The corresponding Perl script can handle a parameter like "pdflatex".
If I omit the parameter "VERBATIM", the current CMake software
will add backslashes
> Basically package source generator (in the sense of RPM, DEB and alike)
> are unsupported.
I hoped that the CPack software can also help with the corresponding
processing for such data formats.
http://www.cmake.org/Wiki/CMake:CPackPackageGenerators
Do I need to achieve the desired source file a
> For CPack a source generator is a binary generator which is told to package
> a directory which happens to contains the source.
Interesting ...
Do I need to introduce additional options with the prefix "CPACK_SOURCE_"
for the package generators in my build configuration?
> Basically package s
>http://www.cmake.org/cmake/help/v3.0/manual/cpack.1.html
Can it be automatically determined which of the available archive and package
generators
support a distinction between source and binary files?
Regards,
Markus
--
Powered by www.kitware.com
Please keep messages on-topic and check t
>> https://github.com/elfring/OTCL/blob/eca1ed17f70176435c8575eb55a67cca33926905/package_settings.cmake#L1
>
> That may be sufficient for creating a .deb. For integration into Debian, you
> should read
> http://pkg-ocaml-maint.alioth.debian.org/ocaml_packaging_policy.html/
Thanks for your link.
> There is no need for a .src.rpm when you don't embed the build rules into it.
> However, that only makes sense for distributions that have a package
> maintainer for the software,
> creates a source package with all build options and distribution adaptions.
Have you got any more ideas for the f
Hello,
Software package formats like DEB and RPM can help to distinguish
the provided contents between source and binary files.
https://wiki.debian.org/SourcePackage
http://www.rpm.org/max-rpm/s1-rpm-miscellania-srpms.html
How can I achieve a corresponding distinction with CPack?
http://www.cmake
> I actually don't know if this is an omission or a deliberate design choice.
How often do use DEB and RPM package generation with CPack for your software?
Regards,
Markus
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_F
> You could, as a workaround for the problem, define a add_custom_target
> that removes the corresponding rpm/deb packages and just calls 'cmake
> --build --target package' to regenerate them.
Thanks for your suggestion.
> It's not an ideal solution, but it worked just fine for me.
Does this fe
Hello,
I configured a specific software to use the CPack modules to generate
corresponding DEB and RPM packages together with CMake 3 a while ago.
I notice now that package specifications and control files contain
outdated version data after I called the command "make package".
How can I achieve
Hello,
Variables like "CPACK_DEBIAN_PACKAGE_DEPENDS" and "CPACK_RPM_PACKAGE_REQUIRES"
can be set.
Do you know any other package formats where similar settings are supported by
corresponding generators?
http://www.cmake.org/Wiki/CMake:CPackPackageGenerators
Regards,
Markus
--
Powered by www.kitw
Hello,
The build tool "CMake" supports also the data processing for lists to some
degree.
http://www.cmake.org/cmake/help/v3.0/manual/cmake-language.7.html#lists
I notice that CMake scripts are also provided by some software libraries so that
corresponding settings can be automatically determine
> > Would further checks be useful for tools like "as" (GNU assembler),
> "ar" and "ranlib" from the software package "binutils"?
> [...] Do you have an example where it is necessary ?
How do you think about to consider a few more dependencies around the
tool "flexlink" from the software "FlexDLL
> If you want native executables, you can specify it in the CMakeLists for each
> target
> or set the option CMAKE_OCaml_NATIVE to TRUE.
Thanks for your clarification.
> If you mean .mli files, hopefully they are managed.
I would prefer to map the file name for the OCaml interface compiler als
Hello,
The module "CMakeDependentOption" is provided for a while. Is it possible to
establish dependencies between other CMake variables (which are not "options")
in a similar way?
Can a string be automatically forwarded from one variable into parts at other
places during the build configuration?
> https://github.com/ocaml-cmake/ocaml-cmake
How do you think about to extend configuration checks for the OCaml compiler
which generates native code?
Would further checks be useful for tools like "as" (GNU assembler), "ar" and
"ranlib" from the software package "binutils"?
Regards,
Markus
--
Hello,
A wiki article contains some information for the generation of installation
packages.
http://cmake.org/Wiki/index.php?title=CMake:Packaging_With_CPack#Using_CMake_variables_to_configure_CPack
I would like to generate software packages for the following components.
1. Class library
2. Demon
>> How do you think about to extend configuration checks for OCaml compiler
>> variants?
>
> What do you mean by OCaml compiler variants ?
- bytecode
- Will any implementation for native code generation apply also aggressive
software optimisations?
- interfaces
- librarian (linker?)
>> Would y
> https://github.com/ocaml-cmake/ocaml-cmake
I find your contribution very interesting.
How do you think about to extend configuration checks for OCaml compiler
variants?
Would you also like to check for the availability of any package manager?
Regards,
Markus
--
Powered by www.kitware.com
Hello,
I try to generate some files mainly by calls of the command
"add_custom_command". One of them should start with the action to copy a source
file into the build directory.
But I wonder why this step is not written into a generated make file.
I would appreciate your advices.
Regards,
Markus
Hello,
I would like to build a package for a software which was developed in the
programming language "OCaml".
How is the status for the support of corresponding development tools?
Regards,
Markus
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://w
> The application "CMake GUI 2.8.12.2" reports some "internal errors" as I would
> expect it if I dare to use the following setting.
I expected that my example command "configure_file" will fail somehow. But the
shown error messages do not fit to my expectations so far. I suggest to take a
closer
Hello,
A wiki article mentions some details about how parameters are handled for CMake
commands.
http://cmake.org/Wiki/CMake/Language_Syntax#CMake_splits_arguments_unless_you_use_quotation_marks_or_escapes.
I would like to try out the following command with unquoted parameters in a
small build sc
> Perhaps, all headers-only libraries could be handled by the FindBoost module
I would appreciate if corresponding CMake scripts will consider a better
handling for such software.
> and then reported by CMake:
> "Spirit is headers-only, shall not be specified with COMPONENTS"
I would prefer a d
> Boost.Spirit is headers-only library, so there is no binary library supplied.
Thanks for your response.
> It might be not obvious from the manual [1], but COMPONENTS is dedicated
> to request lookup for the Boost libraries which are built as binary
> components.
Can this documentation be imp
Hello,
I try to use a macro call like "find_package(Boost 1.49 REQUIRED COMPONENTS
spirit)". But I get surprised by the following messages despite of a complete
installation from the current source files of this software library.
elfring@Sonne:~/Projekte/Bau/boot_parameters/boost> cmake . -DBoos
>> 1. The target name can be resolved inside the build system. But how should
>> I determine generated file names when I want to refer to them from
>> external sources like installation directories?
>
> Sorry, I don't really understand your question. What generated file names,
> and what external
> How are the chances to find out where and why the desired compilation
> parameter
> gets lost?
Improve myself?
> If I rename the used variable to "FLAGS", the software generation succeeds.
> I would appreciate if my approach will also work with longer variable names
> which can be found more
Hello,
I would like to build some C++ software with the tool "CMake 2.8.11.2-108.1" on
my openSUSE systen.
I have macro calls like the following in a CMake script of a subdirectory.
...
message(STATUS "{T} XFLAG: |${XFLAG}|")
foreach(X
client
...
unix_server_stream)
set(T "${X
> Sorry, I don't really understand your question. What generated file names,
> and
> what external sources ?
I mean with an external source here a directory which is not directly managed
and controlled by the build system. I see installation directories as a
well-known example for the use case w
>> Now I try to give a build configurator the choice with which library type
>> some executable files should be linked. It seems that I need to construct
>> corresponding file names instead of target names.
>
> No, you don't have to.
Thanks for your feedback.
> Do you want to build static and d
Hello,
CMake supports also building of static and shared libraries together.
http://cmake.org/cmake/help/v2.8.11/cmake.html#command:add_library
I get the impression from the tutorial that a needed library can be passed as a
target name for the macro "target_link_libraries".
http://cmake.org/cmake
Hello,
Does the macro "CMAKE_DEPENDENT_OPTION" contain any open issues in its
implementation that should be changed?
http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/CMakeDependentOption.cmake;hb=2cde67a78123a4e59390f7aa2030ea8ff9e206d2
Regards,
Markus
_
Hello,
I tried to use the module "CMakeDependentOption" with the tool "CMake 2.8.4" on
my openSUSE 11.4 system as it is mentioned in the documentation.
http://cmake.org/cmake/help/cmake-2-8-docs.html#command:option
http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/CMakeDependentOption.cmake;
Hello,
I have read the CMake documentation.
http://cmake.org/Wiki/CMake/Language_Syntax#CMake_splits_arguments_unless_you_use_quotation_marks_or_escapes.
Now I find that more parameters should be enclosed by quotation marks.
Examples:
- Frequently asked questions and corresponding answers
${CM
mhh, yeah, thats a good idea. Ok, I'll use this for doing a "STRING( FIND ...)"
:) It was just an idea to share this patch with you, but you're right. Its easier doing
this with regular expressions.
Can it be that your implementation was faster than a complete regex application
for your use c
> I try to generate a cmake project and want to
> build shared and dynamic libraries in one step.
Do you know answers from a wiki?
http://cmake.org/Wiki/CMake_FAQ#Can_I_build_both_shared_and_static_libraries_with_one_ADD_LIBRARY_command.3F
Regards,
Markus
_
> That's it currently.
Is it possible that a field or attribute can specify a format identifier (in the
near future)?
Regards,
Markus
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensour
Am 26.01.2011 17:44, schrieb Alexander Neundorf:
On Wednesday 26 January 2011, SF Markus Elfring wrote:
E.g. cmake --help-full.docbook
gives you a docbook file, which can then be processed further.
The interesting thing is how to get the links into these files initially.
Do you need any
E.g. cmake --help-full.docbook
gives you a docbook file, which can then be processed further.
The interesting thing is how to get the links into these files initially.
Do you need any intermediate format(s) for the desired data exchange?
Regards,
Markus
_
Currently, for formatting the format as described in the readme.txt in the
CMake modules directory is used (i.e. not that much formatting).
Do higher level programming interfaces exist that can work with
message/documentation templates in various file formats?
Regards,
Markus
We already have this bug filed to improve CTest and CPack documentation:
http://public.kitware.com/Bug/view.php?id=10067
I guess that the selection of a proper documentation format is a general problem
for all applications.
Which are your format favourites for CMake components at the moment?
There are links to the "well known by CMake" properties that exist on various
entities: global, directories, targets, tests, files, cache variables.
I have not overlooked the description for them.
I guess that these properties were extended during CMake history. I do not want
to convert this p
No, there is presently no facility for retrieving a list of properties.
Is such a functionality also missing for variable names and their attributes?
Are more software developers interested to query settings only from a subset of
items?
Regards,
Markus
___
No, it does not. Any cross-references are mentioned in text only form and depend
on the end user finding the cross-reference topic.
Would you like to change this situation?
Regards,
Markus
___
Powered by www.kitware.com
Visit other Kitware open-sourc
Much to my surprise, there was only a single "CMAKE_MATCH" on our
whole documentation page. It would make sense to document the variables
CMAKE_MATCH_0 and friends explicitly. And cross-referencing left, right, north
and south would also be good.
Does the current documentation format support det
Hello,
Various properties can be queried by the command "get_property".
http://cmake.org/cmake/help/cmake-2-8-docs.html#section_Properties
I am looking for a command in the corresponding programming interface which can
return a list of property names which will be optionally filtered by a regular
Probably that would be pretty difficult to achieve and definitely would
break backwards-compatibility beyond resurrection.
I have got a different opinion. I imagine that a property with a new name can
provide the desired service to retrieve target parameters in a portable way from
the build en
get_directory_property(info COMPILE_DEFINITIONS)
How do you think about an extension for this programming interface?
Would you like to support that target parameters like preprocessor symbols are
queried from the build environment even if they were not set by the CMake
command "add_definition
Thanks for your help to make CMake better,
Is the command variant "string(REGEX REPLACE ...)" completely documented?
Can multiple variables be specified that will receive the data from the
evaluation of subexpressions in the passed regular expression?
Regards,
Markus
Thanks for your help to make CMake better,
How many CMake commands can work with subexpressions in regular expressions?
Are any extensions needed in this application area?
Regards,
Markus
___
Powered by www.kitware.com
Visit other Kitware open-sourc
Why not? That's mostly equivalent to doing it based on -DNDEBUG (which
is automatically defined for Release and MinSizeRel).
I would like to be precise here.
Do any configurations exist in the software development world where the build
type "Release" does not include a definition for this prep
set_source_files_properties(debug_funcs.c PROPERTIES
EXCLUDE_FROM_CONFIGURATIONS "Release;MinSizeRel")
I do not want to exclude this file based on the value of the variable
"CMAKE_BUILD_TYPE". ;-)
I don't think it would make to do this based on preprocessor definitions.
It seems that
You don't seem to understand the difference between CMake-time and Make-
(or build-) time.
I understand that there can be differences between the time of configuration and
the applied generation. I guess that we have got different expectations about
the introspection capabilities of the CMake
For multi-config IDE's you *don't know* whether NDEBUG is defined or not at
CMake-time.
I imagine that the build system could keep control on all passed compilation
parameters if calls for generation commands would be intercepted (by CMake).
Does it get any feedback for changes of this prepro
Why don't you include the check for NDEBUG in in your "debug-sources"?
This is the case already.
The time you'll waste compiling these files will be negligible, and it
would work with mult-config IDE's.
I find this view debatable. I would appreciate if I can express in the build
specificat
Hello,
I know that some source code will only be needed in my example project if the
preprocessor symbol "NDEBUG" is not defined.
This is usual for conditional compilation. The corresponding bit of debug code
calls functions which are implemented in a few other source files.
Now I am looking fo
The bug tracker is meant to help us track what bugs are going to be fixed in the
upcoming releases of CMake.
I have got no problems with this view. I have just dared to submit a feature
request directly.
It is not good as a general discussion mechanism because only a handful of CMake
develo
Here is the code:
I have found and implemented a solution that can extract data from a header file
with the "help" from evaluation of regular expressions.
file(STRINGS "${CPPCHECK_SOURCE_DIR}/lib/library_version.h"
CPPCHECK_BUILD_SPECIFICATION REGEX "^[ \t]*#define[
\t]+CPPCHECK_LIBRARY
"The VS6 IDE does not support definition values with spaces..."
By the way:
How do you think about the bug report "rc.exe error in 2.8.4-rc1 if
ADD_DEFINITITIONS contains definition with space" by Vladislav Vaintroub?
http://public.kitware.com/Bug/view.php?id=11695
Regards,
Markus
___
What would you like it to print?
It depends on the syntax interpretation if the passed quoted parameter will be
processed as a CMake list.
David Cole pointed it out to me that this is not the case if some data are
enclosed by quotation marks.
http://public.kitware.com/Bug/view.php?id=11677#
I hope that the involved technical details can be better resolved in a wider
audience.
Now I would like to show a small script which demonstrates a specific detail in
the wording of an error message that I did not expect in this way.
cmake_minimum_required(VERSION 2.6)
project(Bug11677)
set(
Here is the code:
I have got another idea.
Did anybody try to use the C/C++ preprocessor ("cpp" and eventually including
the compiler) to output a file in a format which is suitable for processing of
this data as a project specification for CMake?
Regards,
Markus
___
Here is the code:
Thanks. - Very nice. :-)
Which software licence does belong to your approach?
Would anybody like to transform your example into an official CMake module?
Regards,
Markus
___
Powered by www.kitware.com
Visit other Kitware open-s
I use a simple text file with the build number, which is tracked under
VCS. During the build I parse it, generate my version header, increase
the number, save it to the file and check it in.
Which (CMake) commands do you use for this approach?
Regards,
Markus
___
Are you using source control?
Yes. - But there are challenges to query content management systems in a
portable way.
I use a combination of version in the main CMakeLists.txt and the svn
rev. Variables from these get into a generated project header file
that is also generated in the main CM
Hello,
I would like the add the CMake approach for software generation to a project. My
project example supports also other build tools.
This has got consequences on the way how informations like version numbers are
shared between these approaches.
The CMake tutorial describes components for
Hello,
My experience with CMake programming is evolving. I try to update some scripts
which were published with the feature request "Add simple CMake build files".
https://sourceforge.net/apps/trac/cppcheck/ticket/1092#comment:5
A concern that I try to tackle as a next step for this software p
> There are no classes in CMake script, only functions and macros.
Would it be useful if object-oriented software development might become
supported by this configuration programming language?
> Most find modules are fairly simple but many of them have their
> quirks. I don't think there's a t
> If you're asking if the module should find "svn.exe" if all you need
> is the subversion libraries, the answer is it doesn't have to. Once
> COMPONENTS have been specified the module can require the user
> specify one to find executables as well. FindImageMagick is a good
> example of this. I
> You could look to FindImageMagick for inspiration. It started as a
> way to find the ImageMagick binary utilities like "convert" and "
> mogrify" but support was added to detect the ImageMagick libraries
> via specifying additional COMPONENTS.
Thanks for your suggestion.
I am also interested
> Again, to me it looks like FindSubversion is for *using* Subversion, not
> for building it. As such, setting up include paths and link libraries is
> not appropriate in that module.
Does a naming convention exist for configuration scripts?
How should names be distinguished between scripts which
> Again, to me it looks like FindSubversion is for *using* Subversion, not
> for building it. As such, setting up include paths and link libraries is
> not appropriate in that module.
How should a module be called which provides all required settings for the
build process?
> I'm not aware of a
> You mean that you have FindSubversion.cmake as part of your
> CMake installation?
Yes. - The configuration script is a part of the package "cmake 2.6.4-29.2"
from the openSUSE build service.
> I don't see any variables defined with those names in the module you
> linked above. What is the que
Hello!
A configuration script on my Linux system contains the following information.
# $Id: FindSubversion.cmake,v 1.2.2.3 2008-05-23 20:09:34 hoffman Exp $
http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/FindSubversion.cmake?revision=1.4&root=CMake&view=markup
I have got the impression tha
83 matches
Mail list logo
