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

Update build instructions to correctly configure dotnet #520

Closed
wants to merge 0 commits into from

Conversation

Wills2022
Copy link
Contributor

@Wills2022 Wills2022 commented Jul 23, 2024

Description

Previous build instructions would not link dotnet library if the arcade machine was configured without a desktop environment. In a desktop-less environment ~/.bashrc is not loaded but ~/.bash.bash_profile is. This fixes this problem too.

The old .md file explicitly numbers points rather than using 1., 1.,1. to generate them automatically. This is a problem in this doc generally, but I will split that amendment into a separate pull if it's deemed an issue.

**update
The arcade cabinet build instructions direct users to a broken link on the Splashkit.io docs site.
The URL points to "https://splashkit.io/articles/installation/ubuntu/"

But this page as changed to https://splashkit.io/installation/linux/ at some point. It's possible to navigate to the correct page from the 404 in a couple of clicks, but there's no reason not to update this URL to point to the correct place.

Also replaced an ugly full link to sharepoint with an embedded link for better readability.

There's also a broken image in the "Configure Start CLI on Boot and Network Manager" section that pointed to a typo'd file that i have corrected.

The other links seem to be free from link rot.

Type of change

  • Documentation (update or new)

How Has This Been Tested?

.md file has been tested locally to ensure formatting is consistent and remains unbroken.

Testing Checklist:

  • Tested in latest Firefox

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have requested a review from ... on the Pull Request

@Wills2022
Copy link
Contributor Author

Due to messing up some branching I have recreated this pull here:
#523

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.

1 participant