Skip to content
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 on Ubuntu (WSL fails) #89

Open
zuluonezero opened this issue May 17, 2024 · 3 comments
Open

Build on Ubuntu (WSL fails) #89

zuluonezero opened this issue May 17, 2024 · 3 comments

Comments

@zuluonezero
Copy link

=:) sudo jpm build
compiling raylib/src/rshapes.c to build/raylib___src___rshapes.o...
compiling src/main.c to build/src___main.o...
compiling raylib/src/rcore.c to build/raylib___src___rcore.o...
compiling raylib/src/rmodels.c to build/raylib___src___rmodels.o...
compiling raylib/src/raudio.c to build/raylib___src___raudio.o...
compiling raylib/src/rglfw.c to build/raylib___src___rglfw.o...
compiling raylib/src/rtext.c to build/raylib___src___rtext.o...
compiling raylib/src/rtextures.c to build/raylib___src___rtextures.o...
compiling raylib/src/utils.c to build/raylib___src___utils.o...
generating meta file build/jaylib.meta.janet...
raylib/src/rtextures.c:152: warning: "STB_IMAGE_IMPLEMENTATION" redefined
152 | #define STB_IMAGE_IMPLEMENTATION
|
: note: this is the location of the previous definition
In file included from src/main.c:5:
src/types.h:483:20: error: expected expression before ‘,’ token
483 | JANET_ATEND_GET,

Resolved by removing the trailing comma on line 483 in src/types.h

@sogaiu
Copy link

sogaiu commented May 17, 2024

That does look like a problem.

I reproduced the issue. Removing the trailing comma as suggested did result in a successful build.

May be it would be better to report this to the jaylib repository though.

@sogaiu
Copy link

sogaiu commented May 18, 2024

@zuluonezero

I've gone ahead an created an issue at the jaylib repository.

Thanks for reporting.

@sogaiu
Copy link

sogaiu commented May 18, 2024

I believe the issue has been addressed in this commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants