Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Miscellaneous build fixes #184

Merged
merged 16 commits into from
Dec 3, 2023
Merged

Miscellaneous build fixes #184

merged 16 commits into from
Dec 3, 2023

Conversation

arch1t3cht
Copy link
Collaborator

Various small fixes to building and installer generation that came up on arch1t3cht/Aegisub .

The two most "controversial" commits are at the bottom:

  • Avisynth is broken anyway (at least for now), so the paths could also just be taken out
  • The commit that adds bundling of the hunspell dictionaries downloads them from Sourceforge (mainly to document where they came from), but that download fails quite frequently on the CI. So maybe it's better to just check them into the repo or use some newer dictionary.

arch1t3cht and others added 9 commits December 3, 2023 21:10
This makes it easier to notice when installer generation failed.
These are included in the Aegisub source files, so they need to be
generated before compiling.
Nasm's website goes down quite frequently, which breaks ci builds.
On native builds this is derived automatically, but on cross builds
it needs to be set explicitly.
This isn't actually set in luajit's Makefile. Maybe it was at some
point in the past, but there's no trace of it now.

Fixes arch1t3cht#98 .
This was done in Aegisub/Aegisub.
@CoffeeFlux
Copy link
Member

Leaving the paths commit in is fine. I'm less excited about the sourceforge bit, though I agree with the need to indicate where they came from. How big are they and how frequently are they updated?

@arch1t3cht
Copy link
Collaborator Author

They're around 250KB and weren't updated since... 2007.

@CoffeeFlux
Copy link
Member

How often do see you see the downloads fail? I'm leaning towards "just check in the dictionaries" but don't feel particularly strongly.

@arch1t3cht
Copy link
Collaborator Author

Looking through a couple of old CI runs, around 25% of the time

@CoffeeFlux
Copy link
Member

That's pretty bad. Are they hosted anywhere else we could use as a fallback?

@arch1t3cht
Copy link
Collaborator Author

I don't think so, they're pretty old after all and most applications just use SCOWL nowadays.

@CoffeeFlux
Copy link
Member

I really don't want to check in the dictionaries to the main repo -- can you dump them in a repo in TSTools and download from Github's CDN?

@arch1t3cht
Copy link
Collaborator Author

Yeah, done.

For now, this uses the same OpenOffice dictionaries that were used in
previous official releases, downloaded from
https://sourceforge.net/projects/openofficeorg.mirror/files/contrib/dictionaries/
In the future this could be updated to some newer dictionary like
SCOWL's.

Fixes arch1t3cht#21.
@CoffeeFlux CoffeeFlux merged commit 0e2a14c into master Dec 3, 2023
5 checks passed
@arch1t3cht arch1t3cht deleted the misc_build_fixes branch December 3, 2023 23:59
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.

3 participants