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 "boot" #8155

Open
ncannasse opened this issue Apr 11, 2019 · 3 comments · May be fixed by #11755
Open

Haxelib "boot" #8155

ncannasse opened this issue Apr 11, 2019 · 3 comments · May be fixed by #11755
Milestone

Comments

@ncannasse
Copy link
Member

I propose the following for replacing haxelib.exe:

In OCaml:

  • rewrite the method responsible for resolving haxelib repository (which is quite easy)
  • locate the current haxelib package installed using this method
  • if not present, install it from statically linked data
  • run it using haxe eval

This way:

  • no neko dependency required (only for running run.n if necessary)
  • haxelib can be distributed/updated as a library

Show stopper:

  • eval ssl support ?
@Simn
Copy link
Member

Simn commented Apr 12, 2019

I wanted the compiler to have less knowledge about haxelibs and such, not more...

@ncannasse
Copy link
Member Author

It's not a compiler, it's a new exe. Any other proposal for boostrapping ?
Alternative solution is to have this written in Haxe (using haxelib sources) and compiled with hxcpp as exe. But since hxcpp requires haxelib...

@back2dos
Copy link
Member

I'm not sure what this is actually solving, but concerning concrete issues brought up:

But since hxcpp requires haxelib...

Possible solution: Add hxcpp as git submodule to haxelib. Compile with -D no-compilation and call into the build tool in Context.onAfterGenerate (involves making sure it runs on eval, but with the new unified threading API, it might actually work quite well).

@Simn Simn added this to the Design milestone May 22, 2019
@tobil4sk tobil4sk linked a pull request Sep 4, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

3 participants