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

What is the intended approach for an installed launch? #610

Closed
boombatower opened this issue Sep 14, 2016 · 5 comments
Closed

What is the intended approach for an installed launch? #610

boombatower opened this issue Sep 14, 2016 · 5 comments
Labels
area: buildsystem Related to our cmake/python buildsystem bug Behaving differently as it should behave packaging Bundling openage for distribution
Projects
Milestone

Comments

@boombatower
Copy link
Contributor

boombatower commented Sep 14, 2016

openage.desktop file:

Exec=openage %u
Path=.openage

Which no longer works since qml files are also expected to be sitting next to ./assets. On an installed system the qml files are in /usr/share/openage while the assets are in ~/.openage/assets. Short of symlinking the assets into /usr/share/openage and launching the game from that directory there does not appear to be a way to run it outside of a development setup where everything is in a single directory.

Seems like there needs to be some path discovery or somesuch.

@VelorumS
Copy link
Contributor

That's probably because I've mixed up global_asset_dir and the game asset directory. Should use global_asset_dir in engine.cpp.

@TheJJ TheJJ added bug Behaving differently as it should behave area: buildsystem Related to our cmake/python buildsystem packaging Bundling openage for distribution labels Sep 26, 2016
@TheJJ
Copy link
Member

TheJJ commented Sep 26, 2016

Currently the installed version is really untested, we have to spend some time there to get it working smoothly.

@zuntrax zuntrax added this to the v0.4.0 milestone Jan 23, 2017
@TheJJ TheJJ moved this from issues to packaging in buildsystem Feb 15, 2017
@TheJJ
Copy link
Member

TheJJ commented Feb 25, 2017

Fixed by #723

@TheJJ
Copy link
Member

TheJJ commented Mar 17, 2017

@boombatower please test #723, it should improve lots of things and allow an installed run.

@TheJJ
Copy link
Member

TheJJ commented Mar 21, 2017

#723 is merged.

@TheJJ TheJJ closed this as completed Mar 21, 2017
@zuntrax zuntrax moved this from packaging to done in buildsystem Jan 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: buildsystem Related to our cmake/python buildsystem bug Behaving differently as it should behave packaging Bundling openage for distribution
Projects
buildsystem
  
done
Development

No branches or pull requests

4 participants