Delete cabal.project

[clyring]

It seems to no longer do anything useful, and it also prevents CI from detecting that include/bytestring-cpp-macros.h was not getting picked up by cabal sdist.

[clyring]

The cabal package description docs do not provide me much clarity on the relevant-looking package description fields includes and install-includes. But includes: bytestring-cpp-macros.h doesn't result in cabal sdist picking up the file while install-includes: bytestring-cpp-macros.h does.

"Note that in order for files listed in install-includes to be usable when compiling the package itself, they need to be listed in the includes field as well."

This doesn't appear to be true? Or is it a fluke that this appears to work for me?

This is in contrast to install-includes, which lists header files that are intended to be exposed to other packages that transitively depend on this library.

These macros are probably not very useful to expose to downstream users.

Maybe I should just use extra-source-files instead.

[Bodigrim]

unix includes headers such as HsUnix.h three (!) times:

• extra-source-files,
• includes
• install-includes

It does not harm, better be safe than sorry ;)

[clyring]

CI seems to say there is, in fact, harm done.

[clyring]

I see this in the cabal build -v3 output:

/usr/bin/gcc returned ExitFailure 1 with error message:
In file included from /tmp/846-14.c:2:
./include/bytestring-cpp-macros.h:2:2: error: #error "bytestring-cpp-macros.h
does not work in C code yet"
2 | #error "bytestring-cpp-macros.h does not work in C code yet"
| ^~~~~

It seems that cabal-install believes bytestring-cpp-macros.h is broken because it is not meant for inclusion in C code.