Re: Packaging a project using cmake

On Sun, Jun 8, 2008 at 9:43 AM, Riku Voipio <[EMAIL PROTECTED]> wrote: > On Sat, Jun 07, 2008 at 09:25:23PM +0200, Mathieu Malaterre wrote: >> >> $ superdupertool libfoo.so >> >>=> this lib requires libstdc++6 at least version 4.0.2 > >> > dpkg-shlibdeps run during build does that and then dpkg-gen

Re: Packaging a project using cmake

On Sat, Jun 07, 2008 at 09:25:23PM +0200, Mathieu Malaterre wrote: > >> $ superdupertool libfoo.so > >>=> this lib requires libstdc++6 at least version 4.0.2 > > dpkg-shlibdeps run during build does that and then dpkg-gencontrol > > replaces the ${shlibs:Depends} in control file > All this is kin

Re: Packaging a project using cmake

On 2008-06-07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote: And this is where the cmake folks are wrong (I once wrote them a long email about it). >>> >>> link, please ? >> >> To Alex Neundorff and Bill Hoffmann. > > I originally wrote the deb plugin, Alex simply integrated in cmake. If >

Re: Packaging a project using cmake

"Mathieu Malaterre" <[EMAIL PROTECTED]> writes: > On Sat, Jun 7, 2008 at 8:28 PM, Sune Vuorela <[EMAIL PROTECTED]> wrote: >> - running ldconfig in postinst > AFAIK that's not always required... Policy 8.1.1. -- Russ Allbery ([EMAIL PROTECTED]) --

Re: Packaging a project using cmake

"Mathieu Malaterre" <[EMAIL PROTECTED]> writes: > You need to use cmake 2.6.0 (none of the dpkg-* utils are needed in > the process). I believe the current thinking on this is that using the dpkg-* utilities is required for uploads to the Debian repositories. Even if you can duplicate their beha

Re: Packaging a project using cmake

On Sat, Jun 7, 2008 at 8:28 PM, Sune Vuorela <[EMAIL PROTECTED]> wrote: > On 2008-06-07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote: What do you mean ? Indeed I want the whole process from src to .deb handled by cmake. >>> >>> Then please forget it. That doesn't make proper debs. >> >> b

Re: Packaging a project using cmake

#include * Sune Vuorela [Sat, Jun 07 2008, 06:28:03PM]: > > SET(CPACK_DEBIAN_PACKAGE_DEPENDS "libc6, libstdc++6 (>= 4.0.2-4), > > libuuid1, zlib1g (>= 1:1.2.1), libgcc1 (>= 1:4.0.2), libexpat1, swig") > > you do this *manually* ? Relay, he cannot beat http://bugs.debian.org/cgi-bin/bugreport.

Re: Packaging a project using cmake

On 2008-06-07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote: >>> What do you mean ? Indeed I want the whole process from src to .deb >>> handled by cmake. >> >> Then please forget it. That doesn't make proper debs. > > because... Because they doesn't use - dpkg-shlibdeps - python-support|python-c

Re: Packaging a project using cmake

he work before ? I am currently >>>> struggling on how to do it properly when installing python module >>>> (what is the layout, how do you know the python target installation >>>> directory...) >>> >>> Are you talking about using cmake to *build the de

Re: Packaging a project using cmake

>> (what is the layout, how do you know the python target installation >>> directory...) >> >> Are you talking about using cmake to *build the deb* or just about >> packaging a project using cmake? >> >> If you are talking about the former, please forget it.

Re: Packaging a project using cmake

; Are you talking about using cmake to *build the deb* or just about > packaging a project using cmake? > > If you are talking about the former, please forget it. What do you mean ? Indeed I want the whole process from src to .deb handled by cmake. I made some prelimianary versions at:

Re: Packaging a project using cmake

fore ? I am currently > struggling on how to do it properly when installing python module > (what is the layout, how do you know the python target installation > directory...) Are you talking about using cmake to *build the deb* or just about packaging a project using cmake? If you are talking a

Re: Packaging a project using cmake

On Sat, Jun 07, 2008 at 06:04:53PM +0200, Mathieu Malaterre wrote: > I am working on cleaning up the packaging of my project (GDCM) using > cmake so that the .deb produced is consistant with the debian package. Not sure what you mean here, a .deb is a debian package, so what is needed to be cons

Packaging a project using cmake

Hi there, I am working on cleaning up the packaging of my project (GDCM) using cmake so that the .deb produced is consistant with the debian package. I was wondering if anyone had done the work before ? I am currently struggling on how to do it properly when installing python module (what is the