Opened 4 years ago

Last modified 4 years ago

#61491 closed defect

supertux @0.6.2: No such file or directory: "/Applications/MacPorts/SuperTux.app/Contents/Resources/SuperTux.app/Contents/Resources/data" — at Version 2

Reported by: kencu (Ken) Owned by: kencu (Ken)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: supertux

Description (last modified by kencu (Ken))

Darn.

I saw this once or twice during testing, but I thought I had scrubbed it out of the build in the end, and ran it many times locally here. But the builds are showing this again.

% /Applications/MacPorts/SuperTux.app/Contents/MacOS/supertux2
[FATAL] /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_games_supertux/supertux/work/SuperTux-v0.6.2-Source/src/supertux/main.cpp:610 Unexpected exception: boost::filesystem::canonical: No such file or directory: "/Applications/MacPorts/SuperTux.app/Contents/Resources/SuperTux.app/Contents/Resources/data"

I'll have to patch main.cpp I guess, or otherwise sort this out.

Apologies -- thought I had it.

Change History (2)

comment:1 Changed 4 years ago by kencu (Ken)

This launches it:

 % SUPERTUX2_DATA_DIR=/Applications/MacPorts/SuperTux.app/Contents/Resources/data /Applications/MacPorts/SuperTux.app/Contents/MacOS/supertux2

The upstream MacOS application bundle uses a launch script that sets something like this, but this appeared to be working for me, so I didn't think I'd need it.

Worst case scenario, I guess I can write a script for it like they do.

comment:2 Changed 4 years ago by kencu (Ken)

Description: modified (diff)
Note: See TracTickets for help on using tickets.