Hi,
I'm building llvm project with CMake.
While build process is compiling the code I prefer running "make -j3" on my
4 core pc (bumping processor to 100% on 3 of 4 cores and using up ~5 GB of
ram - part of it is system and not build related).
While build process is linking I must run "make" with
On Wed, Aug 1, 2018, 03:46 CrestChristopher
wrote:
> Hi, I'm using CMake for Windows as I was informed that I couldn't use
> `make` as the CMakeLists.txt file was only for CMake.
>
CMake is a meta build system which means that on for example Linux it
henerates make fliles so CMakeLists.txt shoul
2018-07-19 18:00 GMT+02:00 dbegun via CMake :
> I have a project where a lib and a binary requiring the lib are built in
> separate subdirs of the project root. Each dir contains its own
> CMakeLists.txt with build/install targets, and there is also a top level
> one, which mainly just adds subdir
2018-01-04 22:42 GMT+01:00 Sam Lunt :
> Hi Domen,
>
> Thanks for the reply, but that doesn't seem to work for me. I modified
> my example to add this function call:
>
> list(APPEND CPACK_RPM_RELOCATION_PATHS
> ${CPACK_PACKAGING_INSTALL_PREFIX}
> )
>
The documentation states that CPACK_PACKAGI
2018-01-03 22:40 GMT+01:00 Sam Lunt :
> I am trying to set a per-component value for
> CPACK_PACKAGING_INSTALL_PREFIX when using the RPM generator, but I
> haven't been able to do so.
>
> I would like to be able to:
> 1. Install using "make install" (or cmake --build ${BUILD_DIR}
> --target instal
2017-12-16 0:18 GMT+01:00 Saad Khattak :
> Hi,
>
> I have 4 configurations (2 for Debug and 2 for Release) and I would like
> to install the libraries such that they are installed in the correct
> directories.
>
> Installing without worrying about configurations looks like this:
>
> install(TA
2017-12-04 20:35 GMT+01:00 DKLind :
> Domen Vrankar wrote
> > I'm a bit confused. Is there something missing in the patch?
> > Attached patch only adds per component version override - it doesn't even
> > touch the multiple calls to `include(CPack)` and naming of di
2017-12-04 23:17 GMT+01:00 Saad Khattak :
> Hi,
>
> I have an interface library and I am not sure how I would get CMake to
> generate the usual -config.cmake file for the library so that I can
> then use "find_package" on the interface library from an external project.
>
> I am adding (and install
2017-12-04 19:57 GMT+01:00 DKLind :
> Domen Vrankar wrote
> > product_1-component_1-1.0.0
> > product_1-component_2-1.0.0
> > product_2-component_1-3.5.7
> > product_2-component_2-3.5.7
>
> This too is what my patch fixes. Attached is the patch.
>
> CP
2017-12-01 18:04 GMT+01:00 Domen Vrankar :
> 2017-12-01 16:47 GMT+01:00 DKLind :
>
>> This is precisely my situation. I have a large project where 50+ packages
>> are
>> generated. I wanted, needed, to be able to set each packages' version
>> uniquely. Usin
2017-12-01 16:47 GMT+01:00 DKLind :
> This is precisely my situation. I have a large project where 50+ packages
> are
> generated. I wanted, needed, to be able to set each packages' version
> uniquely. Using the CPACK_DEBAIN__PACKAGE_VERSION variable
> seemed
> to be the correct way, except it doe
2017-12-01 5:41 GMT+01:00 Craig Scott :
>
>
> On Fri, Dec 1, 2017 at 11:15 AM, Domen Vrankar
> wrote:
>
>> 2017-11-29 17:07 GMT+01:00 DKLind :
>>
>>> I have finally found time to work on a patch so
>>> CPACK_DEBAIN__PACKAGE_VERSION is recognized. I
2017-11-29 17:07 GMT+01:00 DKLind :
> I have finally found time to work on a patch so
> CPACK_DEBAIN__PACKAGE_VERSION is recognized. I am amazed how
> simple the fix actually is.
>
> I plan on submitting a formal patch soon for Debian and RPM. I don't know
> anything about other CMake packaging fe
2017-07-23 17:19 GMT+02:00 DKLind :
> Also, curious why CPACK_*COMPONENT*__DESCRIPTION is different
> from the other CPACK_*DEBIAN*__PACKAGE_XXX?
>
Most variables are debian package specific/allow to override general CPack
variables specifically for debian packages. For e.g. package description i
2017-07-22 1:55 GMT+02:00 DKLind :
> I have a large project and I need to create a Debian package for each
> sub-project (essentially each add_subdirectory).
>
> I have been experimenting with CPack components as outlined here:
> https://cmake.org/cmake/help/v3.8/module/CPackComponent.
> html?high
>
> I have an application repository that is built with CMake, but
> requires additional/custom handling when packaging -- hence the need
> for a custom .spec file.
Can this not be done from CMakeLists.txt by setting some additional CPACK_*
variables depending on the build environment?
> After
>
> > set(INSTALL_DIR ${CMAKE_INSTALL_PREFIX}/ssp-suite)
> > install(DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}/ssp/" DESTINATION
> ${INSTALL_DIR})
>
Eric already covered this part - use relative paths instead ( no / at the
beginning).
> But I also need to execute a post script, which runs after ins
>
> Transaction check error:
> file /opt from install of ssp-suite-7.1-1.x86_64 conflicts with file
> from package filesystem-3.2-21.el7.x86_64
>
> Error Summary
>
Directory /opt is already owned by filesystem package but is not
listed in CPACK_RPM_EXCLUDE_FROM_AUTO_FILELIST
variable.
Add /opt (
2017-04-03 12:30 GMT+02:00 Volker Enderlein <
volker.enderl...@ifm-chemnitz.de>:
> But when I checked the CPack*Config.cmake files none of the entries above
> are referenced. After running the `cmake -G "Visual Studio 14 2015 Win64"
> ..\TestProject` a second time everything is fine; the entries a
2017-03-31 4:41 GMT+02:00 kipade :
> There are some files I do not want to build if the specified condition was
> ture.
> For example, for testing, I want build a new file witch include a main
> entry just
> for testing; if not, a new file would be compile for normal task.
> I do not want to write
2017-03-08 16:23 GMT+01:00 Bernhard Seckinger :
> Hi Domen,
>
> > This came up in the past and if I recall correctly the only workaround
> was
> > the install(DIRECTORY ... DIRECTORY_PERMISSIONS) that you mentioned.
> Please
> > file a bug report for this one.
>
> Where is the best place to do so?
2017-03-08 10:00 GMT+01:00 Bernhard Seckinger :
> Hi all,
>
> I'm using cpack to generate a debian package. There are two things that
> look
> like bugs in cpack to me (although it might also be, that I got something
> wrong):
>
> a) Files, that I install with install(FILES ...) get the wrong name
2017-02-16 7:59 GMT+01:00 Milan Ziegler :
> Hi,
>
> we are using the CMake install mechanism "install(...)" to copy all
> relevant files and target binaries of the product into the CMake install
> prefix folder, for further packaging. So far so good.
>
> We are also using several thirdparty librar
2017-02-09 12:08 GMT+01:00 Martin Craig :
> Hi, got this problem which I've boiled down to a simple test case. My
> source dir contains just one file (realfile) and the installation should
> install this in bin and make a symlink from linkfile to it. This is the
> CMakeLists.txt file:
>
> cmak
2017-01-18 22:37 GMT+01:00 ardi :
> If anybody has further suggestions, please don't hesitate to tell.
>
Alternative 1:
I usually go with the platform supported packages even if that means having
more than one package format... I prefer less custom dependencies to
one-package-to-rule-them-all log
2016-12-21 12:29 GMT+01:00 Dvir Yitzchaki :
> Thanks, but as I understand a component can only belong to one group.
>
> How can I get the same component/target on multiple packages?
>
Usually you wouldn't want to package same file on same location with same
filename since during unpackaging they
2016-12-20 21:53 GMT+01:00 Paul Londino :
> Hello,
>
> I am trying to create an RPM package using CPack. I am having trouble
> packaging the documentation. There is a custom target that generates
> HTML using DoxyGen (in a folder called html), and this gets installed
> to /usr/doc/share during the
2016-11-15 15:16 GMT+01:00 Christoph Grüninger :
> Hi Domen,
> thanks for your answer.
>
> > > CMake 3.7 compiles so far, but test #379 (RunCMake.CPack_RPM) fails,
> see
> > > the error below from OBS. I had a brief look at our patches and I am
> apt
> > > to think they are unrelated.
> > > Can so
2016-11-12 14:38 GMT+01:00 Christoph Grüninger :
> Dear CMake folks,
> I am trying to package CMake for openSuse. I was a bit surprised that
> the new dependency libuv was nowhere mentioned. Can it be disabled by a
> configure switch for older systems?
>
If I remember correctly libuv is only used
2016-10-25 16:59 GMT+02:00 cen :
>
> Why is patch level not baked into the DEB but it is in RPM? If install the
> deb, soft links have the proper patch level version so I guess it is
> ultimately ok but kinda annoying.
>
Which version of CPack are you using?
I can't reproduce this even with old
Hi,
> I have a very standard CPack configuration for deb package. I have two
> questions:
>
> 1. I generate the deb with: cpack --config CPackConfig.cmake -G "DEB"
>
> This is supposedly a binary package but when I install it on the machine I
> see header files being installed in /usr/include.
>
>
> And now? Do I have to uninstall cmake 3.5 and install it again?
Rebuild (in such cases I usually remove previous build dir as in the
past sometimes it did not detect if a new library was added to the
environment) and install (install is a dumb command that only copies
files so you don't need to
> Now I have the right version of cmake (3.5.2), but the ccmake version is
> still 2.8.12... How can I update ccmake too?
Not 100% certain but my guess would be that you are missing
ncurses-devel package and therefore ccmake was not built.
sudo yum install ncurses-devel
Regards,
Domen
--
Power
> This could probably be supported by adding USE_SOURCE_PERMISSIONS for
> install(FILES ...) would you be willing to contribute a patch?
Misses that this is not cmake-dev mailing list... Patch would still be
appreciated but you could also file a feature request (for extending
the documentation reg
> Before running this cmake script, I am setting executable permissions on the
> build machine, where the package is created.
With install(FILES ...) command permissions set to source file will be
ignored by default (this is missing from documentation).
You could set permissions with PERMISSIONS a
> The strange thing is that CMAKE_HOST_SYSTEM_PROCESSOR (outputed by cmake
> --system-information) uses the same "uname -m"
> see Modules/CMakeDetermineSystem.cmake.
>
> So there is something odd to have one right and the other wrong...
In that case it's quite possible that CPACK_RPM_PACKAGE_ARCHI
> I am working on an IBM Power8 RHEL7.2 system and we installed cmake 3.6
> (default cmake from repo was 2.8.12?) but it seems when making a package
> the arch is set incorrectly to x86_64 instead of ppc64le.
I don't have access to a ppc with Linux but it seems that 'uname -m'
(default that is use
2016-05-30 0:44 GMT+02:00 Thomas Teo :
> Hi All,
> In building an RPM package, I'd like to set multiple (un)install scripts -
> an application specific one which starts services that are installed by the
> RPM, and also to call ldconfig so that the shared library list is updated.
> The CMake/CPack
;PROVIDES' information is not generated.
>
> Thanks for your time again :)
>
> Wang Peng (Rex)
> Seat: 21F
> HZ SE Team
> +86018605811125
>
>
> -Original Message-
> From: EXT Kristian [mailto:kristianonlin...@gmail.com]
> Sent: Friday, April 08, 201
> Let's assume, I have a library, e.g. liblibrary.so.5.6.7 and I have
> two symbolic links, so the result of "ls -l" would look like this
>
> liblibrary.so -> liblibrary.so.0
> liblibrary.so.0 -> liblibrary.so.5.6.7
> liblibrary.so.5.6.7
>
> And let's assume, I have these lines in my CMakeLists.txt
is generated in the 'PROVIDES' fields of the RPM package. But with cpack, it
> doesn't.
>
> Wang Peng (Rex)
> Seat: 21F
> HZ SE Team
> +86018605811125
>
> -Original Message-
> From: EXT Domen Vrankar [mailto:domen.vran...@gmail.com]
> Sent: Friday
> Does someone know why this "CPACK_RPM_PACKAGE_AUTOPROV" option doesn't take
> effect? how can I make it auto generates these 'PROVIDES' information in the
> RPM? thanks for your time and it will be very appreciated if you can
> provide some hints.
CPackRPM relies on rpmbuild and other rpm tools
> So, I've done some research and I found two things:
> - There's a closed bug entry and a very recent patch
> (https://cmake.org/Bug/view.php?id=12431;
> https://cmake.org/gitweb?p=cmake.git;a=log) that will help fixing this;
> - The documentation advises setting the CMAKE_INSTALL_RPATH variable
> Specifying a user binary specfile for CPack RPM packages is done like this:
>
> set(CPACK_RPM_blah_USER_BINARY_SPECFILE blah.spec.in)
>
> The documentation says the "specified file will be processed by
> configure_file( @ONLY)." However, exactly which variables are available for
> substitution? I
> Can this use of mixed case-sensitive/all-upper-case can be clarified in the
> documentation for CPACK_ and CPAC_RPM_ component variables?
I was certain that this was already documented... I'll document it and
also change CPackRPM so that it will support both original version of
component name an
> set(CPACK_GENERATOR "RPM")
> set(CPACK_RPM_BLAH1_USER_BINARY_SPECFILE
> "${CMAKE_CURRENT_SOURCE_DIR}/install/SPECS/blah1.spec.in")
> set(CPACK_RPM_BLAH1_PACKAGE_PREFIX "${CMAKE_INSTALL_PREFIX}/blah1")
> set(CPACK_RPM_BLAH2_PACKAGE_PREFIX "${CMAKE_INSTALL_PREFIX}/blah2")
> set(CPACK_RPM_COMPONENT_
> Not sure how we can disable such script call from CPackRPM unless adding the
> extra feature to call
> rpm/rpmbuild wiht appropriate option. May be you can try to fill the
> CPACK_RPM_SPEC_MORE_DEFINE variable
> with appropriate macro redefining "__os_install_post".
>
> This would be more like a
> I have a slightly unusual question (I guess). Is it possible somehow to force
> CPack to produce RPM files from projects that have build problems?
>
> We use CMake in our nightly build system to test the latest changes in our
> software. When a build problem occurs we don't want the whole build
> If in someApp I find foo find_package(foo CONFIG REQUIRED)
> I get an error: "The following imported targets are referenced, but are
> missing: bar::bar"
>
> The current workaround is to manually add in someApp
> find_package(bar CONFIG REQUIRED) before
> find_package(foo CONFIG REQUIRED)
>
>
> B
I've accidentally dropped the mailing list in reply:
> I do not find an example on how to provide separate RPM's
> for them; one for the binary and one for the headers+library.
> The required results (rough example):
>
> - foo-1.2.3.4-1.x86_64.rpm
> - libfoo-1.2.3.4-1.x86.64.rpm
You have to provi
Hm I've accidentally dropped cmake mailing list when replying
before... Sorry about that.
> Im using "bin" and "devel" as component names. I tried next with upper and
> lower case in the properties but no difference.
> it's about what you see in the RPM header using "rpm -qlip name.rpm" ...
Compo
2015-11-26 0:01 GMT+01:00 Bill Somerville :
> Hi All,
>
> we are trying to get our Debian install package to install on a Linux
> PowerPC system running
Which version of CMake have you tried?
Version 3.4.0 had some changes regarding how DEB packages are packaged
(libarchive instead of system tar)
2015-10-09 19:17 GMT+02:00 Domen Vrankar :
> 2015-10-09 15:37 GMT+02:00 Robert Bielik :
>> Den 2015-10-09 kl. 15:36, skrev Robert Bielik:
>>>
>>> I saw that Rafael introduced libarchive in commit 7044e8ee4, which seems
>>> to be set to both produce tars withou
2015-10-09 15:37 GMT+02:00 Robert Bielik :
> Den 2015-10-09 kl. 15:36, skrev Robert Bielik:
>>
>> I saw that Rafael introduced libarchive in commit 7044e8ee4, which seems
>> to be set to both produce tars without sparse files, and having root:root as
>> user.
>
> Sorry, that would be Raffi ;)
Yes
> I am not sure how to check for the links or their targets. Probably the tests
> run
> fine on my local openSuse installation.
A single test can be run with:
ctest -V -R "CPackComponentsForAll-RPM-default"
This will create directory structure in:
./Tests/CPackComponentsForAll/buildRPM-default/
> I am trying to create a CMake 3.3.0 RPM for openSuse using their Open
> Build Service. It compiles but the tests 115, 116, 117 and, 118 fail.
> The RPM build causes the error but I don't get what I should change. I
> attached the output.
>From the attached output it would seem that something wen
> Is there an alternative method for setting the CMAKE_TOOLCHAIN_FILE variable
> other than, for example:
>
> cmake -D CMAKE_TOOLCHAIN_FILE=...
>
> Perhaps an environment variable or something similar?
You always have the option to set an environment variable and then
read it at the top of your
> if ((${CMAKE_SYSTEM_NAME} MATCHES "SunOS") or (DEFINED LINUX64))
> message(STATUS "On Solaris or 64 bit Linux")
> endif()
> # [
>
> I'm using cmake version 2.8.11.2 built from source on
>
> Linux localhost.localdomain 2.6.18-8.el5 #1 SMP Thu M
> I would like to end up with the following in the specs file:
>
> ...
> %file
> ...
> %if 0%{fedora} >= 14
> "/path/to/some/file"
> %endif
>
> I tried to use CPACK_RPM_USER_FILELIST as
>
> set(CPACK_RPM_USER_FILELIST ${CPACK_RPM_USER_FILELIST}
> "%if 0%{fedora} >= 14"
> "/path/to/some/file
2015-04-25 11:01 GMT+02:00 Markus Mäkelä :
> Hi,
>
> I'm working on a project that uses CMake for build configuration and
> CPack for packaging. We're running on Linux and seem to run into some
> issues with CPack when INSTALL commands have absolute paths.
>
> When we use Makefiles as the build too
> do i make something wrong or is this an Error in FindMFC which i have to
> report?
ATM each CMake provided module has to set its own policies otherwise
policies from CMakeLists.txt minimum required version setting are
used.
Please file a bug report.
Thanks,
Domen
--
Powered by www.kitware.co
> however I am facing a quite dramatic issue: after configuration and
> generation I do have my build folder, but I miss the bin folder inside it,
> and all build folders result empty.
One thing comes to mind... If you accidentally generate build
structure inside root source directory and later
2015-01-19 17:06 GMT+01:00 :
> I am trying to build rpms for projects so they can be installed together
> using a modified yum into a user defined area as
> ///
> hence the rpms should look like
> ///
>
> The only way I could find to do this was to
> set(CPACK_PACKAGING_INSTALL_PREFIX )
> set(CPAC
Hi all,
I wanted to glob recursively for all files and directories and noticed
a difference in behaviour between the recursive and non recursive
version - recursive version doesn't list directories (I am using
latest version from git master - 3.1.2...).
I also noticed that documentation for file(
2015-01-15 1:25 GMT+01:00 David Thompson :
> Hi Bob,
>
> You can see what platforms CMake is tested on here:
>
> https://open.cdash.org/index.php?project=CMake
>
> We just don't distribute binary packages on all of those platforms.
>
> David
>
>> On Jan 14, 2015, at 5:43 PM, Bob Mosleh Sa
> install( PROGRAM ) will keep executable permissions... (as opposed to
> using FILES or DIRECTORY ) not sure about symlinks
Hm forgot about this one... Had problems with it years ago on AIX and
stopped using it back then (it removed baked in paths to libraries
from executables)... Time
> The lib files are not built by cmake but are dependencies for my program.
You could move external libraries wih something like this:
install(FILES /some/location/libsomething.so DESTINATION lib)
> The lib files are symbolic links to the /usr/local/lib directory. For
> example:
>
> Release/lib/l
> Hi,
>
> I was looking at https://www.cmake.org/Bug/view.php?id=3602 "Add
> possibility to change file owner into install macro".
I am also interested in this feature but mostly because of packaging
limitations - implementing this feature would give CPackRPM the
ability to set user and group for
> I request to reopen the bug/feature request (#13231) --
> https://www.cmake.org/Bug/view.php?id=13231&nbn=1
Hi,
I'll have a look at it next week when I'll have more time and get back
to you then.
Regards,
Domen
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake
This was asked a few years ago and I doubt that things have changed
since then... http://www.cmake.org/pipermail/cmake/2010-May/036924.html
(http://www.cmake.org/cmake/help/v2.8.10/cmake.html#prop_sf%3aCOMPILE_FLAGS).
An alternative would be to use
http://www.cmake.org/cmake/help/v3.0/module/Extern
2014-12-03 21:22 GMT+01:00 Chris Johnson :
> I think I've made it work by adding 1 ugly hack and 1 reasonable directive
> to each library's CMakeLists.txt, which is at least far preferable to adding
> several new include paths to potentially hundreds of programs which refer to
> those libraries.
Y
efore because I'm not
certain how to produce two differently named .o files but maybe you'll
be able to figure that out...
Regards,
Domen
2014-11-29 10:31 GMT+01:00 Domen Vrankar :
> Hi,
>
> I haven't tested this but I think you could write something like this:
>
Hi,
I haven't tested this but I think you could write something like this:
add_library(test_single test.c)
set_property(
TARGET test_single
PROPERTY COMPILE_DEFINITIONS DOUBLE=some_val
)
add_library(test_double test.c)
set_property(
TARGET test_double
PROPERTY COMPILE_DEFINITIONS DOUB
2014-10-23 16:05 GMT+02:00 Petr Kmoch :
> Hi Domen.
>
> This is what helps me reason about it:
>
> A string with a ';' in it is a list.
> An unqouted ';' separates arguments to CMake commands.
> string(REPLACE ...) simply concatenates all of its 'input' parameters.
>
> So, when you expand ${list_1
Hi,
I am trying to convert string to list and back with string(REPLACE) and it
doesn't work as expected (tested with cmake 2.8.12 on Ubuntu 14.04 and main
branch in git on Ubuntu 14.10).
cmake_minimum_required( VERSION 2.8.12 )
project(test_list)
set(str_1 "abc.def.ghi")
message("str_1: ${str_1}
2014-10-23 1:57 GMT+02:00 Luc J. Bourhis :
> Am I missing something or there is no equivalent of
> CPACK_RPM_PRE_INSTALL_SCRIPT_FILE to specify %preun or %postun?
>
>
The variables are missing in documentation but they exist.
For %preun you can set CPACK_RPM_PRE_UNINSTALL_READ_FILE or
CPACK_RPM__
> > A workaround that you could use is to specify something like
> >
> > set(CPACK_RPM_bin_USER_FILELIST "%config /subdir")
> >
> > and this will force CPackRPM to treat the symlink as a config file.
>
> What is the meaning of bin in the middle of that variable name?
CPACK_RPM_USER_FILELIST is us
Hi,
I'm assuming that you used something like:
install(CODE "
EXECUTE_PROCESS(COMMAND ln -sf ${SOME_PATH}/subdir-version subdir
WORKING_DIRECTORY ${LOCATION_WHERE_CPackRPM_IS_PACKAGING_YOUR_FILES}
)
" COMPONENT bin)
in your CMakeLists.txt
Currently CPackRPM doesn't automat
Hi,
I'm trying to use my own exp file for linking of a shared library on AIX.
Currently CMake generates an objects.exp file and I don't know how to
replace it with my own that was used in Makefile files before I switched to
CMake and contains less entries than the generated one.
Is there a way to
79 matches
Mail list logo
