[ITA from Yaakov] python-wx
Apologies for bumping this again, I'm just waiting for this to be done before I start on wxPython 4, which is blocking progress for me doing other things. If you're not interested in this fix, just let me know and I'll move on to wxPython 4. I have re-built the packages using your new cygport as the starting point, and it seems to work really well. I made some minor modifications to include the license files and the new patches from Fedora. The new files are available at https://www.hamishmb.com/files/cygwin-temp/ and I have removed the previous attempt's files. Seeing as I have no need to rebuild wxWidgets, I guess that can stay under your maintainership until an update is needed, at which point I'll be happy to pick it up. Hamish 0x87B761FE07F548D6.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: [ITA] zziplib
On 5/13/2020 11:10 PM, Yaakov Selkowitz wrote: On Wed, 2020-05-13 at 14:44 -0400, Ken Brown via Cygwin-apps wrote: 2. I primed the cache so that configure would think I didn't have xmlto installed. The latter failed to produce man files, for reasons I didn't try to figure out. They build on my system with xmlto 0.0.26, so it's probably a matter of a missing dependency. Do you have all the docbook-* packages installed? What error message is shown? The error message was I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd Installing docbook-xml412 fixed it (Duh!). Thanks. Ken
[ITA] poppler, poppler-data
cygport files attached. In both cases these are routine updates to the latest
upstream release. For poppler, I also updated the Fedora patches to those that
are used in the latest Fedora release (but I ignored the patches that are for
qt4, since the Cygwin build uses qt5).
Ken
inherit qt5 cmake
NAME="poppler"
VERSION=0.88.0
RELEASE=1
CATEGORY="Libs"
SUMMARY="PDF rendering library"
DESCRIPTION="Poppler is a fork of the xpdf PDF viewer which provides PDF
rendering functionality as a shared library and replaces built-in code
with dependencies that are now available as standard components of modern
Unix desktop environments."
HOMEPAGE="http://poppler.freedesktop.org/";
SRC_URI="https://poppler.freedesktop.org/${NAME}-${VERSION}.tar.xz";
PATCH_URI="
https://src.fedoraproject.org/rpms//poppler/raw/master/f/poppler-0.30.0-rotated-words-selection.patch
https://src.fedoraproject.org/rpms//poppler/raw/master/f/poppler-0.63.0-tiling-patterns.patch
https://src.fedoraproject.org/rpms//poppler/raw/master/f/poppler-0.84.0-MacroPushRequiredVars.patch
0.30.0-cygwin-dllexport.patch
"
BUILD_REQUIRES="gtk-doc \
libQt5Gui-devel \
libboost-devel \
libcairo-devel \
libcurl-devel \
libfontconfig-devel \
libfreetype-devel \
libgdk_pixbuf2.0-devel \
libgirepository1.0-devel \
libglib2.0-devel \
libgtk3-devel \
libjpeg-devel \
liblcms2-devel \
libnss-devel \
libopenjp2-devel \
libpng-devel \
libtiff-devel \
openjpeg2 \
poppler-data-devel"
# the core is API/ABI unstable, so this changes with every release
c_abi=99
# the bindings are API/ABI stable, so these should NOT need to change
cpp_abi=0
glib_abi=8
qt5_abi=1
PKG_NAMES="${NAME} libpoppler${c_abi} libpoppler-devel"
poppler_CATEGORY="Graphics"
poppler_SUMMARY="PDF manipulation utilities"
poppler_CONTENTS="usr/bin/*.exe usr/share/doc/ usr/share/man/"
declare libpoppler${c_abi}_SUMMARY="${SUMMARY} (core runtime)"
declare libpoppler${c_abi}_REQUIRES="poppler-data"
declare libpoppler${c_abi}_CONTENTS="usr/bin/cygpoppler-${c_abi}.dll"
declare libpoppler_devel_SUMMARY="${SUMMARY} (core development)"
libpoppler_devel_CONTENTS="--exclude=*cpp* --exclude=*glib* --exclude=*qt4*
--exclude=*qt5*
usr/include/ usr/lib/libpoppler.* usr/lib/pkgconfig/"
PKG_NAMES+=" libpoppler-cpp${cpp_abi} libpoppler-cpp-devel"
declare libpoppler_cpp${cpp_abi}_SUMMARY="${SUMMARY} (C++ STL runtime)"
declare
libpoppler_cpp${cpp_abi}_CONTENTS="usr/bin/cygpoppler-cpp-${cpp_abi}.dll"
libpoppler_cpp_devel_SUMMARY="${SUMMARY} (C++ STL development)"
libpoppler_cpp_devel_CONTENTS="usr/include/poppler/cpp/ usr/lib/libpoppler-cpp.*
usr/lib/pkgconfig/poppler-cpp.pc"
PKG_NAMES+=" libpoppler-glib${glib_abi} libpoppler-glib-devel
libpoppler-glib-doc girepository-Poppler0.18"
declare libpoppler_glib${glib_abi}_SUMMARY="${SUMMARY} (GObject runtime)"
declare
libpoppler_glib${glib_abi}_CONTENTS="usr/bin/cygpoppler-glib-${glib_abi}.dll"
libpoppler_glib_devel_SUMMARY="${SUMMARY} (GObject development)"
libpoppler_glib_devel_CONTENTS="usr/include/poppler/glib/
usr/lib/libpoppler-glib.*
usr/lib/pkgconfig/poppler-glib.pc"
libpoppler_glib_doc_CATEGORY="Doc"
libpoppler_glib_doc_SUMMARY="${SUMMARY} (GObject bindings API docs)"
libpoppler_glib_doc_CONTENTS="usr/share/gtk-doc/"
girepository_Poppler0_18_SUMMARY="${SUMMARY} (GObject Introspection)"
girepository_Poppler0_18_CONTENTS="usr/*/gir*/Poppler-0.18.*"
PKG_NAMES+=" libpoppler-qt5_${qt5_abi} libpoppler-qt5-devel"
declare libpoppler_qt5_${qt5_abi}_SUMMARY="${SUMMARY} (Qt5 runtime)"
declare
libpoppler_qt5_${qt5_abi}_CONTENTS="usr/bin/cygpoppler-qt5-${qt5_abi}.dll"
libpoppler_qt5_devel_SUMMARY="${SUMMARY} (Qt5 development)"
libpoppler_qt5_devel_REQUIRES="libQt5Core-devel libQt5Gui-devel"
libpoppler_qt5_devel_CONTENTS="usr/include/poppler/qt5/ usr/lib/libpoppler-qt5.*
usr/lib/pkgconfig/poppler-qt5.pc"
DISTCLEANFILES="glib/*.gir"
DIFF_EXCLUDES="poppler-config.h reference"
CPPFLAGS+=" -D_XOPEN_SOURCE=500 -D_DEFAULT_SOURCE"
# BUILD_QT5_TESTS: uses private symbols which are not dllexport'ed
CYGCMAKE_ARGS="
-DENABLE_XPDF_HEADERS=ON
-DENABLE_CPP=ON
-DENABLE_GLIB=ON
-DENABLE_GTK_DOC=ON
-DENABLE_QT5=ON
-DBUILD_QT5_TESTS=OFF
-DENABLE_UTILS=ON
-DENABLE_LIBOPENJPEG=openjpeg2
-DENABLE_CMS=lcms2
-DENABLE_DCTDECODER=libjpeg
-DENABLE_LIBCURL=ON
-DENABLE_ZLIB=ON
"
NAME="poppler-data"
VERSION=0.4.9
RELEASE=1
CATEGORY="Graphics Text"
SUMMARY="PDF rendering library (encoding data)"
DESCRIPTION="Poppler is a fork of the xpdf PDF viewer which provides PDF
rendering functionality as a shared library and replaces built-in code
with dependencies that are now available as standard components of modern
Unix d
[ITA] libpng
Builds fine from Yaakov's cygport file, no update needed at present. Ken
Re: [ITA] python2-wx and related packages for wxPython and wxwidgets
Am 23.04.2020 um 20:52 schrieb Yaakov Selkowitz: On Thu, 2020-04-23 at 18:09 +0100, Hamish McIntyre-Bhatty wrote: On 23/04/2020 17:08, Yaakov Selkowitz wrote: Please keep all discussion on list. Fair enough. python-sip will need to be updated for that as well, which requires also updating python-pyqt5* in sync therewith, so this will need to be coordinated. -- Yaakov sorry for missing this point I will look at both. Marco
Re: [ITA from Yaakov] python-wx
Am 14.05.2020 um 12:02 schrieb Hamish McIntyre-Bhatty via Cygwin-apps: Apologies for bumping this again, I'm just waiting for this to be done before I start on wxPython 4, which is blocking progress for me doing other things. If you're not interested in this fix, just let me know and I'll move on to wxPython 4. I have re-built the packages using your new cygport as the starting point, and it seems to work really well. I made some minor modifications to include the license files and the new patches from Fedora. The new files are available at https://www.hamishmb.com/files/cygwin-temp/ and I have removed the previous attempt's files. Seeing as I have no need to rebuild wxWidgets, I guess that can stay under your maintainership until an update is needed, at which point I'll be happy to pick it up. Hamish question: do you take both or only wxWidgets3.0 ? python-wxYaakov Selkowitz wxWidgets3.0 Yaakov Selkowitz Regards Marco
Re: [ITA] poppler, poppler-data
Am 14.05.2020 um 16:54 schrieb Ken Brown via Cygwin-apps: cygport files attached. In both cases these are routine updates to the latest upstream release. For poppler, I also updated the Fedora patches to those that are used in the latest Fedora release (but I ignored the patches that are for qt4, since the Cygwin build uses qt5). Ken both yours Regards Marco
Re: [ITA from Yaakov] python-wx
Am 14.05.2020 um 18:51 schrieb Hamish McIntyre-Bhatty: On 14/05/2020 16:41, Marco Atzeri via Cygwin-apps wrote: question: do you take both or only wxWidgets3.0 ? python-wx Yaakov Selkowitz wxWidgets3.0 Yaakov Selkowitz Regards Marco I think I'd take only python-wx until wxWidgets3.0 needs a rebuild - currently wxWidgets3.0 doesn't seem to have any problems. I could have a look and see if Fedora has any new patches for it, but AFAIK it's working fine so perhaps just best left alone. Hamish python-wx is your. please provide your SSH Key as mentioned https://cygwin.com/packaging/key.html#sshkey
SSH key for Hamish McIntyre-Bhatty
Name: Hamish McIntyre-Bhatty BEGIN SSH2 PUBLIC KEY Comment: "8192-bit RSA, converted by hamish@hamish-HP-bw024na from Ope" B3NzaC1yc2EDAQABAAAEAQDbP8s1z+JIpAtj8E+Xzy3YlGZxXVLMuGb8YLy1XF gISiZFIChQFzRCRDDHLb7KvuFThlA0YqQdz8yJcW1Ko+2DYx1pPKtBq3mD2WZ9kU0pp8mP fPg6YOqC0BZX7J0DQ3EqqkymHsygUjpH5lFnHj/Hi02B5hoN3/5BuNAIMNYO+oEhEkEjGF HErAKDCOWSziu/wEf/XdQpqc+Zh9gn9HuOsMPxLFwLt3MtiAdkZHwTf1Sb5fZUHHet7e41 yFy2BIg04SKY7Sx6HGd+vJb1HwKRyURbitxe5ZZng14qOxI0cAf2c8J8bZmqdcRK5MO0OZ AYBFeSUhZLTU+O+5js+K+O9vlCPSvRokqm3/gZltf7dYp/YgMO/N9FF0uoVELxrlF0KEMw mDakIYJ+eEi4qWx5wQrSYyVKGmnUMAQ1sLulEkvMFmx8wVZWqqJrQXJR+TVGmm+XmmW5e9 HWFcHwzQfTD5uQ1AOudIQ0JB1HkmtXXijrrBa9z7hY6D1Zet7hZ1Fu92G7NmSiDf4Uraxr dul5ragwmzd6AmHwpCl758JgRR34wNsuF3bX3Mdr2cbgNa4peQACxnx62C8hMT2bGhpSrm 3TCJIaRGUvZQ6yFiGoWRde68aGtwj0FGQccOTyopeNVDXzoqBqcbtnFieyzSj/q6QEOnq9 81vMntdqgnvgSESIeaW2Lldu1zCdLGGPZJMlAquiL5+8c7ajda9HJ17eC0eStkUN/RpTqu Wnvq8ME6DfEMYxMEilnfawN2U3GOqkUd17dpVotQfeOZQrgbizsLFaH9c5HN8pptiKKG4u zKyJCixP3a0O1EEhisf16DdMKLW/8I1AfxEG8hCouP3wHP6dpRH8zrAOfMRggHc0M/7GKt WUL64/jADrXb6A5R7Tmjt5IWb7ts1O3MFVoBnSFDDs75mI/7jneETCuNNuO/cmzYzwKc/n KepXrsw5pZtyc9cBODOmcX5M39hAssJdS1Wzk2Ym5DLyO3c3RNXhx2W2lb68y4vTz4doOt SZVGxOPnnjvLLpynBhe5ZPhis+0DOr04taNJw4cRrE4W8WyUHbAXIfkRmutwZ5ROuObbaw 7lDXfzLkZi/O7b5L3eXHHL04fQC0bPpsjUwoR3w/ssPfBEjU0eu2wvn/1xkZbmoOcawKK+ lRucWZaI3XLyg8JiyWoWkQ01fFtNpgPNR2jZ9IllYbixpvwziXYgV54FWl/9Utwpyyw221 uaSq+gLnJ2ynnnT8cbQtqJrTEQL0jb4XhL+6emPnE3D+XzvD0ZmE3d7gQJv7I2Us4nS10/ C4NbaGMEHISk5gevImvH8B9J+58+piIzcccUNMbXmmwrjjBtCgzf2xSOQ9O0YklXJr END SSH2 PUBLIC KEY 0x87B761FE07F548D6.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
python-wx: new maintainer Key
On 14/05/2020 18:06, Marco Atzeri via Cygwin-apps wrote: Am 14.05.2020 um 18:51 schrieb Hamish McIntyre-Bhatty: On 14/05/2020 16:41, Marco Atzeri via Cygwin-apps wrote: question: do you take both or only wxWidgets3.0 ? python-wx Yaakov Selkowitz wxWidgets3.0 Yaakov Selkowitz Regards Marco I think I'd take only python-wx until wxWidgets3.0 needs a rebuild - currently wxWidgets3.0 doesn't seem to have any problems. I could have a look and see if Fedora has any new patches for it, but AFAIK it's working fine so perhaps just best left alone. Hamish python-wx is your. please provide your SSH Key as mentioned https://cygwin.com/packaging/key.html#sshkey Cheers, I have provided the key. How do I know if I did it correctly? Hamish - Forwarding Hamish's key submissions It seems the mailing list has problem with the default reply-to. I am manually overriding the current behaviour, but clearly I am not the only one impacted. 0x87B761FE07F548D6.asc Description: application/pgp-keys signature.asc Description: PGP signature
Fwd: Re: [ITA] libpng
to the right mailing list Weitergeleitete Nachricht Am 14.05.2020 um 17:17 schrieb Ken Brown via Cygwin-apps: Builds fine from Yaakov's cygport file, no update needed at present. Ken updated maintainer
[ITA] mm-common
cygport file attached. I bumped the version to the latest upstream release, and
I removed the custom src_compile, since the default src_compile now works (and
the custom one doesn't, since the tarball no longer includes a configure script).
Ken
inherit gnome.org
NAME="mm-common"
VERSION=1.0.0
RELEASE=1
CATEGORY="Devel"
SUMMARY="GNOME C++ bindings build infrastructure"
DESCRIPTION="The mm-common module provides the build infrastructure and
utilities shared among the GNOME C++ binding libraries."
ARCH=noarch
CYGPORT_USE_UNSTABLE_API=1
src_unpack_hook() {
NOCONFIGURE=1 ./autogen.sh
}
src_compile() {
cd ${B}
cygconf
cygmake
}
[ITA] libsigc2.0, [ITP] libsigc3.0
cygport files attached. I've updated libsigc2.0 to the latest release in the
2.0 series, and I've created libsigc3.0 as a new package, as Fedora does. Note:
If you want to do a test build of the latter, you'll need to install the updated
mm-common from the previous ITA.
Ken
ORIG_PN="libsigc++"
inherit gtkmm
NAME="libsigc2.0"
VERSION=2.10.3
RELEASE=1
CATEGORY="Libs"
SUMMARY="C++ typesafe callback library"
DESCRIPTION="libsigc++ implements a typesafe callback system for standard C++.
It allows you to define signals and to connect those signals to any callback
function, either global or a member function, regardless of whether it is
static or virtual."
HOMEPAGE="https://libsigcplusplus.github.io/libsigcplusplus/";
PKG_NAMES="${NAME}_0 ${NAME}-devel ${NAME}-doc"
libsigc2_0_0_CONTENTS="usr/bin/*-2.0-0.dll usr/share/doc/${NAME}/"
libsigc2_0_devel_CONTENTS='usr/include/ usr/lib/'
libsigc2_0_doc_CONTENTS='usr/share/devhelp/ usr/share/doc/libsigc++-2.0/'
BUILD_REQUIRES="mm-common"
ORIG_PN="libsigc++"
inherit gtkmm
NAME="libsigc3.0"
VERSION=3.0.3
RELEASE=1
CATEGORY="Libs"
SUMMARY="C++ typesafe callback library"
DESCRIPTION="libsigc++ implements a typesafe callback system for standard C++.
It allows you to define signals and to connect those signals to any callback
function, either global or a member function, regardless of whether it is
static or virtual."
HOMEPAGE="https://libsigcplusplus.github.io/libsigcplusplus/";
PKG_NAMES="${NAME}_0 ${NAME}-devel ${NAME}-doc"
libsigc3_0_0_CONTENTS="usr/bin/*-3.0-0.dll usr/share/doc/${NAME}/"
libsigc3_0_devel_CONTENTS='usr/include/ usr/lib/'
libsigc3_0_doc_CONTENTS='usr/share/devhelp/ usr/share/doc/libsigc++-3.0/'
BUILD_REQUIRES="mm-common"
Re: [ITA from Yaakov] python-wx
On Thu, 2020-05-14 at 11:02 +0100, Hamish McIntyre-Bhatty wrote: > Apologies for bumping this again, I'm just waiting for this to be done > before I start on wxPython 4, which is blocking progress for me doing > other things. If you're not interested in this fix, just let me know > and I'll move on to wxPython 4. > > I have re-built the packages using your new cygport as the starting > point, and it seems to work really well. I made some minor modifications > to include the license files and the new patches from Fedora. The new > files are available at https://www.hamishmb.com/files/cygwin-temp/ and I > have removed the previous attempt's files. This looks fine. > Seeing as I have no need to rebuild wxWidgets, I guess that can stay > under your maintainership until an update is needed, at which point > I'll be happy to pick it up. Let's discuss it then. -- Yaakov
Re: [ITA] mm-common
Am 14.05.2020 um 20:57 schrieb Ken Brown via Cygwin-apps: cygport file attached. I bumped the version to the latest upstream release, and I removed the custom src_compile, since the default src_compile now works (and the custom one doesn't, since the tarball no longer includes a configure script). Ken changed maintainer
Re: [ITA] libsigc2.0, [ITP] libsigc3.0
Am 14.05.2020 um 23:14 schrieb Ken Brown via Cygwin-apps: cygport files attached. I've updated libsigc2.0 to the latest release in the 2.0 series, and I've created libsigc3.0 as a new package, as Fedora does. Note: If you want to do a test build of the latter, you'll need to install the updated mm-common from the previous ITA. Ken changed maintainer and added 3.0
Re: cygport development
On Tue, 2020-05-12 at 16:59 +0200, Federico Kircheis wrote: > On 10/14/19 10:55 AM, Federico Kircheis wrote: > > On 13/10/2019 18.41, Achim Gratz wrote: > > > Federico Kircheis writes: > > > > I've sent the patches the 14.07.19, unfortunately I still got no answer. > > > > > > The cygport maintainer is rather busy with non-Cygwin related work these > > > days, I suppose. Anyway, one of the questions I have is why you need > > > these changes. Most build systems do not actually work when they > > > encounter a path with spaces if they use make under the hood, so fixing > > > cygport to grok such path locations isn't getting you much further I'd > > > think. Can you explain? > > > > Yep. > > > > I've built some software in my windows home directory. > > It contains a space. > > I expected it to work. > > > > Instead of failing with a clear error message, the build process deleted > > some unrelated files as it cd failed (or cd in the wrong directory, cant > > remember right now). > > > > I believe it is unacceptable to delete unrelated data. > > > > Even if it stated that there is no intention to support path with > > spaces, those scripts should fail fast and ideally with a clear error > > message. > > > > I found it easier to quote the offending variables, as not only spaces > > might cause issues. > > The merge request in the repository has been closed. > > I'm attaching the updated patch. This patch is clearly not limited to the protection of data, as it quotes variables that could in no way contain a space or have anything to do with file paths. As mentioned multiple times, using filenames ore directories with spaces is asking for trouble, and I have no interest in trying to support such a case. I'm willing to consider a *limited* patch that makes sure that cygport doesn't do something it shouldn't in that case, but that's about it. -- Yaakov
Re: [ITA] libpng
On Thu, 2020-05-14 at 11:17 -0400, Ken Brown via Cygwin-apps wrote: > Builds fine from Yaakov's cygport file, no update needed at present. Go ahead. -- Yaakov
Re: [ITA] mm-common
On Thu, 2020-05-14 at 14:57 -0400, Ken Brown via Cygwin-apps wrote: > cygport file attached. I bumped the version to the latest upstream release, > and > I removed the custom src_compile, since the default src_compile now works > (and > the custom one doesn't, since the tarball no longer includes a configure > script). This is fine, go ahead. -- Yaakov
Re: [ITA] libsigc2.0, [ITP] libsigc3.0
On Thu, 2020-05-14 at 17:14 -0400, Ken Brown via Cygwin-apps wrote: > cygport files attached. I've updated libsigc2.0 to the latest release in the > 2.0 series, and I've created libsigc3.0 as a new package, as Fedora does. > Note: > If you want to do a test build of the latter, you'll need to install the > updated > mm-common from the previous ITA. These look fine. Just curious, were you planning on doing the entire (or some part of) GTKmm stack? -- Yaakov
