Trying to npx lix install haxe XXX in a Github action (with Node)
why 3.5.7? :D
Is that a typo or an internal build?
No it's a typo...
let me try again with 3.4.7 :D
Not a very helpful error message when you ask for a non-existent version :D
yeah, it's weird indeed
pretty sure it was better at some point ^^
If you work on a library libxyz, and its unit tests have a dependency, e.g. tink_unittest, you will have a libxyz/haxe_libraries/tink_unittest.hxml. Does that file implies a user of libxyz will also depend upon tink_unittest, or not?
during a haxelib install haxelib.json is authoritative ... during a git(hub|lab) install, the haxe_libraries are, but if there's a haxelib.json only the dependencies resulting from that are taken
I don't mind ... but that actually creates a new distribution problem ^^
Could it run in eval? Then the only issue is Haxe version support. :D
On top of, you know, having to install Haxe before installing Lix. :(
it'll have to be uploaded to brew, which AFAIK is a bit of a PITA, and then to choco and whatever Microsoft's package manager thingy is called and of course to all sorts of linux package managers
Eval is kinda slow, too. It has to handle compilation at runtime
Which can be noticeable with tink goodies
(also, "lix" is already taken in some(many?) linux package managers °°)
can we "just" host the binary somewhere and instruct people to set up their $PATH manually
I suppose ... I guess with github actions one could compile something for windows, linux and mac and add it as an artifact to the release or something
ya iiuc the pkg library can compile the three platforms already
ooooh, nice :)
Seems like haxeshim is required to build hxcpp with lix. Which is also weird because you have to uninstall some of the files from one of the installs of either lix or shim to install both (because they both try to install the Haxe/haxelib/neko cmds etc)
if some particular thing doesn't work with lix, please open an issue, with as many details as possible on how to repro ;)
@back2dos I know. But Lix (latest) failed to compile hxcpp without haxeshim installed as well (it could compile other targets but for hxcpp it was complaining about haxeshim module). I had tried manually deleting the files out of my global npm and installing Lix fresh but it didn't resolve the issue
Ultimately what I had to do was:
Completely uninstall lix (and by this I mean I ran npm uninstall and also deleted the cmds/sh/scripts for Haxe out of npm folder), install haxeshim, delete the cmds/sh/scripts again (Lix tries to install these as well, because as you said it includes haxeshim), then install lix, and it built
Oh I just now saw your second message. I'll open an issue
the CI via travisci.org is gone and when I try to add the repo on travisci.com, it's not there \o/
Thanks :D It works for me now!
Hey guys, I have a question about --haxelib-url. In our project, we are getting most of the dependencies from a private haxelib repo. They were installed using lix install --haxelib-url ... But some libs are installed from github. When running lix download, the subdeps of those libs are downloaded from the public haxelib repo, which is undesirable in our case. Is there some way to tell lix to use the private haxelib url in this case? Perhaps this option can apply to lix download?