You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we're cross-compiling Clixon and currently, when there's a syntax error in one of the .cli files, it's not until we start the CLI on target that you get a warning:
root@infix:~# cli
/usr/lib/clixon/clispec/core-cli.cli:36: Error: syntax error: at or before: ')'
Mar 13 14:19:33: cli_load_syntax_file: 303: Plugins: failed to parse cli file /usr/lib/clixon/clispec/core-cli.cli
Is there a way to run a host-built clixon_cli in a bare-bones way1 that it can act as a .cli file linter? Maybe I'm alone in this struggle, but if not, maybe a stripped down clixon_cli could be called clint 😃
Footnotes
The obvious way is of course to develop the .cli file natively first, but maybe other ppl have had the same idea for a linter? ↩
The text was updated successfully, but these errors were encountered:
Hi, we're cross-compiling Clixon and currently, when there's a syntax error in one of the .cli files, it's not until we start the CLI on target that you get a warning:
Is there a way to run a host-built
clixon_cli
in a bare-bones way1 that it can act as a .cli file linter? Maybe I'm alone in this struggle, but if not, maybe a stripped downclixon_cli
could be calledclint
😃Footnotes
The obvious way is of course to develop the .cli file natively first, but maybe other ppl have had the same idea for a linter? ↩
The text was updated successfully, but these errors were encountered: