-
Notifications
You must be signed in to change notification settings - Fork 192
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
Unable to build flutter application for linux #390
Comments
Got the same error: https://ci.appveyor.com/project/flet-dev/flet/build/job/8ml3csb67k1mi5dr#L1994 |
0.13.2 introduced that issue. 0.13.1 gives successful build: https://ci.appveyor.com/project/flet-dev/flet/builds/49860784/job/ctoa28981dcvrgg5#L1926 0.13.2 adds |
Same error with 0.13.1 and latest 0.13.5 on Linux Mint.
|
This should be higher priority issue. Almost 2 months but no fix is applied for an unused variable warning causing build error. Please update it with a fix. |
Is there any update? It's still impossible to build the app for Linux with the latest Rive. |
As a data point I build Rive 0.4.11 (added CMake) for Yocto Linux using this repo: The install target also installs a package config file. This Yocto recipe supports both GCC 13 and Clang 18: |
Same issue, please fix this bug. |
Description
It seems it's not possible to build flutter application for linux
Steps To Reproduce
$ flutter build linux /home/roland/entwicklung/wger/flutter/linux/flutter/ephemeral/.plugin_symlinks/rive_common/macos/SheenBidi/Source/SBParagraph.c:618:16: error: unused variable 'stringLength' [-Werror,-Wunused-variable] Building Linux application... Build process failed
Source
.riv
/.rev
filen/a
Expected behavior
The build succeds. It seems that 0.13.0 is the version that introduced the bug, it's possible to build the application with 0.12.4 without any problems.
Screenshots
n/a
Device & Versions (please complete the following information)
Additional context
Also happens on github's CI: https://github.com/wger-project/flutter/actions/runs/9052280531/job/24869782253
The text was updated successfully, but these errors were encountered: