I'm working on packaging rtorrent for Cygwin. To that end it requires
libtorrent and libsigc++. My question is, for libtorrent and
libsigc++, I need to split the dll and the developer packages
(obviously), but do I also need to split the devel package and
separate out the documentation?
For
On Aug 5 10:34, Chris Sutcliffe wrote:
I'm working on packaging rtorrent for Cygwin. To that end it requires
libtorrent and libsigc++. My question is, for libtorrent and
libsigc++, I need to split the dll and the developer packages
(obviously), but do I also need to split the devel package
On Thu, Aug 05, 2010 at 10:34:38AM -0400, Chris Sutcliffe wrote:
I'm working on packaging rtorrent for Cygwin. To that end it requires
libtorrent and libsigc++. My question is, for libtorrent and
libsigc++, I need to split the dll and the developer packages
(obviously), but do I also need to
On 5 August 2010 11:44, Christopher Faylor wrote:
I like the idea of separating the documentation but not every package
does this so whatever you decide is ok with me unless someone else has a
compelling argument either way.
I'm working on following the libtheora model:
On 5 August 2010 12:02, Chris Sutcliffe wrote:
I'm working on following the libtheora model:
libsigc++-2.2.8-1.tar.bz2 (documentation)
libsigc++0-2.2.8-1.tar.bz2 (runtime)
libsigc++-devel-2.2.8-1.tar.bz2 (development)
I've made good progress with libsgic++, but libtorrent is giving me
grief
On 8/5/2010 3:09 PM, Chris Sutcliffe wrote:
libtool: link: warning: undefined symbols not allowed in
i686-pc-cygwin shared libraries
but I can't find any output from libtool to tell me what symbols are
undefined. Is there a way to find out what libtool is complaining
about?
There may not
On Thu, 2010-08-05 at 12:02 -0400, Chris Sutcliffe wrote:
I'm working on following the libtheora model:
libsigc++-2.2.8-1.tar.bz2 (documentation)
libsigc++0-2.2.8-1.tar.bz2 (runtime)
libsigc++-devel-2.2.8-1.tar.bz2 (development)
Please API-version these, as there have been several
Hi Yaakov,
On 5 August 2010 16:43, Yaakov (Cygwin/X) wrote:
Please API-version these, as there have been several
parallel-installable APIs of libsigc++. Feel free to borrow from Ports:
http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/ports;a=tree;f=libs/libsigc%2B%2B2.0
On Thu, 2010-08-05 at 20:44 -0400, Chris Sutcliffe wrote:
I've made some minor modifications to your packaging:
ORIG_PN=libsigc++
inherit gtkmm
HOMEPAGE=http://libsigc.sourceforge.net/;
SRC_URI=http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/${ORIG_PN}-${PV}.tar.bz2;
gtkmm.cygclass
On Thu, 2010-08-05 at 15:09 -0400, Chris Sutcliffe wrote:
I've made good progress with libsgic++, but libtorrent is giving me
grief in that it refuses to build the shared target (static is fine).
What I get is:
libtool: link: warning: undefined symbols not allowed in
i686-pc-cygwin shared
On 5 August 2010 22:42, Yaakov (Cygwin/X) wrote:
This should get you started:
http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/ports;a=tree;f=net/libtorrent
I just built it; I made no attempt to test its functionality.
Excellent, thank you Yaakov!
Chris
--
Chris
On Fri, Jul 26, 2002 at 07:59:06AM -0400, Nicholas Wourms wrote:
Now this package's c++ library has been compiled with g++-2 since
libtool refuses to link to libstc++.la in the new g++-3.1.1-4. This
certain someone suggested that I rebuild the proposed packages with only
the C libraries
- Original Message -
From: Nicholas Wourms [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, July 27, 2002 12:04 AM
Subject: Re: gcc-3.2 C++ ABI and packaging c++ libraries [was Re: [ITP]:
Berkeley DB v3.1]
Gareth Pearce wrote:
B)If possible, I'd like to know what
13 matches
Mail list logo