Skip to content

Conversation

@DaleStan
Copy link
Collaborator

This fixes #478, at least for ./build.sh. Attempts to use dotnet run --project Yafc from clean source are still broken, but it doesn't appear anyone is trying to do that.

Other solutions I tried all seemed to have more pain than benefits: dotnet build FactorioCalc.sln --target:Yafc:Publish -r win-x64 would try to run an explicitly x64 version of I18n.Generate on arm64 processors, or vice versa. Using project-level dependencies requires a #if to prevent introducing a warning, and adds extra files to the publish folders.

@DaleStan DaleStan requested a review from veger May 19, 2025 13:05
@DaleStan DaleStan requested a review from shpaass as a code owner May 19, 2025 13:05
Copy link
Owner

@shpaass shpaass left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the fix!

@veger
Copy link
Collaborator

veger commented May 19, 2025

Attempts to use dotnet run --project Yafc from clean source are still broken, but it doesn't appear anyone is trying to do that.

Uhm... I do..! 😛 But I will manage!

@shpaass shpaass merged commit 977cc81 into shpaass:master May 19, 2025
1 check passed
@DaleStan DaleStan deleted the 478-unable-to-build branch May 19, 2025 17:14
shpaass added a commit that referenced this pull request Aug 27, 2025
#486 broke (or, maybe 'failed to fix') `dotnet build Yafc` and `dotnet
run --project Yafc` on clean source or after adding new i18n keys. This
fixes those commands again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unable to build

3 participants