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.

Sign up for GitHub

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

Corrected haxe paths for OS X 10.11+ #2

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Corrected haxe paths for OS X 10.11+ #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7ef30d8
Corrected haxe paths for OS X 10.11+
anissen Sep 9, 2016
33cc5e2
Update paths for OS X 10.11+
anissen Sep 9, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,9 @@ For `version`, you can use any git reference - a branch, a tag, a commit hash, e

### Known bugs

When you use `haxelib run hvm` some installations actually use Haxe to compile/run haxelib, then haxelib runs and calls `haxe/lib/hvm/0.0.2/run.n`. This is all well and good, until `hvm` tries to replace the Haxe binary, and the OS complains. A workaround is to use something along the lines of:
When you use `haxelib run hvm` some installations actually use Haxe to compile/run haxelib, then haxelib runs and calls `/usr/local/lib/haxelib/hvm/0,0,2/run.n`. This is all well and good, until `hvm` tries to replace the Haxe binary, and the OS complains. A workaround is to use something along the lines of:

sudo neko /usr/lib/haxe/lib/hvm/0,0,2/hvm.n --use development
sudo neko /usr/local/lib/haxelib/hvm/0,0,2/hvm.n --use development

### Implementation Details

Expand All @@ -51,7 +51,7 @@ When you use `haxelib run hvm` some installations actually use Haxe to compile/r
* When `--set` is used, the compiled version and the standard library are copied to your system path. You may need to use `sudo` for this to work.
* On Linux & Mac:
* You will need the build dependencies installed already. See <http://haxe.org/documentation/introduction/building-haxe.html>
* This assumes you have your Haxe binary at `/usr/lib/haxe/haxe` and the standard library at `/usr/lib/haxe/std/`. It would be nice to make this configurable.
* This assumes you have your Haxe binary at `/usr/local/lib/haxe/haxe` and the standard library at `/usr/local/lib/haxe/std/`. It would be nice to make this configurable.
* This will place your repo in `~/.hvm/`, where `~` is your home directory, found using the `HOME` environment variable.
* On Windows:
* We are lacking an implementation, but it should be dead easy. See <https://github.com/jasononeil/hvm/blob/master/src/hvm/platform/WinConfig.hx>. Pull requests welcome.
* We are lacking an implementation, but it should be dead easy. See <https://github.com/jasononeil/hvm/blob/master/src/hvm/platform/WinConfig.hx>. Pull requests welcome.
4 changes: 2 additions & 2 deletions src/hvm/platform/UnixConfig.hx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,8 @@ class UnixConfig implements PlatformConfig {
hvmRepo = Sys.getEnv( 'HOME' ).addTrailingSlash() + '.hvm/';

// TODO: a better way to get these, check env variables or `path haxe` etc.
haxeBinary = '/usr/lib/haxe/haxe';
stdLib = '/usr/lib/haxe/std/';
haxeBinary = '/usr/local/lib/haxe/haxe';
stdLib = '/usr/local/lib/haxe/std/';
}

public function build() {
Expand Down