On Jul 31 21:44, Andy Koppe wrote:
On 26 July 2010 09:41, Corinna Vinschen wrote:
Is the above The following packages are required to
satisfy dependencies of your selection. ok? I'm wondering if it's
a bit too wordy, but I admit I have no better way to say this.
How about this?
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:18:05AM +0200, Corinna Vinschen wrote:
On Jul 31 21:44, Andy Koppe wrote:
On 26 July 2010 09:41, Corinna Vinschen wrote:
Is the above The following packages are required to
satisfy dependencies of your selection. ok? ??I'm wondering if it's
a bit too wordy, but I
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 16:42, Christopher Faylor wrote:
How about this?
==
Unmet Dependencies Found [in bold]
The following packages are required to meet dependencies.
I would prefer satisfy instead of meet. But it doesn't matter.
Just go ahead.
I also find meet unsatisfying and think that
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
Please upload:
wget http://mintty.googlecode.com/files/mintty-0.8.1-1.tar.bz2
wget http://mintty.googlecode.com/files/mintty-0.8.1-1-src.tar.bz2
Please delete 0.6.2-1, leaving 0.7.1-1 as previous.
Thanks,
Andy
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
mm-common provides a common build infrastructure for the GNOME C++
bindings (aka GTKmm). This is required at build-time for all packages
using gtkmm_autoreconf and gtkmm_compile.
mm-common is already in Fedora and Debian.
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
16 matches
Mail list logo
