question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add Linux requirements to "Requirements" chapter in README.md

See original GitHub issue

When running osu!lazer on Linux, there must be BASS(libbass.so) and BASS FX(libbass_fx.so) in /usr/lib64(for 32-bit system, the path should be /usr/lib), or the game will crash and exit when starting.

The BASS’s and BASS FX’s archive can be downloaded from Un4seen. The libbass.so(or libbass_fx.so) lives in x64/ directory in 64-bit system or in the root directory of the archive in 32-bit system.

I’ve looked in the package manager in my system(Fedora 28), but I didn’t find anything about “bass” or “bassfx”.

BTW, I’m sorry for my bad English because English is not my native language.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
LastExceedcommented, Aug 22, 2018

This problem has been addressed before. Unfortunately I can’t find the particular issue where it was mentioned (as there have been lots of issues and PRs about problems with the BASS library on linux), but the closing note was that this problem won’t occur when osu! is published as a self-contained program and therefore won’t be addressed any further, so this issue can be closed.

0reactions
morguldircommented, Aug 25, 2018

You can’t package it anyway because of how un4seen manages the releases.

Also, if we do what is suggestd in https://github.com/ppy/osu-framework/issues/1638, this issue will be fixed.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Sysadmin university: How to write a README file
Writing the ever-popular README file isn't as straightforward as you might think. This guide makes it easy.
Read more >
How to Write a Good README File for Your GitHub Project
Provide a step-by-step description of how to get the development environment set and running.
Read more >
Writing a README
The name README is self-explanatory — it's a document that users should read to get more information about the contents of a project....
Read more >
Make a README
A README is a text file that introduces and explains a project. It contains information that is commonly required to understand what the...
Read more >
What is README.md File?
A README file is an essential guide that gives other developers a detailed description of your GitHub project. You may be wondering, ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found