Sparkle
glibc_version_header
Sparkle | glibc_version_header | |
---|---|---|
15 | 8 | |
7,144 | 767 | |
0.8% | - | |
8.3 | 0.0 | |
8 days ago | 3 months ago | |
Objective-C | C++ | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Sparkle
- Sparkle: A software update framework for macOS
-
Flatpak Is Not the Future
* i use appimagelauncher[1] to integrate with my menus etc but sometimes it works and sometimes it doesn't? i haven't really figured out the rhyme or reason
[0] https://sparkle-project.org/
- The PD launcher issue is not permanent!
-
One line of code that did cost $8k
I'm glad I'm not the only one that thinks checking every 5 mins is a little bit excessive!
Seeing as it's macOS only is there even any reason to roll your own update mechanism when you can use the Sparkle framework [1]?
[1]: https://sparkle-project.org/
-
What is the best method you guys use to distribute desktop apps over your websites?
The bucket contains dmg files and an appcast.xml that allows for updates. I'm using the auto_updater package, which in turn uses the popular Sparkle library.
-
Do I have to enroll in Apple Developer Program to distribute macOS applications as a final product?
Our build process is automated using fastlane. That handles building and testing the app as well as signing, notarizing and uploading to Amazon S3. We distribute via a link on our website -- Callisto. Updates are handled using Sparkle. We have a custom built appcast generator as part of our website that reads the S3 bucket and builds the feed that Sparkle uses.
- Transmission 4.0.0 beta 1 is out
-
Auto Updater
Something like Sparkle but for Node.
- Sparkle 2.0: Secure and reliable software update framework for macOS
glibc_version_header
-
Flatpak Is Not the Future
One major headache with trying to run precompiled binaries on Linux is that if they were compiled using a newer version of glibc than the target machine, they won't be able to run. Back while working on Factorio, I was trying to get around this problem with endless Docker containers, but coworker Wheybags came up with a much solution to this, which is simply to, at compile time, link to the oldest compatible version of glibc: https://github.com/wheybags/glibc_version_header
-
Win32 Is the Only Stable ABI on Linux
If what you're doing works for you, great, but in case it stops working at some point (or if for some reason you need to build on a current-gen distro version), you could also consider using this:
https://github.com/wheybags/glibc_version_header
It's a set of autogenerated headers that use symbol aliasing to allow you to build against your current version of glibc, but link to the proper older versioned symbols such that it will run on whatever oldest version of glibc you select.
-
Because cross-compiling binaries for Windows is easier than building natively
There are other approaches like https://github.com/wheybags/glibc_version_header or sysroots with older glibc, e.g. https://wiki.gentoo.org/wiki/Crossdev - you don't need your whole XP, just the the system libs to link against.
Sure, having a nice SDK where you can just specify the minimum vesion you want to support would be nice but who do you expect to develop such an SDK? GNU/glibc maintainers? They would rather you ship as source. Red Hat / SUSE / Canonical? They want you to target only their distro. Valve? They decided its easier to just provide an unchaning set of libraries since they need to support existing games that got things wrong anyway and already have a distribution platform to distribute such a base system along with the games without bundling it into every single one.
- Glibc Version Header Generator
-
Thank You, Valve
A few links gathered from a quick google search as a primer:
http://stevehanov.ca/blog/?id=97
https://www.evanjones.ca/portable-linux-binaries.html
https://insanecoding.blogspot.com/2012/07/creating-portable-...
https://rpg.hamsterrepublic.com/ohrrpgce/Portable_GNU-Linux_...
https://github.com/wheybags/glibc_version_header
In other words: there are a lot of steps and a lot of gotchyas to doing this that you're glossing over. Linux userland libraries are generally designed with the intention that an army of third-party maintainers will integrate all of this desperately developed software together and place it in a repo. Naturally every distribution wants to do things a little differently too, and they have a habit of changing it up every couple years. When you try to step out of that mold things unsurprisingly become more difficult. Whereas Windows, Mac, Android, etc. have been designed since the beginning not to require that sort of thing and it is consequently a much, much more straightforward process.
I'm curious why, since you seem to believe the process is so straight-forward, you think it is that so few people distribute a simple binary? Why were Flatpak and AppImage invented?
-
“LLVM-Libc” C Standard Library
> Binaries compiled against today's glibc can fail to run on a machine that hasn't been updated since last week because they rely on a new / different symbol.
Note, however, that it is a Glibc bug (modulo Drepper’s temper) if the reverse happens: Glibc symbol versioning ensures that binaries depending on an old Glibc (only) will run on a new one. So the proper way to build a maximally-compatible Linux executable would be to build a cross toolchain targeting an old Glibc and compile your code with it. Unfortunately, the build system is hell and old Glibcs doesn’t compile without backported patches, so while I did try to follow in the footsteps of a couple of people[1–4], I did not succeed.
Mass-rebuilds still happen with other ecosystems, though. GHC-compiled Haskell libraries are fine-grained and not ABI-stable across compiler versions, so my Arch box regularly gets hit with a deluge of teensy library updates, and Arch is currently undergoing a massive Python rebuild (blocking all other Python package updates) behind the scenes as well.
[1]: https://github.com/wheybags/glibc_version_header (hack but easy and will probably work most of the time)
What are some alternatives?
OpenEmu - 🕹 Retro video game emulation for macOS
holy-build-box - System for building cross-distribution Linux binaries
Hyperion - In-app design review tool to inspect measurements, attributes, and animations.
overwatch-aimbot - 🔫🎮 An OpenCV based Overwatch Aimbot for Windows
simde - Implementations of SIMD instruction sets for systems which don't natively support them.
osxcross - Mac OS X cross toolchain for Linux, FreeBSD, OpenBSD and Android (Termux)
keypad-layout - Control window layout using Ctrl + Numeric Keypad on macOS
manylinux - Python wheels that work on any linux (almost)
libtorrent - an efficient feature complete C++ bittorrent implementation
mach - zig game engine & graphics toolkit
React-Paintinglite - 🚀🚀🚀Support for ORM operation,Customize the PQL syntax for quick queries,Support dynamic query,Secure thread protection mechanism,Support native operation,Support for XML configuration operations,Support compression, backup, porting MySQL, SQL Server operation,Support transaction operations. [Moved to: https://github.com/CreaterOS/ReactPaintinglite]
musl-cross-make - Simple makefile-based build for musl cross compiler