Manager
|
trying to get away from using checkinstall which was causing some weird issues on my system
I tried creating a k9copy rpm with cpack but though the executable was created the rpm is just empty (contains a /usr dir size of 0) 1) extracted the tar 2) ran "cmake ." -- if I don't I get "CPack Error: CPack project name not specified" 3) ran " cpack -D CPACK_RPM_PACKAGE_NAME="kde4-9copy" -D CPACK_RPM_PACKAGE_VERSION="2.3.3" -G RPM" ==================== konsole messages" CPack: Create package using RPM CPack: Install projects CPack: - Run preinstall target for: k9copy CPack: - Install project: k9copy CPack: Compress package CPack: Finalize package CPack: Package /home/MyTemp/k9copy-2.3.3- Source/k9copy-2.3.3-Linux.rpm generated. ===================== spec file created: # -*- rpm-spec -*- Buildroot: /home/smiley/MyTemp/k9copy-2.3.3- Source/_CPack_Packages/Linux/RPM/k9copy-2.3.3- Linux Summary: k9copy built using CMake Name: kde4-k9copy Version: 2.3.3 Release: 1 License: unknown Group: unknown Vendor: Humanity #%define prefix /usr/local %define _rpmdir /home/MyTemp/k9copy-2.3.3- Source/_CPack_Packages/Linux/RPM %define _rpmfilename k9copy-2.3.3-Linux.rpm %define _unpackaged_files_terminate_build 0 %define _topdir /home/MyTemp/k9copy-2.3.3- Source/_CPack_Packages/Linux/RPM ================= rpmbuild.err and rpm.log both look clean ===================== thanks, ps - not a developer, so obviously know idea about developer stuf |
Administrator
|
Can you please provide the contents of the applications CMakeLists.txt ( including your modifications to support CPack )
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Manager
|
thanks, I'm pretty clueless here
there's 5 such file but I assume you're interested in /k9copy-2.3.3-Source/CMakeLists.txt? and by your reply I am supposed to edit this file so it supports cpack? the part of the file that addressed cpack (which i didn't modify) is: ############package############### SET(CPACK_PACKAGE_VERSION_MAJOR "2") SET(CPACK_PACKAGE_VERSION_MINOR "3") SET(CPACK_PACKAGE_VERSION_PATCH "3") SET(CPACK_PACKAGE_NAME "k9copy") SET(CPACK_SOURCE_IGNORE_FILES "moc_" "\\\\.a" "\\\\.moc" "\\\\.gmo" "k9copy$" "k9play$" "k9xineplayer$" "ui_" "\\\\.gz" "\\\\.tar.Z" "\\\\.tar.bz2" "\\\\.tar.xz" "\\\\~$" "\\\\kdevelop" "\\\\automoc" "Makefile$" "TODO" "CMakeCache.txt" "install_manifest.txt" "cmake_install.cmake" "cmake_" "CTest" "CPack" "CMakeLists.txt.user" "/CVS/" "/CMakeTmp/" "/CMakeFiles/" "/_CPack_Packages/" "/templates/" "/\\\\.svn/" "\\\\.swp$" "\\\\.#" "/#" "build" ) #SET(CPACK_INSTALL_CMAKE_PROJECTS "${CMAKE_CURRENT_BINARY_DIR};K9Copy;ALL;/" ) INCLUDE(CPack) |
Administrator
|
I don't see anywhere in there that includes a project which was previously created.
See: http://itk.org/Wiki/CMake:Packaging_With_CPack Perhaps try removing the SET(CPACK_SOURCE_IGNORE_FILES section, and add
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Manager
|
tried removing the SET CPACK section AND uncommenting "#SET(CPACK_INSTALL_CMAKE_PROJECTS "${CMAKE_CURRENT_BINARY_DIR};K9Copy;ALL;/" )
-- which appears to be what you suggested also tried keeping SET CPACK section and uncommenting #SET (CPACK_INSTALL_ ..... neither worked |
Administrator
|
I do not know why the CPack routines fail to generate a valid package for you unfortunately, and was unable to do so myself due to the dependencies it has preventing me from compiling it. You may wish to contact the author of the project.
I have found that the package "kde4-k9copy" is available from the PackMan repositories. http://packman.links2linux.org/package/kde4-k9copy/ If you have the needed dependencies available, the source RPM will likely be of the most help, and can be directly installed. http://packman.links2linux.org/download ... .1.src.rpm
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Manager
|
I know there's a Packman rpm available (though there is a slightly newer one available on kde-apps.org). I was using k9copy as my test case for testing a replacement for checkninstall (which gives me problems on my system). Occasionally I have found a few programs that are not packaged for openSuse (gnubg, kardsgt, until recently amarok 2.2) or something not yet updated (like k9copy, or a more current amarok 2.2) and I try and install only rpm's in effort to keep my system clean and manageable. thanks, |
Administrator
|
I have found generally that when compiling from source it is good to set up a single area ( such as /opt/trunk-kde/ ) and install source packages under here
I have a script which automatically configures my environment to allow installation of Trunk KDE / latest released Qt, which would likely help. I can post a copy if you wish.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered users: Bing [Bot], claydoh, Google [Bot], markhm, rblackwell, sethaaaa, Sogou [Bot], Yahoo [Bot]