On Wednesday, 16 September 2020 at 09:33:05 UTC, wjoe wrote:
On Tuesday, 15 September 2020 at 18:49:48 UTC, Iain Buclaw
wrote:
On Tuesday, 15 September 2020 at 16:05:53 UTC, wjoe wrote:
[...]
Note the comments in the build function, only the dependencies
of the C++ and D libraries are built. So you'll need to do
`make all` in order to cover anything that was deliberately
skipped.
Does that mean that building with build_bootstrap="enabled" is
insufficient ?
Because I exported that variable in the Cirrus CI configuration
and set it to 'disabled' for GDC and Unittest tasks and to
'enabled' for the Package task.
build_bootstrap=enabled should be OK. Even better, it configures
with --enable-checking=release.
Packaging in the Unittest task didn't work unfortunately
because building that with bootstrap enabled exceeded the 2h
time limit.
So now there are 3 tasks.
- Build GDC testsuite
- Build Unittests
- Build Package task
At the moment I made the Package task depend on the Unittest
task, but GDC and Unittest run in parallel.
I guess best practices would ask to make Unittest depend on GDC
to go easy on resources.
However, that would blow up the build cycle to something over
3.5h.
All tasks could be ran in parallel as there's no dependencies
between them. The Package task though I'd imagine should be
reserved for the release branches, so it's only ran infrequently.
