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

haxelib path order is different than what tools processing it might expect #132

Closed
Gama11 opened this issue Mar 27, 2020 · 5 comments
Closed

Comments

@Gama11
Copy link
Member

Gama11 commented Mar 27, 2020

haxelib and npx haxelib should have the same output:

>haxelib path dox
C:\Users\Jens\Haxelibs\dox\src\
-D dox=1.3.0

>npx haxelib path dox
-D dox=1.3.0
C:/Users/Jens/Haxelibs/dox/src/

Also notice the extra newline at the end of the output from regular Haxelib.

This wouldn't be as much of an issue if it wasn't for lix-pm/haxeshim#60.

@Gama11
Copy link
Member Author

Gama11 commented Mar 27, 2020

Note: the lix dox was installed via npx lix dev.

@back2dos
Copy link
Contributor

You can either swap the lines in the haxe_libraries/dox.hxml or reinstall dox with a recent enough lix (see #103 (comment))

@Gama11
Copy link
Member Author

Gama11 commented Mar 29, 2020

Err... the project wasn't even using lix yet at the time this was supposedly fixed. :) Still looks the same after a reinstall. This is with lix 15.8.9.

@back2dos
Copy link
Contributor

Is the library installed via lix or via haxelib?

@Gama11
Copy link
Member Author

Gama11 commented Mar 29, 2020

@back2dos back2dos transferred this issue from lix-pm/haxeshim Apr 25, 2020
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