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

Custom Wine prefix location #103

Open
nixRidge opened this issue Dec 22, 2023 · 3 comments
Open

Custom Wine prefix location #103

nixRidge opened this issue Dec 22, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@nixRidge
Copy link

I couldn't find a way to do this already, so I'm hoping it's ok that I request an option to specify a custom Wine prefix location. Having it in ~/.xlcore is a bit inconvenient, and the home directory isn't on my best harddrive.

Of course, I could just move the prefix and symlink the directory to ~/.xlcore/wineprefix, but for the sake of user friendliness, this would be a really great option.

@Blooym Blooym added the enhancement New feature or request label Dec 22, 2023
@GingerBobRoss
Copy link

Bumping this issue as i have been trying to get my game to run on Wine (system) version 9.8 or wine-staging.
Ive updated my prefix to 9.8/staging and manually set the location to where xlcore's prefix is, but every time it reports that the directory does not have a lib32 binary or something close to that.

@nixRidge
Copy link
Author

nixRidge commented May 14, 2024

every time it reports that the directory does not have a lib32 binary or something close to that

Sounds like less of an issue with the path XIVLauncher loads the prefix at. How are you starting XIVLauncher, and where's the prefix? Have you properly symlinked the prefix to ~/.xlcore/wineprefix?
Error messages would be helpful too.

@reiichi001
Copy link
Contributor

Bumping this issue as i have been trying to get my game to run on Wine (system) version 9.8 or wine-staging. Ive updated my prefix to 9.8/staging and manually set the location to where xlcore's prefix is, but every time it reports that the directory does not have a lib32 binary or something close to that.

It sounds like you've updated your wine bin path in xivlauncher's settings (or should be doing that instead of running wine directly from your terminal), but that's the application binaries, not the prefix. This is not related to the wine prefix location and should not be a part of this issue.

Which wine binaries and whether or not you're using a system package over something built through TKG with our wine-xiv patches will matter. (This is why people use @rankynbass's builds - but as a reminder, they're not officially supported). You are better off following up on this in our Linux channel on our Discord server, @GingerBobRoss

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants