Makepkg is creating a /usr/lib64 why?[SOLVED]

Question

Hi there,
i'm trying to use vmime (http://www.vmime.org/) for a project. after seeking through the AUR there is no package available that builds out of the box. So i tried to make my own.
I am using the src from github (https://github.com/kisli/vmime) which build just fine. But after the simple step to wrap it in an arch package i get an issue i can't find documentation about. after the package() step i have a folder /usr/lib64 where the lib is copied. Obviously i cant use that to install cuz pacman don't let me install files under /usr/lib64 but i cant'f find the step where this folder is created in the first place.
i tried -DCMAKE_INSTALL_LIBDIR=/usr/lib without any success. I can't really belief this has something to do with cmake cuz if i am building this "standalone" i get a simple "lib" folder. But using makepgk suddenly i have an lib64 folder inside my pgk.
what is causing the creation of the /usr/lib64 folder?
Here is my script so far:
pkgname=libvmime-git
pkgver=0.9.2
pkgrel=1
pkgdesc="A powerful C++ class library for working with RFC-822 and MIME messages."
arch=("i686" "x86_64")
url="http://www.vmime.org/"
license=("GPL3")
depends=("gsasl" "gnutls")
makedepends=("cmake")
conflicts=("libvmime" "libvmime-svn" "zarafa-libvmime")
optdepends=("sendmail: sendmail protocol support")
build() {
git clone git://github.com/kisli/vmime.git ${pkgname}
cd ${srcdir}/${pkgname}
cmake -DVMIME_HAVE_MESSAGING_PROTO_SENDMAIL:BOOL=OFF \
-DCMAKE_INSTALL_PREFIX:PATH=/usr \
-DVMIME_SHARED_PTR_USE_CXX=ON \
-DVMIME_SHARED_PTR_USE_BOOST=OFF
make
package() {
cd ${srcdir}/${pkgname}
make DESTDIR="${pkgdir}" install
Last edited by lordnaikon (2015-03-23 08:52:34)

Answer 1

"I'm not sure if our wiki needs documenation on build systems"
Yes you're right about that, thats just a messed up cmake i just wondered where this is coming from in the first place ... the doku of vmime says nothing about that, the other cmake options to enable c++11 smart pointer instead of boost pointer i had to dig out of the cmake .. the only options that are mentioned in the doku are "if you wanna build with openssl or gnutls ... "
i grep a bit around and after the build i found a vmime.pc file with "libdir=/usr/lib64" but thats generated by cmake so i looked a bit closer to the CMakeList and found
# Automatically set lib suffix
IF(UNIX AND NOT APPLE AND NOT CMAKE_CROSSCOMPILING AND NOT EXISTS "/etc/debian_version")
IF(CMAKE_SIZEOF_VOID_P EQUAL 8 AND NOT LIB_SUFFIX)
# ...only if LIB_SUFFIX is not defined...
IF(NOT DEFINED LIB_SUFFIX)
# ...and if CMAKE_INSTALL_LIBDIR does not already contain the suffix
IF(NOT "${CMAKE_INSTALL_LIBDIR}" MATCHES ".*64.*")
SET(LIB_SUFFIX 64)
ENDIF()
ENDIF()
ENDIF()
ENDIF()
# Determine library installation dir, in this order:
# 1) use VMIME_INSTALL_LIBDIR if set
# 2) use LIB_INSTALL_DIR if defined
# 3) use CMAKE_INSTALL_LIBDIR if set
# if it is a relative path, prepend CMAKE_INSTALL_PREFIX to it
# 4) use CMAKE_INSTALL_PREFIX/lib
IF(NOT DEFINED VMIME_INSTALL_LIBDIR)
IF(DEFINED LIB_INSTALL_DIR)
SET(VMIME_INSTALL_LIBDIR ${LIB_INSTALL_DIR})
# respect CMAKE_INSTALL_LIBDIR if set
ELSEIF(DEFINED CMAKE_INSTALL_LIBDIR)
SET(VMIME_INSTALL_LIBDIR ${CMAKE_INSTALL_LIBDIR})
IF(IS_ABSOLUTE ${VMIME_INSTALL_LIBDIR})
SET(VMIME_INSTALL_LIBDIR ${CMAKE_INSTALL_LIBDIR}${LIB_SUFFIX})
ELSE()
SET(VMIME_INSTALL_LIBDIR ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_LIBDIR}${LIB_SUFFIX})
ENDIF()
ELSE()
SET(VMIME_INSTALL_LIBDIR ${CMAKE_INSTALL_PREFIX}/lib${LIB_SUFFIX})
ENDIF()
ENDIF()
GRRR *:(  So i'll try VMIME_INSTALL_LIBDIR instead of my first MAKE_INSTALL_LIBDIR
EDIT://
Trilby wrote:As for Karol's suggestion, cmake/FindICU.cmake is the only file to actually specify lib64 before the build process.  I'm retrying the build with that sed replacement.
i guess that needs to stay, it just searches for needed libs
Last edited by lordnaikon (2015-03-22 21:34:21)