Conversation
|
is it only about |
|
No it's about application design and how to extend vab without building special case support into the app for every framework available out there. A compile time plugin system would be gold - but maybe runtime plugin support would be okay as well. vab also miss some essential features from the v_sdl4android project. |
|
... but yes, the failing CI check is because the files need to be formatted with |
| src_path := os.join_path(raylib_path, 'src') | ||
| ndk_path := ndk.root() | ||
| os.execute('make -C ${src_path} clean') | ||
| arch_name := if arch == 'arm64-v8a' { |
There was a problem hiding this comment.
would it be more eficient and nicer with mach{...} instead of if ... else if ... else?
There was a problem hiding this comment.
It would look cleaner with match. The else branch for the match would take care of the following if as well.
|
|
||
| // add the compiled raylib libraries for each arch | ||
| if is_raylib { | ||
| build_cmd << '-L ${lflags}' |
There was a problem hiding this comment.
maybe initialisation of 'lflags' for raylib would be nice put inside if
|
Just to refresh what is going on here: I'm keeping this PR open because I think Work has been done lately to simplify calling and using |
|
I was copy and done (with vlang/raylib#18) own version of this pr, can I give here or should I open other one? And I asume that is suitable all command put into vab, I will put prototypes and I asume you will tidy(give me point), it is ok? |
I would prefer raylib support is done like SDL is supported; via an extra command like The extra command should thus result in the user being able to build an application importing |
please can you help me?
vab is working with manual : |
I will take a look as soon as possible. I am a bit busy IRL at the moment 👍 |
ok, I will search for error, but I am probable at the end of my ability/skills and I do not want end without giving you report at least prototype ....... |
|
If the .so is not picked up it may be a directory structure problem or similar see the ( |
|
Ok. I've tried now to build the project. IMO both |
|
@MatejMagat305 I have opened MatejMagat305/vab-raylib#1 to fix it so |
|
I am building with: |
ok, your changes make: and it make full apk, with old https://github.com/MatejMagat305/raylib/pull/1/files or new vlang/raylib#19 |
|
and of course |
my android was install it, but some bug ......, please wait |
|
well, some ideas? |
|
I am sorry I was not provading full version what was working, here is old fashion............. https://github.com/MatejMagat305/vab-raylib-bin-prototype/tree/main, I probably know where is error, I will inform, thank for help |
|
well I do not know what I do wrong ...........
can I move ownership to Vlang after work will be done ? |
|
I'll look onto it ASAP. It can take a while as I am currently busy |
@MatejMagat305 this is because I am working on a solution that is not forked from larpon/vab-sdl that compiles raylib in parallel directly instead and does not depend on |
|
I am closing this. Use https://github.com/larpon/vab-raylib to build |

No description provided.