[CMake] providing your own exp file on AIX

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

Re: [CMake] [CPack] RPM generator and directory symlink

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

Re: [CMake] [CPack] RPM generator and directory symlink

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 used for non

Re: [CMake] [CPACK] [RPM] Support of %preun and %postun

2014-10-23 1:57 GMT+02:00 Luc J. Bourhis luc_j_bour...@mac.com: 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

[CMake] Concatenating lists back to string

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})

Re: [CMake] How about GNU Automatic Variables

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

Re: [CMake] How about GNU Automatic Variables

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 domen.vran...@gmail.com: Hi, I haven't tested this but I think you could write something like this: add_library

Re: [CMake] How to set path to library header files?

2014-12-03 21:22 GMT+01:00 Chris Johnson cxjohn...@gmail.com: 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

Re: [CMake] Removing compiler options

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

Re: [CMake] Request to reopen a bug (#13231) and apply patch given in to mainstream

I request to reopen the bug/feature request (#13231) -- https://www.cmake.org/Bug/view.php?id=13231nbn=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

Re: [CMake] CPack. Modifying the installation prefix when building relocateable RPMs. v3.0.1

2015-01-19 17:06 GMT+01:00 alan.thomp...@glasgow.ac.uk: I am trying to build rpms for projects so they can be installed together using a modified yum into a user defined area as new_prefix/project/platform/installed_binaries hence the rpms should look like

[CMake] different behaviour between file GLOB and GLOB_RECURSE

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

Re: [CMake] supported platforms by Cmake

2015-01-15 1:25 GMT+01:00 David Thompson david.thomp...@kitware.com: 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

Re: [CMake] Creating an installer using cpack

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:

Re: [CMake] Creating an installer using cpack

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

Re: [CMake] Specifying a file owner

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 every

Re: [CMake] missing bin folder

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

Re: [CMake] CMP0054 and CMake Modules

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.com

Re: [CMake] Problems with CPack RPM

2015-04-25 11:01 GMT+02:00 Markus Mäkelä markus...@gmail.com: 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

Re: [CMake] [CPACK] [RPM] Using %if in %file section

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 %endif )

Re: [CMake] Problem with multiple expressions with if()

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 Mar 15

Re: [CMake] alternative method for setting CMAKE_TOOLCHAIN_FILE?

Is there an alternative method for setting the CMAKE_TOOLCHAIN_FILE variable other than, for example: cmake -D CMAKE_TOOLCHAIN_FILE=... args 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

Re: [CMake] Tests 115, 116, 117 and, 118 fail

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/

Re: [CMake] Tests 115, 116, 117 and, 118 fail

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 went

Re: [CMake] CPack Debian

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,

Re: [CMake] CPack Debian

2015-10-09 19:17 GMT+02:00 Domen Vrankar <domen.vran...@gmail.com>: > 2015-10-09 15:37 GMT+02:00 Robert Bielik <robert.bie...@dirac.se>: >> Den 2015-10-09 kl. 15:36, skrev Robert Bielik: >>> >>> I saw that Rafael introduced libarchive in commit 7044e8ee4, wh

Re: [CMake] CPack: Debian package will not install on Linix-ppc

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

[CMake] Fwd: CPack and executable permissions on linux

> 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

Re: [CMake] CPack and executable permissions on linux

> 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

Re: [CMake] CCMake is not getting updated

> 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 --

Re: [CMake] cpack ppc64le rhel7.2 CPACK_RPM_PACKAGE_ARCHITECTURE

> 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

Re: [CMake] cpack ppc64le rhel7.2 CPACK_RPM_PACKAGE_ARCHITECTURE

> 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

Re: [CMake] CCMake is not getting updated

> 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

Re: [CMake] CPack: setting multiple RPM pre/post (un)install scripts

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

Re: [CMake] How to on multiple RPM packages

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

Re: [CMake] How to on multiple RPM packages

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" ...

Re: [CMake] Interpackage dependencies - find_package() from package

> 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) > > >

Re: [CMake] Variables substituted in CPack RPM component user binary specfile

> 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?

Re: [CMake] Stopping CPack from compiling python files

> 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

Re: [CMake] CPack RPM generator not using CPACK_RPM__XXX variables

> 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") >

Re: [CMake] CPack RPM generator not using CPACK_RPM__XXX variables

> 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

Re: [CMake] Creating RPMs from failing projects with CPack

> 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

Re: [CMake] Fwd: CPack does not generate a RPM

> 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

Re: [CMake] 'CPACK_RPM_PACKAGE_AUTOPROV' doesn't work when pack existing binaries with CPack

> 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

Re: [CMake] Issues using CPack for making a debian package

> 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

Re: [CMake] 'CPACK_RPM_PACKAGE_AUTOPROV' doesn't work when pack existing binaries with CPack

raries information > 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

Re: [CMake] Fwd: CPack does not generate a RPM

ted. > > 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, 2016 4:28 PM > To: Wang, Peng 1. (Nokia

Re: [CMake] CPack source package install location

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. >

Re: [CMake] Disabling INSTALL target for subdirectory

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

Re: [CMake] Using CMAKE_INSTALL_PREFIX in custom install command fails with CPack

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 >

Re: [CMake] Managing a local installation of cmake-built open source packages

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

Re: [CMake] CPack DEB version info is missing patch level

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

Re: [CMake] CMake 3.7: Test #379: RunCMake.CPack_RPM fails

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

Re: [CMake] CMake 3.7: Test #379: RunCMake.CPack_RPM fails

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

Re: [CMake] Documentation in RPM Package

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

Re: [CMake] cpack multiple packages

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

Re: [CMake] Packaging issues

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

Re: [CMake] CPACK, generating deb packages: md5sums and wrong directory permissons

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

Re: [CMake] CPACK, generating deb packages: md5sums and wrong directory permissons

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

Re: [CMake] How to exclude some files from building?

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

Re: [CMake] CPack: Create debian packge for each sub-project

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: >

Re: [CMake] CPack: Create debian packge for each sub-project

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

Re: [CMake] RPM package and relocation

> > > 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

Re: [CMake] CPack - Transaction error

> > 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

Re: [CMake] CPack and user .spec file

> > 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

Re: [CMake] CPack: Create debian packge for each sub-project

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

Re: [CMake] CPack: Create debian packge for each sub-project

2017-12-04 19:57 GMT+01:00 DKLind <davidkl...@gmail.com>: > 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 i

Re: [CMake] CPack: Create debian packge for each sub-project

2017-12-04 20:35 GMT+01:00 DKLind <davidkl...@gmail.com>: > 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(CPac

Re: [CMake] INTERFACE libraries and -config.cmake files

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

Re: [CMake] CPack: Create debian packge for each sub-project

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

Re: [CMake] CPack: Create debian packge for each sub-project

2017-12-01 18:04 GMT+01:00 Domen Vrankar <domen.vran...@gmail.com>: > 2017-12-01 16:47 GMT+01:00 DKLind <davidkl...@gmail.com>: > >> This is precisely my situation. I have a large project where 50+ packages >> are >> generated. I wanted, needed, to b

Re: [CMake] Installing and exporting multiple configurations of the same library

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

Re: [CMake] CPack: Create debian packge for each sub-project

2017-12-01 5:41 GMT+01:00 Craig Scott <craig.sc...@crascit.com>: > > > On Fri, Dec 1, 2017 at 11:15 AM, Domen Vrankar <domen.vran...@gmail.com> > wrote: > >> 2017-11-29 17:07 GMT+01:00 DKLind <davidkl...@gmail.com>: >> >&g

Re: [CMake] CPack per-component value for CPACK_PACKAGING_INSTALL_PREFIX when using RPM generator

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

Re: [CMake] CPack per-component value for CPACK_PACKAGING_INSTALL_PREFIX when using RPM generator

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

Re: [CMake] Beginning to compiling CMake file

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

Re: [CMake] CPack multiple packages

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

[CMake] requiring parallel building but sequential linking

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

Re: [cmake-developers] [CPack] Call for volunteer for CPackRPM, CPackDeb maintenance.

Hello, I have been talking with Eric for the past few days now and would also like to help out with maintaining these two modules. I am a CMake user for about six years now and have also been using CPackRPM but for now I haven no experience with CPackDeb. As suggested by Eric I'll start with

[cmake-developers] [CPack] [CPackRPM] mantis ticket 13176 CPackRPM support for per-component summary and description

Hi, I extended the proposed patch for ticket 13176 with: - documentation section - CPACK_RPM_component_PACKAGE_DESCRIPTION fallback to CPACK_COMPONENT_compName_DESCRIPTION - handling of cases when one component sets its variable and the other doesn't Regards, Domen -- Powered by

Re: [cmake-developers] [CPack] [CPackRPM] mantis ticket 13176 CPackRPM support for per-component summary and description

that could be used by CPACK_RPM_component_PACKAGE_SUMMARY as default value? Thanks, Domen 2014-10-14 0:23 GMT+02:00 Domen Vrankar domen.vran...@gmail.com: Message was sent to early by accident so I'm resending the rest. 2014-10-14 0:17 GMT+02:00 Domen Vrankar domen.vran...@gmail.com: Hi, I

Re: [cmake-developers] [CPack] [CPackRPM] mantis ticket 13176 CPackRPM support for per-component summary and description

2014-10-14 9:28 GMT+02:00 Eric Noulard eric.noul...@gmail.com: 2014-10-14 9:03 GMT+02:00 Domen Vrankar domen.vran...@gmail.com: Sorry for spamming... I noticed that the previous patch would break user provided rpm spec files so I'm attaching a new patch that fixes that problem with a bit

[cmake-developers] CMake and CPack automated testing

Hi, I was looking at CMake automated tests and did not quite understand how they are intended to be written. Do they only test for e.g. if CPack executes without errors or do they check generated files content (e.g. diff or call for e.g. rpm -qi some_pkg.rpm and then diff the output)? I'm not

Re: [cmake-developers] [CPack] [CPackRPM] mantis ticket 13176 CPackRPM support for per-component summary and description

I also have a question. Would CPack also need something like CPACK_COMPONENT_component_PACKAGE_SUMMARY that could be used by CPACK_RPM_component_PACKAGE_SUMMARY as default value? Not sure of that one. We already have CPACK_COMPONENT_GROUP_CMAKE_DESCRIPTION which may be a default value for

Re: [cmake-developers] [CPack] [CPackRPM] mantis ticket 13176 CPackRPM support for per-component summary and description

I also wrote a test and noticed two things: 1) CPackComponentsForAll test is using component names in lower case and component parts in variables in upper case (e.g. COMPONENT headers and CPACK_COMPONENT_HEADERS_DESCRIPTION). Patch uses CPACK_RPM_PACKAGE_COMPONENT variable as part of

Re: [cmake-developers] [CPack] [CPackRPM] mantis ticket 13176 CPackRPM support for per-component summary and description

2014-10-21 14:52 GMT+02:00 Brad King brad.k...@kitware.com: On 10/21/2014 02:18 AM, Domen Vrankar wrote: Patches must be applied in order: 0001-CPackRPM-component-based-packaging-description-and-s.patch 0001-add-added-semantic-tests-for-rpm-component-descripti.patch Could someone pleas

Re: [cmake-developers] [CMake] [CPack] RPM generator creates %dir for /usr/local/xxx

Moving the conversation to developers mailing list. More docs on this for 2.8.12: http://www.cmake.org/cmake/help/v2.8.12/cpack.html#variable:CPACK_RPM_EXCLUDE_FROM_AUTO_FILELIST_ADDITION I guess that /usr/local may be added to CPACK_RPM_EXCLUDE_FROM_AUTO_FILELIST default list values. For

[cmake-developers] [CPack] [CPackRPM]patch for bug 15209 - handling of symbolic links

a relative path symlink if needed. Please review the patch and post the feedback. If the patch is OK add it to repository. Thanks, Domen From 0a3098dbeb79c90ac3882b13afa77e6e8ff98d62 Mon Sep 17 00:00:00 2001 From: Domen Vrankar domen.vran...@gmail.com Date: Sat, 8 Nov 2014 22:01:19 +0100 Subject

Re: [cmake-developers] string SUBSTRING TRUNCATE mode

This should be a good addition, no? diff --git a/Modules/CPackRPM.cmake b/Modules/CPackRPM.cmake index 56d9b66..66717ef 100644 --- a/Modules/CPackRPM.cmake +++ b/Modules/CPackRPM.cmake @@ -683,9 +683,7 @@ foreach(_RPM_SPEC_HEADER URL REQUIRES SUGGESTS PROVIDES OBSOLETES PREFIX

Re: [cmake-developers] [PATCH] CPackRPM: unset temporary component variable fixed

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,

Re: [cmake-developers] [PATCH] CPackRPM: unset temporary component variable fixed

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

Re: [cmake-developers] [PATCH] Avoid bad alloc for large files

I received a bad alloc when uploading a large file with CTest. The patch below resolved this. Your patch is line-wrapped and can't be applied. However, I did this by hand. This is basically the same, but it avoids the needless floating point arithmetic. Does it work for you? snip

Re: [cmake-developers] [PATCH] Avoid bad alloc for large files

I received a bad alloc when uploading a large file with CTest. The patch below resolved this. I just took a look at the code and noticed that it is quite memory consumption heavy ((2 * encoded_buffer_size) + file_buffer_size). This implementation could be used instead (not tested): std::string

Re: [cmake-developers] [Review request] Topic install_CMAKE_INSTALL_RELATIVE

) before submitting the patch for review. Preview patch is attached. Regards, Domen From 2d5289559527371e3fce555d49b20e6789d1324c Mon Sep 17 00:00:00 2001 From: Domen Vrankar domen.vran...@gmail.com Date: Mon, 22 Dec 2014 21:22:34 +0100 Subject: [PATCH] multiple path relocation prefixes Allow multiple

[cmake-developers] [PATCH][CPack][RPM] multiple path relocation prefixes

Hello, Could somebody please review the topic rpm_multi_prefix. http://www.cmake.org/gitweb?p=stage/cmake.git;a=commit;h=c908ba3707fcf8cf43df0c5cd90f8ea6d98d7c29 Patch adds support for multiple relocation paths per RPM package. For relocation paths I have extended GNUInstallDirs module since it

Re: [cmake-developers] [PATCH] CPackRPM: Fix cross-building rpms

Add the --target argument to rpmbuild Do not add a BuildArch variable to the spec file for arch specific packages BuildArch causes rpm building to fail except for noarch packages I'm not too familiar with cross compilation problems so could you please also provide a simple test case to help

[cmake-developers] fixing a bug after topic was merged to master

Hi all, While writing tests for a new topic I found a bug in an older topic that I wrote. The that topic was already merged to master (last week) but remote stage branch still exists. The fix is trivial - one variable typo. How can I get the fix both into master and next release candidate

[Cmake-commits] CMake branch, next, updated. v3.1.2-1118-g1952221

- http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=19522216e892f73351dc480507040cd453a795cb commit 19522216e892f73351dc480507040cd453a795cb Merge: 82caa82 521d4cc Author: Domen Vrankar domen.vran...@gmail.com AuthorDate: Sun Feb 8 14:05:24 2015 -0500 Commit: CMake Topic Stage

[Cmake-commits] CMake branch, next, updated. v3.1.0-2047-gb2b55d4

- http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b2b55d49dcd0474b12bdc175d1852301440935c5 commit b2b55d49dcd0474b12bdc175d1852301440935c5 Merge: d875307 c908ba3 Author: Domen Vrankar domen.vran...@gmail.com AuthorDate: Fri Jan 16 15:44:15 2015 -0500 Commit: CMake Topic

[cmake-developers] CPack RPM failing tests on dashboard

I've noticed CPack/RPM test fails on dashboard for two Fedora-19-x86_64 machines: https://open.cdash.org/buildSummary.php?buildid=3658687 https://open.cdash.org/buildSummary.php?buildid=3658677 Would it be possible to get generated rpm files from one of them for analysis?

  1   2   3   4   >