xrepo
lhelper
xrepo | lhelper | |
---|---|---|
1 | 2 | |
333 | 11 | |
3.0% | - | |
0.0 | 7.4 | |
over 1 year ago | about 2 months ago | |
Shell | Shell | |
Apache License 2.0 | - |
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.
xrepo
-
C++Now 2022: Searching for Convergence in C++ Package Management
I have a suggestion that almost nobody knows about. It's called "xrepo" and it's designed to go a long with "xmake" (which is an excellent build tool), but xrepo is technically seperate from xmake. Literally, way too much info to put it all here, but you (and everyone) should SERIOUSLY check it out. Xmake: https://github.com/xmake-io/xmake/ Xrepo: https://github.com/xmake-io/xrepo
lhelper
-
C++ Package Managers: The Ultimate Roundup
I have made my own tool to solve this problem:
https://github.com/franko/lhelper
It is currently used by nobody except me but it serves me well.
Its strong points are:
- it works on macOS, Linux and Windows
-
Building Outer Wonders for Linux
I agree, for their use case they should have linked to SDL2 as a static library. It was the best option instead of patching the binary with patchelf.
I think many developers don't know about static libraries. For some reason they think they have to use a shared libraries. This is probably due to many tutorial saying something like: download the SDL2 library from there, it is provided as a shared library, here the instructions to use it with Visual Studio.
The way I do is with static libraries, I ship a single executable, all the third-party libraries are linked in as static libraries. The only dynamic libraries the exectuable will use are the standard libraries that are part of the OS.
I do this very easily with the help for lhelper:
https://github.com/franko/lhelper (I am the author)
that has recipes to build many libraries including SDL2. It builds the library on you system using your compiler and your settings. By default it will build static libraries so you don't have to bother distributing additional dynamic libraries.
What are some alternatives?
pkgconf - package compiler and linker metadata toolkit
dockcross - Cross compiling toolchains in Docker images
xmake.sh - A script-only build utility like autotools
manylinux - Python wheels that work on any linux (almost)
itch - 🎮 The best way to play your itch.io games
SDL - Simple Directmedia Layer
OpenRCT2 - An open source re-implementation of RollerCoaster Tycoon 2 🎢
hexchat - GTK+ IRC client
the-bread-code - Learn how to master the art of baking the programmer way.
Cheesemake - It is not meant to be taken literally, it refers to any manufacturers of dairy products.