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

Example can't run lack of game.dat? #56

Open
mindoff6502 opened this issue May 8, 2019 · 5 comments
Open

Example can't run lack of game.dat? #56

mindoff6502 opened this issue May 8, 2019 · 5 comments

Comments

@mindoff6502
Copy link

I'm useing Window 7,VS2017,successfully compile halley-template example.
But while run the app,It says

Unhandled exception : Unable to load resource .../halley-template/assets/game.dat

I checked folder there is no game.dat file there,so what should I do to run a success example?

@AnbyKatz
Copy link

AnbyKatz commented May 9, 2019

After building you need to import assets and then build again. For windows, after building the command is apparently: (Do this inside halley/bin/ after building the build tools)

halley-cmd.exe import /full/path/to/game/repo/root /full/path/to/halley/repo/root

this should generate the game.dat file in the assets/ folder. Then simply build again and it should work.

@mindoff6502
Copy link
Author

OK,thanks for reply.

Successfuly get game.dat,and now get new error...what is happening?

Halley has aborted with an unhandled exceptions:Process aborting with signal #SIGSEGV (11)

It seems halleyproj.exe does not cry for game.dat but this happened.

@AnbyKatz
Copy link

Not 100% sure but first make sure that you have all the necessary libraries eg:
boost, sdl, freetype, yaml-cpp
Next make sure that when you build, you use a command along the lines of (Im on Linux so it'll be a tiny bit different):
cmake -DHALLEY_PATH=../halley -DBUILD_HALLEY_TOOLS=1 -DBUILD_HALLEY_TESTS=0 \ -DCMAKE_INCLUDE_PATH=/usr/include \ -DCMAKE_LIBRARY_PATH=/usr/lib \ -DBoost_USE_STATIC_LIBS=1 \ -DBOOST_INCLUDEDIR=/usr/include/boost ..
Your project should be organised in the following way generally:

  • Project
    • build
    • halley (the engine itself)
    • src
    • assets_src
    • halley_project
      (Some other stuff)

Try again from a clean build (delete the build and bin folders in both halley and your project). Use a similar command as above to make, then type make (in the build directory). After its made, do the import assests thing and then type make again (in the build directory).

Hopefully that helps... maybe?

@LoveGlitchCoffee
Copy link

I'm on MacOS, just wanted to check. I ran ./halley_cmd from halley/bin to import assests, but it created a assets_unpacked folder in root instead ... thats not expect is it XD additionally, game.dat was not generated :P

@JoelOtter
Copy link
Contributor

@ParityB1t Bit of a weird one, but on macOS the halley-cmd import requires full paths rather than relative ones. E.g.

./halley/bin/halley-cmd import "$(pwd)" "$(pwd)/halley"

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

No branches or pull requests

4 participants