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

Kristall: x86 support, less RAM for building, etc. #6192

Merged
merged 2 commits into from
Sep 16, 2021

Conversation

SOURCE_FILENAME="kristall-$portVersion-tar.gz"
SOURCE_DIR="kristall-$srcGitRev"
ADDITIONAL_FILES="kristall.rdef.in"

ARCHITECTURES="all !x86_gcc2"
SECONDARY_ARCHITECTURES="?x86"
ARCHITECTURES="!x86_gcc2 x86_64"
Copy link
Contributor

Choose a reason for hiding this comment

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

@waddlesplash we'll be seeing this in the near future ...

Copy link
Member

Choose a reason for hiding this comment

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

Indeed, something to watch out for.

Copy link
Contributor

Choose a reason for hiding this comment

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

We can't all check architectures our selves (don't have a riscV/arm* environment for those), and for those some of these will depend on people with access to them to see if they actually build?

Copy link
Member

Choose a reason for hiding this comment

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

The point of all is that most software will likely build on riscv or arm if it builds on x86_64. We don't necessarily need to check every single package on every architecture before we publish it; we can just see if it builds and fix it if it needs to be.

@Begasus Begasus merged commit 0d3dc2e into haikuports:master Sep 16, 2021
@win8linux win8linux deleted the kristall branch September 28, 2021 06:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants