pugl.git - Pugl GUI library

Age	Commit message (Collapse)	Author	Files	Lines
2023-01-14	MacOS: Fix Vulkan backend build	David Robillard	1	-1/+2

2023-01-14	Allow applications to specify the Vulkan library path	David Robillard	1	-2/+4
	I don't know if vendoring the Vulkan library is appropriate, but regardless, this allows applications to set the name to whatever they want, or specify an absolute path, just in case the standard value baked into Pugl isn't the right one in some situation.
2022-06-08	Separate private and public function implementations	David Robillard	1	-1/+1

2022-04-21	Remove unused return type from backend destroy methods	David Robillard	1	-3/+2
	Since this is essentially a destructor, I don't think there's anything really useful to do with errors here, and in practice no backends actually used it anyway.
2021-12-17	Adopt REUSE machine-readable licensing standard	David Robillard	1	-15/+2
	See https://reuse.software/ for details.
2021-01-02	Use email address instead of website for attribution	David Robillard	1	-1/+1

2021-01-02	Simplify clang-format configuration and format all code	David Robillard	1	-85/+83

2020-11-26	Remove file documentation	David Robillard	1	-4/+0
	These will not be used in the Sphinx documentation, and most were self-explanatory and only there to make the Doxygen index look nice anyway. Where there was actually useful information, it has been preserved as regular comments.
2020-11-25	Pass vkGetInstanceProcAddr to puglCreateSurface instead of a loader	David Robillard	1	-3/+3
	This allows puglCreateSurface() to be used with some other loader, or when linking to Vulkan at compile time.
2020-10-30	Simplify header names	David Robillard	1	-2/+2

2020-10-30	Move implementation source files to a conventional src directory	David Robillard	1	-0/+217
	I think this attempt to be optionally header-only was misguided, particularly installing source code to the system include path. Typically anyone vendoring code just includes the repository and builds from there anyway. This commit moves all the implementation code to a typical src directory (Don't Be Weird). I still think there is some value in simple "inline" deployment, but that would be better achieved another way, like producing a single-file amalgamation that builds anywhere, ala sqlite.