Remove custom setup to enable cross-compilation #107
Conversation
georgefst
force-pushed
the
cross-compile
branch
from
20e114a to
6fb9b28
Compare
georgefst
force-pushed
the
cross-compile
branch
from
6fb9b28 to
49fadf8
Compare
For some reason selecting "latest" Cabal leads to 3.10, despite 3.12 (recommended for GHC 9.10) being available.
georgefst
force-pushed
the
cross-compile
branch
from
7a30cd5 to
ef6aef7
Compare
|
@cdepillabout I've updated this so that the doctests run on CI, following the approach suggested by @Kleidukos in #82. Would you consider merging this? I know it doesn't pass your criteria from #129 (comment), namely working with Stack and Nix, but the old approach is an unmaintained hack, and even the better long-term solution, i.e. setup hooks (alluded to in #129 (comment)), may not be supported by either of those for a long time either. I've lost track of how many projects I've had to point to this branch, especially in the last few months as I've been doing a lot with the Wasm backend. (Note to self: if we do merge this, add something to docs about installing the binaries, and if not then cherry-pick the first commit in to a new PR.) |
|
@georgefst This PR works for me. Could you add a section at the bottom of the README describing how to run the doctests? (I'm guessing just doing Other than that, this looks good to me. Feel free to merge it in and cut a release. |
## 4.1.3.0
* Remove custom setup. This makes cross-compiling `pretty-simple` a lot more
straightforward. No functionality has been lost from the library, since the
custom setup was only used for generating tests.
[#107](cdepillabout/pretty-simple#107)
This is really just a placeholder. Until we have a new approach to doctests, this serves as a branch to point to for projects where I need to cross-compile pretty-simple. I'll periodically rebase it on master.Closes #82.