Windows: Upload individual `.exe` Binaries in Workflow

[God-damnit-all]

Continuation of Individual Binaries in Workflow #8072

---

I, especially as a Windows user, feel like having these as individual binaries would be incredibly useful.

I'm aware I can build it myself, but I feel like uploading them should be part of the workflow.
Originally posted by @God-damnit-all in #7496

The workflow is a very complex beast that I have trouble making sense of, so while I can build them myself, I have no idea if they're being built the same way this repo is doing it.

If possible, could the workflow output the individual binaries that are built?
Originally posted by @God-damnit-all in #8072

---

Fixed with #10338
Originally posted by @cakebaker in #8072

---

@cakebaker closed this as completed #8072 (comment)

---

This is currently Linux-x64-glibc only. @God-damnit-all Please reopen if you are still need *.exe with different title.
Originally posted by @oech3 in #8072

---

I actually do need the individual .exe binaries, so here's the new issue.

[oech3]

Please add "individual" to title. coreutils.exe is already provided.
Also note that you can manually hardlink using corutils --list.

[God-damnit-all]

Please add "individual" to title. coreutils.exe is already provided.

My bad, I meant to include it.

[oech3]

What is the usecase for this? It might able to suggest alternative until this was added (would not happen soon).

[oech3]

I'll work on this after #10352 was merged. Because we builds many duplicated Linux binaries on the CI if we published individual *exe before fixing it.

[oech3]

I tried to cross-build *.exe at makefile CI (since it is already using energy for building duplicated individual Linux binaries with release profile). But I failed.

[God-damnit-all]

I tried to cross-build *.exe at makefile CI (since it is already using energy for building duplicated individual Linux binaries with release profile). But I failed.

I don't understand why you can't just reuse the same individual binaries that are built for the binary size benchmarking. It's as simple as creating a job that waits on that one to complete.

If it was from a completely separate workflow you could take these steps:

• ArcticLampyrid/action-wait-for-workflow@v1.3.0
  • This would be used to wait for a workflow matching the same commit to finish.
• dawidd6/action-download-artifact@v13
  • actions/download-artifact@v7 also works but is less flexible.
• GeekyEggo/delete-artifact@v5
  • Cleanup so the files don't have to be retained for any length of time beyond what is necessary.

But the individual binaries are built within the same workflow, so none of that should be necessary.

[oech3]

We are not building individual *.exe currently on the CI. Also if we build them at different CI building coreutils.exe, it has bad efficient (we are building individual linux bins 3 times with release profile independentaly... very bad!).

So I'm waiting #10403 which deduplicated 2 build.

[God-damnit-all]

We are not building individual *.exe currently on the CI. Also if we build them at different CI building coreutils.exe, it has bad efficient (we are building individual linux bins 3 times with release profile independentaly... very bad!).

So I'm waiting #10403 which deduplicated 2 build.

Okay yeah, I misremembered, it was the tests that had individual binaries built:

coreutils/.github/workflows/CICD.yml

Lines 833 to 841 in c3e3847

	- name: Test individual utilities
	if: matrix.job.skip-tests != true
	shell: bash
	run: |
	## Test individual utilities
	${{ steps.vars.outputs.CARGO_CMD }} ${{ steps.vars.outputs.CARGO_CMD_OPTIONS }} test --target=${{ matrix.job.target }} \
	${{ matrix.job.cargo-options }} ${{ steps.dep_vars.outputs.CARGO_UTILITY_LIST_OPTIONS }}
	env:
	RUST_BACKTRACE: "1"

I recall this outputting the binaries, and as I understand, tests normally do so unless you specify certain parameters that it doesn't seem to have been defined here.

Here's what it seems to be now, I don't know how it differs:

coreutils/.github/workflows/CICD.yml

Lines 1245 to 1254 in e5bf248

	- name: build and test all programs individually
	shell: bash
	run: |
	CARGO_FEATURES_OPTION='--features=${{ matrix.job.features }}' ;
	for f in $(util/show-utils.sh ${CARGO_FEATURES_OPTION})
	do
	echo "Building and testing $f"
	cargo test -p "uu_$f" -p coreutils --features=$f --no-default-features
	done