Tree: e9fccd9932

2.4-stable

2.6-stable

2.8-stable

3.0-stable

dependabot/github_actions/dot-github/workflows/actions/download-artifact-4.1.7

dev

master

2.4

2.6

2.8

2.9.1

3.0

3.1.0

3.1.1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'e9fccd9932'

${ noResults }

Commit Graph

2 Commits (e9fccd99320d3582d07b08dee4f5145af8d148ae)

Author	SHA1	Message	Date
Hamish Coleman	670aadcf1b	Address CMake config ordering requirements (#942) For a moment there, I was starting to think that I might have found a good feature in cmake, but then it turned out that it had specific ordering requirements and strange cryptic functions that error out in mysterious ways. If I am going to have an antique build engine with special quirks that I must learn in order to use it, I may as well choose the one that is not also trying to be clever and hiding its internal magic from me. Which means that I still prefer Makefiles - they are more debuggable.	3 years ago
Hamish Coleman	028d6f9b07	Harmonise configuration defaults (#937) * Ensure all options start off for cmake too * Attempt to make the build time config logic in the cmake process match the makefile process * Add a simple muscle memory helper for cmake * Ask them what they are smoking, then tell them to put it out * Avoid occasional stale package cache errors	3 years ago