ac465d29b4
I'm taking a page from Dolphin's book, and including copies of each dependency's source code. This combines the ease of use of including pre-built libraries instead of needing to navigate a package manager - as is (or was) the case for MSVC - with the portability of using packages. Granted, this method's more of a jack of all trades, master of none, since it's *less* user-friendly than prebuilt packages (compilation times), and you don't get the per-distro compatibility fixes you'd get from a package manager. You can still use system libs if you want. In fact, it's still the default behaviour: compiling the libs manually is just a fallback. I'll add an option to force-enable this soon, however, since it's a nicer way to produce static MSYS2 builds than the hackish nightmare that I was using before. Not to mention, having my own copy of the sources means I can provide my own fixes and tweaks your package manager may not. For example, I can combine MSYS2's FreeType subpixel rendering with vcpkg's fix for SDL2 exporting its symbols in static builds. |
||
|---|---|---|
| .. | ||
| README | ||
README.lib ---------- This README file is a placeholder for library files on your system. Under Microsoft Windows a successful build of all projects and configurations will contain debug and release libraries for you to link to - all are built using the multi-threaded DLL settings. The DLL files (fltkdll.dll and fltkdlld.dll) required for a complete DLL-based binary distribution are located in the "visualc" directory. Under UNIX a single set of library files will be built, with or without debug information depending on the options you provided to the configure script.