Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Aug 10 00:16
    pzmarzly edited #176
  • Aug 10 00:16
    pzmarzly edited #176
  • Aug 10 00:12
    pzmarzly opened #176
  • Aug 10 00:08
    pzmarzly commented #65
  • Aug 10 00:06
    pzmarzly commented #65
  • Aug 10 00:04
    pzmarzly commented #65
  • Jul 27 22:51
    player-03 commented #167
  • Jul 10 18:40
    back2dos closed #174
  • Jul 10 18:40
    back2dos commented #174
  • Jul 06 01:34
    TheDrawingCoder-Gamer closed #175
  • Jul 06 00:05
    TheDrawingCoder-Gamer commented #175
  • Jul 06 00:03
    kevinresol commented #175
  • Jul 05 23:53
    TheDrawingCoder-Gamer opened #175
  • Jul 05 23:20
    TheDrawingCoder-Gamer opened #174
  • Apr 03 06:33
    TC218 edited #173
  • Apr 03 06:31
    TC218 edited #173
  • Mar 14 19:04
    JordanPlayz158 commented #89
  • Mar 14 09:23
    back2dos commented #89
  • Mar 14 08:21

    kevinresol on master

    Cleanup (compare)

  • Mar 14 03:40
    kevinresol commented #89
Kevin Leung
@kevinresol
my understanding is that the json file basically resembles what haxe_libraries folder contains
grepsuzette
@grepsuzette
yes me too
Kevin Leung
@kevinresol
but then I don't have much opinion on it. I think it is just fine
grepsuzette
@grepsuzette
although it is technically equivalent I much prefer a haxe_libraries/ folder, .haxerc and keeping lix as a 3 character command. It works better for console work, also it's already there and people have choice not to use it
Peter Achberger
@Antriel
I agree, I prefer haxe_libraries too. Someone voiced the arguments for it, I think. More obvious diffs, easier copying of required libs to another project.
With npm the lock file is practically a crutch that they had to add later to fix the issue, there's really no good reason to have separate entries for libraries and for their versions.
grepsuzette
@grepsuzette
@Antriel in that case the HaxeFoundation/haxe#9135 could use your upvotes :)
Peter Achberger
@Antriel
Yeah, the discussion there is a bit mixed, I'm not sure what everyone is saying.
What you wrote about haxe doing it all... but it's not. The compiler is still just dumb compiler.
There's just a new frontend app to convert hxmls into compiler calls smartly, and haxelib is extended to understand scope.
grepsuzette
@grepsuzette
it's intertwined with haxelib right now, which makes emergence of tools difficult, complicating the job for lix and others. And once there is a frontend + haxec + haxelib it will be even more solidified
Peter Achberger
@Antriel
I don't see it being an issue. If you would want to, you could entirely replace haxe (the frontend) and haxelib, and use only haxec (the compiler).
grepsuzette
@grepsuzette
the last post will be debated I think, but the 2 arguments about haxe_libraries are the one where you should vote, just to signal it is important for somebody
Peter Achberger
@Antriel
So custom tools are possible.
Not sure why nicolas made it a wiki page instead of going through haxe-evolution.

And absolutely no idea what he meant by

This is WIP , please discuss there and don't edit directly ;)

It's not like we can discuss on a wiki page. :D Probably meant discuss here.

Kevin Leung
@kevinresol
I can see one downside for haxe_libraries. It contains copies of the actual compiler arguments. So it is not normalized.
Peter Achberger
@Antriel
Hmm. Good point, that shouldn't be there, rather only lib + version.
Kevin Leung
@kevinresol
that's why they proposed json
Peter Achberger
@Antriel
Which makes the need for individual files a bit weaker.
Hmm.
Well I don't really have strong feelings either way, just liked git diffs for haxe_libraries and really dislike how npm does it.
Gabriel Hayes
@piboistudios
Is there a way that get lix to work for private repos?
I'm getting an error asking me to Auth (I should already be via git)
Kevin Leung
@kevinresol
you can use the git: protocol if your ssh key is correctly set up
or use --gh-credentials and --gl-private-token through github:/gitlab: protocol
Gabriel Hayes
@piboistudios
Ah thanks
grepsuzette
@grepsuzette
but if you commit this by mistake to github then, big oops... I think better you clone it and then modify the hxml to point to your local path
i don't know exactly how it works with credentials, but the idea scares the shit out of me^^
Kevin Leung
@kevinresol
yes it will be saved in the hxml
so ssh+git is preferred
Gabriel Hayes
@piboistudios
How ironic ;) I was just asking my brother earlier why ever bother with SSH git
grepsuzette
@grepsuzette
ssh git is awesome, if it's your server I think it's the natural solution. But it's only for private projects of course
Kevin Leung
@kevinresol
same for gitlab/github private repos.
Kevin Leung
@kevinresol
when using the git: protocol, what is the syntax to select a branch?
trying lix install git:https://gitlab.com/org/repo#develop, apparently it can resolve the branch's head but somehow unable to switch to it
downloading git:https://gitlab.com/org/repo.git#57a30275b9362746a7aa161140e877e69c6445d6
From https://gitlab.com/org/repo
 * branch            HEAD       -> FETCH_HEAD
fatal: reference is not a tree: 57a30275b9362746a7aa161140e877e69c6445d6
Kevin Leung
@kevinresol
ok apparently lix downloaded the files via http zip, then try to git checkout that commit.
however the correct first step should be a git fetch instead
Juraj Kirchheim
@back2dos
oO
kro13
@kro13
hello. i've installed lime via lix, using
npm lix install haxelib:lime.
trying to run it with npx lix run lime
but get an error
Error: Could not find haxelib "lime", does it need to be installed? Failed to invoke `haxelib run-dir lime C:\Users\473387\AppData\Roaming/haxe/haxe_libraries/lime/7.8.0/haxelib` because Error: Command failed: haxelib run-dir lime C:\Users\473387\AppData\Roaming/haxe/haxe_libraries/lime/7.8.0/haxelib.
could anyone please explain what am i doing wrong?
npx haxelib install lime works, but i'd love to use the power of lix downloadlater, which obviously will not work
grepsuzette
@grepsuzette
@kro13 I don't know the syntax with npm or npx, or how to use lime.
FWIW personally I use lix directly, e.g. lix scope create, lix install haxelib:xxx, lix --help, lix run yyy.
Kevin Leung
@kevinresol
Which lix version?
Juraj Kirchheim
@back2dos
the following works (prints the lime ASCII-art): mkdir limetest && cd limetest && npm init -y && npm i lix && npx lix scope create && npx lix install haxelib:lime && npx lix lime
kro13
@kro13
thank you for your replies. @back2dos those commands do not work for me with the same error (. probably something with my setup then. @kevinresol lix version is 15.9.0, node version is 10.15.2, OS windows 10, if it matters.
Kevin Leung
@kevinresol
the versions look fine. so yeah probably a setup issue
kro13
@kro13
here is what i've managed to figure out. first of all my global haxe is 3.4.7 which comes with haxelib 3.3.0, which seems to be incapable of performing run-dir. when i use npx haxelib run-dir lime C:\Users\473387\AppData\Roaming\haxe\haxe_libraries\lime\7.8.0\haxelib directly from terminal it uses scoped haxelib 4.0.2 and works fine. however changing @run directive in haxe_libraries\lime.xml does not work and still fails with
Failed to invoke `npx haxelib run-dir lime C:\Users\473387\AppData\Roaming\haxe\haxe_libraries\lime\7.8.0\haxelib
it seems to be running out of scope or something like that. maybe anyone could bring some light here, knowing all above?
kro13
@kro13
updating global haxe is not a desireable option right now(
Juraj Kirchheim
@back2dos
hmm ... seems like the %PATH% set by npx is lost somewhere and then it falls back to your global installation
this may take a while ^^
haxelib run-dir is actually a lix feature anyway ^^