Switch to using build-type Configure instead of Custom. #20
Conversation
Doing so allows for easier building on the HaLVM, as it doesn't require Cabal to be smart about cross-compilers. The new configure script is a straightforward reimplementation of the old Setup.hs semantics into autoconf form. Both the configure.ac and configure form are included for simplicity.
|
Can anyone confirm this works trivially on Windows (32/64)? |
|
On my computer (64bit Windows 7, 32bit compiler) it crashes conftest.exe. |
|
I know this is an old thread, but would you be interested in helping to try to revive this work? I have a large project I'm trying to cross-compile (x86-linux to aarch64-linux) where this library is the one remaining blocker. I'd like to see if this sort of approach can be made to work before I resort to At a glance, it looks like the custom setup here isn't doing anything which should be out of scope for autoconf? |
|
@georgefst is not allowed to run commands |
…rpreter`) As it stands, we also need changes to `entropy`, but I'll manage that separately. Hopefully by reviving haskell/entropy#20. Note that the custom setup is only used for `cabal-doctest`, so we really can just safely remove it. This is essentially the same issue as cdepillabout/pretty-simple#82. Seeing as all the TH is just for `makeLenses`, in an ideal world we really ought to just be able to run on the host: see ghc-proposals/ghc-proposals#243. The changes to the two `.hs` files are from dumping the TH splices (and manually (well, with _some_ help from HLS) adding a load of qualified imports). The splices can be found in `dist-newstyle` after adding this to `cabal.project`: ``` package wreq ghc-options: -ddump-splices -dth-dec-file ```
|
Okay, it seems that simply disabling the custom setup is enough to get things to build, and, AFAICT, work. Is the setup script not always necessary? EDIT: See also #42. |
|
@georgefst is not allowed to run commands |
Doing so allows for easier building on the HaLVM, as it doesn't require Cabal to
be smart about cross-compilers. The new configure script is a straightforward
reimplementation of the old Setup.hs semantics into autoconf form. Both the
configure.ac and configure form are included for simplicity.