So for the moment will keep this one and the discord active.. we'll see which is better in the long run
Cool new feature: you can now use explicit generics without having to create a named specialization for structs: aardappel/lobster@bc58e7f
PSA: if you do anything with colors in Lobster I have potentially just broken your stuff with that last commit (the SRGB one). But it its for the best, really. Please read the commit message to learn how to deal with it :) aardappel/lobster@42aca24
Hello. I'm new here and I hope this is the right place to ask. I'm trying to compile lobster on Ubuntu Feisty. The compilation ends with an error: "/git/lobster/dev/external/SDL/src/audio/jack/SDL_jackaudio.h:24:10: fatal error: jack/jack.h: Datoteka ali imenik s tem imenom ne obstaja [file doesn't exist] 24 | #include <jack/jack.h>" What can I do to make things right?
Well, obviously it does... I tried to install "jack, " it doesn't work. A matter of fact, jack in Ubuntu is "libjack-jackd2" and I have a dev package installed. But now when I checked again, there is a libjack-dev package, which isn't installed. I'll install it (hopefully it doesn't mess my sound) and try compiling lobster again. I'll get back to you with the results.
Sorry, I'm not happy installing this. It replaces jacd2 with jackd1, something that is almost certain to bring down my sound system... Do you think that some kind of symbolic link could do the trick?
and I've never heard anyone mention this particular compile error before
I guess its somewhat new: https://discourse.libsdl.org/t/sdl-now-with-jack-support/22607/2
Thanks for the answer. What I really meant was code reloading a-la common lisp. Most game framework I have seen simply keep the application state in a global environment and then reload code at specific points, for example at each iteration of the game loop. CL is agnostic in this sense and a function definition can be reloaded at any time. This is done trough a level of indirection. Could this be achieved with Lobster or do you see any technical challenge?
@lucaregini well, I am not familiar what exactly common lisp does. It would generally be tricky to replace a single function, since Lobster nowadays goes thru a JIT that uses C underneath, but since it is so fast it should be possible to simply recompile the whole program
keeping the existing game state may also be tricky, since Lobster, unlike common lisp, is generally a very "static" language, meaning adding or removing fields, or changing types would make the previous VM state incompatible. Currently that can even be the case with adding variables, though that could be improved
Though Lobster is generally a friendly, high level language that is great for making games, it's also intended to be fast.. in some sense it will (at some point) not just be the language you write gameplay code in, but also most of what you'd consider the "engine" (minus the most performance sensitive graphics and physics functions)
So personally, if I wanted to make an engine where Lobster was used in a context with hot reloading, I'd simply add very fast serialization of the game state, and basically re-run the entire Lobster program upon code changes with that state. That would have the advantage that no code changes would be incompatible as long as the serializer can handle them. And it should still be fast, assuming the "engine" keeps textures and models etc in memory while this happens.
Sorry to ask a noob question. I just cloned lobster in MacOS and built. I get the following warning: "The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.7, but the range of supported deployment target versions is 10.9 to 11.1.99."
Xcode said build successful, but:
lobster$ ls bin
openvr_api.dll steam_api64.dll
and yeah the binary may end up in a different spot on osx
yes I get the same warning btw, you can ignore it for now
hmm for me the binary does end up in
bin
are you building the lobster > my mac target?
I think so. Don't know how to change the target to lobster_release.
Not an option
the prebuilt binary from the CI? what happens if you try to run it?
same for the
lobster scheme
With lobster > My Mac selected, did Product > Build For > Running. That worked, creating bin/lobster executable. As suggested, did 'bin/lobster samples/pythtree.lobster' and, wow! Good demo!
Thanks for help. Still can't find any 'lobster-release' but seem to be fine without it.
Thanks for help. Still can't find any 'lobster-release' but seem to be fine without it.
the problem with the "lobster" scheme is that it builds for debug which may be slow, you may want to go Edit Scheme -> Run -> Build configuration and change to Release
it seems schemes are a per user thing: https://stackoverflow.com/questions/5304031/where-does-xcode-4-store-scheme-data#:~:text=Schemes%20are%20stored%20per%20user,seen%20and%20used%20by%20everyone.
so yeah, you kind of have to build it for release yourself