-
Notifications
You must be signed in to change notification settings - Fork 12
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
Build broken using Love12 AppImages #40
Comments
liblove.so
rename
Sorry for the long delay. I have been on vacation, then quit my job and lots of stuff has been happening. so_target_dir = find_liblove([
appdir("lib/"), # pfirsich-style AppImages
appdir("usr/lib"), # Official AppImages (since 11.4)
])
if so_target_dir == None:
sys.exit("Could not find liblove.so in AppDir. The AppImage has an unknown format.") and do def find_liblove(search_dirs: list[str]):
is_liblove = lambda fname: fname.startswith("liblove") and fname.endswith(".so")
for search_dir in search_dirs:
if any(is_liblove(f) for f in os.listdir(search_dir)):
return search_dir
return None This is not tested or anything. And you can do it a different way too, if you want. |
Hello, how did you manage to put own custom version of LÖVE? I'm also using LÖVE 12 from the Github Actions page and trying to build with makelove gives me this error: |
Hi- I have been using love with a custom AppImage, (specifically, the latest love-12 AppImage generated from github actions).
The new Love-12 appImages contain
liblove-12.so
as opposed toliblove.so
, which is breaking makelove.I'm not sure why this was renamed, I've asked on the love discord.I had a discussion with Sasha, turns out
liblove
has always been named this way. I think it's just because I got the extracted appimage from the github CI, why there were issues.What do you think about this? Would it be worth making the
liblove
detection a bit more generic to detect different versions....?I also suspect that this was the cause of #38
(For reference, here is a tree of the new extracted appimage for love 12)
The text was updated successfully, but these errors were encountered: