Add custom starter to App scope
-
@gmelchett Well, you don't have to use the version from git. I suspect it was removed there in favor of using Wayland, with newer versions of Mir, as is also done for other toolkits. That will be the way forward in the future, but for now, direct client support is needed on the phone/tablet builds.
-
any update about love games on UT?
-
Not really. Since Love2d depends on SDL2 we'd first figure out how to compile SDL with clickable:
- All dependencies included
- With SDL2 version <= 2.0.7
-
@wendigo thanks
but why do we need to compile love2d? can't we use an existing armhf love build?
let me know if there are any progress (and maybe how can I help in this), as I'm interested in a love game on UT...btw, are you also ion telegram, where we can chat easily?
-
@mymike said in Add custom starter to App scope:
@wendigo thanks
but why do we need to compile love2d? can't we use an existing armhf love build?
let me know if there are any progress (and maybe how can I help in this), as I'm interested in a love game on UT...btw, are you also ion telegram, where we can chat easily?
IIRC the armhf build for Raspberry Pi was built for X11 with Mir/Wayland explicitly excluded via compiler flags, but I'm not quite sure. All I remember is that it didn't work.
You can find me on Telegram and Matrix (FluffyChat) under the name: [ a t ]mickey83
Though I'm more active on Matrix. -
I had a second look, guess I was wrong. The Mir/Wayland backend was excluded from the RasPi version of SDL2. Love2d was offered for armhf in deb format, which I don't know how to install via clickable. (if that is possible at all)
-
what about installing SDL2 and Love2d in the system image? so that every app/game that needs them doesn't need to have them inside the click package. I know we are almost out of space, but they're quite small and useful...
this way we can install them as deb. I'll have a shot to see if installed as deb they work... -
@mymike We can't, and really shouldn't, ship every possible library that one might want to use in an app, or that is required by a game, which someone wants to package for UT. And if we ship the main SDL library, then how many others should we ship? We can't ship them all, and many different ones are used by different developers.
It's not hard to have an SDL that supports Mir built into a click package.
-
@mymike We can't, and really shouldn't, ship every possible library
ok, I understand
It's not hard to have an SDL that supports Mir built into a click package.
just try to build SDL with clickable?
-
@mymike said in Add custom starter to App scope:
just try to build SDL with clickable?
Yes, with the
librariesconfig, or you might be able to just pull the library out of the deb package if it doesn't have any hard-coded paths built into it, and is linked to the correct version of Mir. -
@Wendigo said in Add custom starter to App scope:
Not really. Since Love2d depends on SDL2 we'd first figure out how to compile SDL with clickable:
- All dependencies included
- With SDL2 version <= 2.0.7
https://forums.ubports.com/topic/2178/c-and-sdl-with-clickable-a-little-help-please/16 SDL2 works on UT, now how can I package love2d in a click?
-
@mymike said in Add custom starter to App scope:
@Wendigo said in Add custom starter to App scope:
Not really. Since Love2d depends on SDL2 we'd first figure out how to compile SDL with clickable:
- All dependencies included
- With SDL2 version <= 2.0.7
https://forums.ubports.com/topic/2178/c-and-sdl-with-clickable-a-little-help-please/16 SDL2 works on UT, now how can I package love2d in a click?
Do basically the same thing to build love2d with SDL2 support, and include the necessary files in your click by installing them to the correct place during the
clickable buildso thatbuild-clickwill include them. -
@dobey eh, the thing is that for SDL2 I just copied someone else's template, do idk how it works...
