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

Compilation through a server vs --next #62

Open
Gama11 opened this issue Mar 31, 2020 · 0 comments
Open

Compilation through a server vs --next #62

Gama11 opened this issue Mar 31, 2020 · 0 comments
Labels

Comments

@Gama11
Copy link
Member

Gama11 commented Mar 31, 2020

To reproduce, first clone flash-debugger and start a compilation server:

> git clone https://github.com/vshaxe/flash-debugger
> cd flash-debugger
> npm install
> npx haxe --wait 7000

In a separate terminal also inside the cloned flash-debugger repo, try to compile through the server - it fails with a rather confusing error:

> npx haxe --connect 7000 build.hxml
Error: : unknown option '--haxe-version'.
Did you mean:
  --swf-version <version>  change the SWF version

Compilation through haxeshim works if there's no server involved:

> npx haxe build.hxml

The build.hxml consists of three builds separated by --next. If it's reduced to just one build (doesn't seem to matter which one), it seems to work through a server too. Most likely there are still some issues with --next support? I remember there were issues before, like #45.

This is with latest lix (15.8.9).

@Gama11 Gama11 added the bug label Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant