Re: Packaging of libraries
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 Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d
Re: Packaging of libraries
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 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? 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. Yaakov
Re: Packaging of libraries
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 already provides the correct SRC_URI (and uses
mirror://gnome too).
> PKG_NAMES="${PN} ${PN}_0 ${PN}-devel"
> libsigc__2_0_CONTENTS="usr/share/doc/libsigc++-2.0 usr/share/devhelp"
> libsigc__2_0_0_CONTENTS="usr/bin/*-2.0-0.dll usr/share/doc/Cygwin
> usr/share/doc/${PN}"
> libsigc__2_0_devel_CONTENTS="usr/include usr/lib"
Please don't make a documentation-only main package. Either make a
separate -doc package (which I did due to its size) or ship it in
-devel.
> but when running 'prep' I get:
Not during prep, but during build (gtkmm_autoreconf, to be precise).
> *** ERROR: mm-common is required to build this package
>
> Am I missing something?
Yeah, mm-common. :-) I've just ITP'd that.
Yaakov
[ITP] mm-common
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. ftp://ftp.cygwinports.org/pub/cygwinports/release-2/GNOME/mm-common/mm-common-0.9.2-1-src.tar.bz2 ftp://ftp.cygwinports.org/pub/cygwinports/release-2/GNOME/mm-common/mm-common-0.9.2-1.tar.bz2 ftp://ftp.cygwinports.org/pub/cygwinports/release-2/GNOME/mm-common/setup.hint Yaakov
Re: Packaging of libraries
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
>
> I did make a separate -doc package due to the size thereof, but that
> would be your call.
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";
PKG_NAMES="${PN} ${PN}_0 ${PN}-devel"
libsigc__2_0_CONTENTS="usr/share/doc/libsigc++-2.0 usr/share/devhelp"
libsigc__2_0_0_CONTENTS="usr/bin/*-2.0-0.dll usr/share/doc/Cygwin
usr/share/doc/${PN}"
libsigc__2_0_devel_CONTENTS="usr/include usr/lib"
but when running 'prep' I get:
*** ERROR: mm-common is required to build this package
Am I missing something?
Chris
--
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
Re: Packaging of libraries
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 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 I did make a separate -doc package due to the size thereof, but that would be your call. Yaakov
[RFU] mintty-0.8.1-1
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
Re: Packaging of libraries
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 actually BE any undefined symbols. If *libtool* is warning you about this, it is because you haven't told libtool that you BELIEVE that the lib has no undefed symbols. If you don't tell it that (LD_FLAGS+=-no-undefined), then it won't even try to build a shared lib. This is so you get a warning, instead of a failure, when compiling libs which actually DO have unresolved symbols; because you ought to be able to compile THOSE as static libs after all, without dying. -- Chuck
Re: Packaging of libraries
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 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 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? Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d
Re: [PATCH] Stop automatic dependency selection on setup.exe chooser screen
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 "satisfy" would be better > wording. > > If you agree and want to meet those requirements then I think we're > satisfied and you can check that in. Done, with one small additional tweak: 'Select required packages' instead of 'Install required packages', because the dialog also appears when trying to uninstall packages that are still needed. Hope that's ok. Andy
Re: Packaging of libraries
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: 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) Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d
Re: Packaging of libraries
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 split the devel package and >separate out the documentation? > >For example, I'm thinking: > >libsigc++-2.2.8-1.tar.bz2 (DLL) >libsigc++-2.2.8-1-devel.tar.bz2 (headers, import libraries) >libsigc++-2.2.8-1-src.tar.bz2 (source) >libsigc++-2.2.8-1-doc.tar.bz2 (Required? - HTML documentation, tutorial) > >Please let me know, thank you. Well, for starters the libsigc++-2.2.8-1-doc.tar.bz2 would give upset, and possibly setup.exe heartburn. It should probably be libsigc++-doc-2.2.8-1.tar.bz2 instead. 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. cgf
Re: [PATCH] Stop automatic dependency selection on setup.exe chooser screen
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 admit I have no better way to say this. >> >> 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 "satisfy" would be better wording. If you agree and want to meet those requirements then I think we're satisfied and you can check that in. cgf
Re: Packaging of libraries
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 and > separate out the documentation? > > For example, I'm thinking: > > libsigc++-2.2.8-1.tar.bz2 (DLL) > libsigc++-2.2.8-1-devel.tar.bz2 (headers, import libraries) > libsigc++-2.2.8-1-src.tar.bz2 (source) > libsigc++-2.2.8-1-doc.tar.bz2 (Required? - HTML documentation, tutorial) > > Please let me know, thank you. It's your decision as maintainer. I would suggest a different layout, though. You're somehow missing the fact that DLLs have versions and that you might have to provide a newer version of the runtime package at one point. So a layout like this seems to be more prudent: libsigc++/ libsigc++-2.2.8-1.tar.bz2 (HTML documentation, tutorial, etc) libsigc++-2.2.8-1-src.tar.bz2 (source) libsigc++20/ libsigc++20-2.2.8-1.tar.bz2 (DLL) libsigc++-devel/ libsigc++-devel-2.2.8-1.tar.bz2 (headers, import libraries) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Packaging of libraries
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 example, I'm thinking: libsigc++-2.2.8-1.tar.bz2 (DLL) libsigc++-2.2.8-1-devel.tar.bz2 (headers, import libraries) libsigc++-2.2.8-1-src.tar.bz2 (source) libsigc++-2.2.8-1-doc.tar.bz2 (Required? - HTML documentation, tutorial) Please let me know, thank you. Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d
Re: [PATCH] Stop automatic dependency selection on setup.exe chooser screen
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? > > == > 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. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
