In the 2decb0e7 refactor we stopped
looking for non-Haskell `main-is` files in the hs-source-dirs and other
appropriate directories. This commit fixes that oversight.

Even if it is not intuitive that main-is-C-sources are searched in the
hs-source-dirs, we don't wish to break users relying on this behaviour
as there does not exist that strong of a motivation to do so.

Fixes #10168

Co-authored-by: sheaf <sam.derbyshire@gmail.com>

fix non-POSIX [[ ]]

Otherwise CI prints `validate.sh: 332: [[: not found` and the line
does nothing (but `validate.sh` continues to run), unless the
system shell is `ksh` / `bash` / `zsh`. This may explain
https://github.com/haskell/cabal/pull/10114#issuecomment-2178163927.

* missed the two changelog pointers

* Apply suggestions from code review

fixup! missed the two changelog pointers

Co-authored-by: ffaf1 <fa-ml@ariis.it>

* squash! and the other two changelogs

---------

Co-authored-by: ffaf1 <fa-ml@ariis.it>
(cherry picked from commit 82cad891)

Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

copy: Take into account extra-dyn-lib-flavours when copying bundled library

This fixes the DynWay case to match the other cases which take into
account extra-dyn-lib-flavours.

haddock-project: added `--all` switch

This matches the installation logic for the validate jobs.

Improve online docs for `includes:` field

Bases:
* https://downloads.haskell.org/~ghc/6.10.1/docs/html/users_guide/release-6-10-1.html
* https://hackage.haskell.org/package/Cabal-2.0.0.2/changelog
* https://github.com/haskell/cabal/commit/e1c39fc9ff4bf4eb8e956e2ee77da95d6cc73bbe

Added `--all` (`--haddock-all`) switches for compatibility with
`haddock` command.  `--haddock-all` alias is added, since that's what is
suggested by some warning messages.

Fixes #10051

haddock-project support public sublibraries

Link test suites & benchmarks from the index.html; Provide the right
`--base-url` flag for them.

`--use-unicode` is added to `cabal haddock` and `cabal haddock-project`.
One cannot simply use `--haddock-option="--use-unicode"` because it
makes haddock to fail when building indexes.

Haddock should know the sublibrary name rather than just the package.
For sublibraries `package_name:sublib_name` is used. The name is
recorded in the `.haddock` file and used when haddock creates the
`index.html` file, e.g. when called by `haddock-project` command.

When running haddock-project `extra-doc-files` should be copied to
a subdirectories of the `argOutputDir` corresponding to the component.
This doesn't affect `haddock` command.

This commit makes haddock-project handle sublibraries.

The commit changes how `cabal haddock` works, changing the layout
in the `dist-newstyle` folder.  With this change `haddock` subcommand
will install `package:sublib` component in a directory `package-sublib`
under `l/sublib/doc/html/`.

The main library must use the package name rather than `UnitId`,
otherwise the links from other sublibraries will not work.

Cabal: Add flag to ignore build tool dependencies

Add a flag to disable the hard requirement on the
build-tools-(depends) declared on the Cabal package.

When this flag is enabled (--ignore-build-tools), a build-tool which
can't be found does not block compilation.

Fixes #10061

Make clear when pkg-config is not present

When no pkg-config program was found, cabal would
claim that the package is not in the db, instead
of telling clearly that no pkg-config was found at
all.

Remove a stray line from cabal-install changelog

See https://github.com/haskell/cabal/pull/9696#discussion_r1651689945
ff.

Use `--io-manager=native` in `lib-suite` on Windows

* Changelogs for 3.12.1.0 (#10124)

* changelog for 3.12.1.0

* fixup! changelog for 3.12.1.0

* fixup! Changelogs for 3.12.1.0

Co-authored-by: Artem Pelenitsyn <a.pelenitsyn@gmail.com>

* fixup! changelog for 3.12.1.0

* fixup! changelog for 3.12.1.0

* fixup! Changelogs for 3.12.1.0

Co-authored-by: ffaf1 <fa-ml@ariis.it>

* fixup! Changelogs for 3.12.1.0

* fixup! Changelogs for 3.12.1.0

* fixup! Changelogs for 3.12.1.0

---------

Co-authored-by: Artem Pelenitsyn <a.pelenitsyn@gmail.com>
Co-authored-by: ffaf1 <fa-ml@ariis.it>
(cherry picked from commit 2067ed19)

# Conflicts:
#	release-notes/Cabal-3.12.0.0.md

* fixup! Changelogs for 3.12.1.0 (backport #10124)

---------

Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Add support for building profiled dynamic way

New options for cabal.project and ./Setup interface:

* `profiling-shared`: Enable building profiling dynamic way
* Passing `--enable-profiling` and `--enable-executable-dynamic` builds
  profiled dynamic executables.

Support for using `profiling-shared` is guarded behind a constraint
which ensures you are using `Cabal >= 3.13`.

In the cabal file:

* `ghc-prof-shared-options`, for passing options when building in
  profiling dynamic way

Other miscellenious fixes and improvements

* Some refactoring around ways so that which
  ways we should build for a library, foreign library and executable is
  computed by the `buildWays` function (rather than ad-hoc in three
  different places).

* Improved logic for detecting whether a compiler supports compiling
  a specific way. See functions `profilingVanillaSupported`,
  `dynamicSupported`, `profilingDynamicSupported` etc
  These functions report accurate infomation after ghc-9.10.1.

* Fixed logic for determining whether to build shared libraries. (see
  #10050)
  Now, if you explicitly enable `--*-shared`, then that will always take
  effect. If it's not specified then `--enable-executable-dynamic` will
  turn on shared libraries IF `--enable-profiling` is not enabled.

* Remove assumption that dynamically linked compilers can build dynamic
  libraries (they might be cross compilers.

* Query the build compiler to determine which library way is necessary
  to be built for TH support to work.
  (rather than assume all compilers are dynamically linked)

* An extensive test which checks how options for `./Setup` and
  `cabal-install` are translated into build ways.

Fixes #4816, #10049, #10050

* Disable arch-native flag when building releases that we distribute

* Use the constraints stanza

* Also disable the flag in cabal.validate.project

Skip tasty-quickcheck 0.11

API incompatible with our test suites

Depend on tar-0.6.3.0