Search Criteria
Package Details: mingw-w64-glib2 2.82.3-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/mingw-w64-glib2.git (read-only, click to copy) |
---|---|
Package Base: | mingw-w64-glib2 |
Description: | Low level core library |
Upstream URL: | https://gitlab.gnome.org/GNOME/glib |
Keywords: | glib2 gnome gtk gtk2 gtk3 mingw mingw-w64 |
Licenses: | LGPL-2.1-or-later |
Submitter: | brcha |
Maintainer: | Martchus |
Last Packager: | Martchus |
Votes: | 20 |
Popularity: | 0.000000 |
First Submitted: | 2012-06-13 19:15 (UTC) |
Last Updated: | 2024-12-10 22:33 (UTC) |
Dependencies (7)
- mingw-w64-gettextAUR
- mingw-w64-libffiAUR
- mingw-w64-pcre2AUR
- mingw-w64-zlibAUR
- git (git-gitAUR, git-glAUR) (make)
- mingw-w64-mesonAUR (make)
- python-packaging (make)
Required by (28)
- mingw-w64-atk
- mingw-w64-cairo
- mingw-w64-cairo-bootstrap
- mingw-w64-fluidsynth
- mingw-w64-fluidsynth-bin
- mingw-w64-gdk-pixbuf2
- mingw-w64-glib-networking
- mingw-w64-glibmm
- mingw-w64-graphene
- mingw-w64-gstreamer
- mingw-w64-gtk2
- mingw-w64-gtk3
- mingw-w64-gtk4
- mingw-w64-harfbuzz
- mingw-w64-json-glib
- mingw-w64-libadwaita
- mingw-w64-libcroco
- mingw-w64-libgtop
- mingw-w64-libnice
- mingw-w64-libsearpc
- mingw-w64-libsmf
- mingw-w64-libsoup
- mingw-w64-libsoup3
- mingw-w64-meanwhile
- mingw-w64-poppler (optional)
- mingw-w64-poppler (make)
- mingw-w64-shared-mime-info-bin
- qemu-guest-agent-windows (make)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 .. 10 Next › Last »
drakkan commented on 2021-04-19 11:04 (UTC)
Hi guys,
I'm having issues updating to glib 2.68.1, here is the diff. It builds fine on x86_64-w64-mingw32 but if fails on i686-w64-mingw32 with this link error. Do you have ideas? Thank your
Martchus commented on 2020-10-20 22:40 (UTC)
I've just restarted the build and now it works. Not sure why it previously failed. I suppose it is not worth investigating this further.
drakkan commented on 2020-10-20 20:47 (UTC) (edited on 2020-10-20 20:48 (UTC) by drakkan)
it is strange, it builds and links fine for me. I'll try to better investigate tomorrow
Martchus commented on 2020-10-20 20:30 (UTC)
Unfortunately I've got tons of linker errors: https://paste.opensuse.org/33853248
drakkan commented on 2020-05-19 20:41 (UTC)
done, it isn't a great gain
drakkan commented on 2020-05-19 13:21 (UTC)
OK, I'll add a
NO_EXECUTABLES
env var here too, thanks for the suggestionMartchus commented on 2020-05-19 12:55 (UTC) (edited on 2020-05-19 13:57 (UTC) by Martchus)
I don't need the executables of this particular package so the decision isn't very important to me. Generally it seems wrong to delete them just to save a few KiB on my floppy disk because they might be useful at some point after all. So far I've just ignored executables I didn't need and I don't see any problem with that.
By the way, the whole "let's not blindly delete all executables" idea came up when I started to use x264, x265 and ffmpeg. The executables contained by these packages are indeed useful to have. Even if ffmpeg isn't used directly after all it can be quite useful for checking quickly whether the libraries work. Maybe the same applies to other packages as well.
So from my point of view we should not have a general "keep EXEs" or "delete EXEs" rule which should be applied to all packages. Since EXEs can be useful I'd like to keep them in doubt but if really nobody uses them (which might be the case in this package) I have nothing against deleting them. By the way, the Qt 5 packages use the
NO_EXECUTABLES
environment variable to decide whether to keep EXEs so that's also an option.If you decide to remove EXEs in your packages, please do not bump the
pkgrel
in this case. I find it unnecessary to rebuild packages just to remove EXEs.drakkan commented on 2020-05-19 11:19 (UTC)
@xantares, no problem to remove the exes, but are we sure that noone need them? I use glib as gstreamer dependency so I don't need exes but executables like
glib-compile-resources
could be useful. @Martchus, @other, do you agree to remove exes from this PKGBUILD (and others that I maintain?), thanks!xantares commented on 2020-05-19 08:00 (UTC)
ok. could we remove the exes please ?
Martchus commented on 2020-05-18 09:00 (UTC)
I don't have a problem with using Git. Once one cloned it one just needs to fetch what's new so it isn't that bad and might even speed up subsequent updates.
And yes, if nothing speaks against it, it makes sense to follow what the official/regular PKGBUILDs do.
« First ‹ Previous 1 2 3 4 5 6 7 .. 10 Next › Last »