First commit
This commit is contained in:
5
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/api.md
generated
vendored
Normal file
5
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/api.md
generated
vendored
Normal file
@@ -0,0 +1,5 @@
|
||||
# Accessing Haxelib info through the Remoting API
|
||||
# Accessing Haxelib info through the JSON API
|
||||
|
||||
|
||||
More information to go here...
|
||||
91
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/creating-a-haxelib-package.md
generated
vendored
Normal file
91
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/creating-a-haxelib-package.md
generated
vendored
Normal file
@@ -0,0 +1,91 @@
|
||||
# Creating a haxelib package
|
||||
|
||||
Each haxelib package is essentially a zip folder containing source code, supporting files, and a `haxelib.json` file.
|
||||
|
||||
### haxelib.json
|
||||
|
||||
Each Haxe library requires a `haxelib.json` file in which the following attributes are defined:
|
||||
|
||||
* name: The name of the library. It must contain at least 3 characters among the following: `[A-Za-z0-9_-.]`. In particular, no spaces are allowed.
|
||||
* url: The URL of the library, i.e. where more information can be found.
|
||||
* license: The license under which the library is released. Can be `GPL`, `LGPL`, `BSD`, `Public` (for Public Domain) or `MIT`.
|
||||
* tags: An array of tag-strings which are used on the repository website to sort libraries.
|
||||
* description: The description of what the library is doing.
|
||||
* version: The version string of the library. This is detailed in [Versioning](#versioning).
|
||||
* classPath: The path string to the source files.
|
||||
* releasenote: The release notes of the current version.
|
||||
* contributors: An array of user names which identify contributors to the library.
|
||||
* dependencies: An object describing the dependencies of the library. This is detailed in [Dependencies](haxelib-json-dependencies.md).
|
||||
|
||||
The following JSON is a simple example of a haxelib.json:
|
||||
|
||||
```haxe
|
||||
{
|
||||
"name": "useless_lib",
|
||||
"url" : "https://github.com/jasononeil/useless/",
|
||||
"license": "MIT",
|
||||
"tags": ["cross", "useless"],
|
||||
"description": "This library is useless in the same way on every platform.",
|
||||
"version": "1.0.0",
|
||||
"classPath": "src/",
|
||||
"releasenote": "Initial release, everything is working correctly.",
|
||||
"contributors": ["Juraj","Jason","Nicolas"],
|
||||
"dependencies": {
|
||||
"tink_macro": "",
|
||||
"nme": "3.5.5"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
<a name="versioning"></a>
|
||||
|
||||
### Versioning
|
||||
|
||||
Haxelib uses a simplified version of [SemVer](http://semver.org/). The basic format is this:
|
||||
|
||||
```
|
||||
major.minor.patch
|
||||
```
|
||||
|
||||
These are the basic rules:
|
||||
|
||||
* Major versions are incremented when you break backwards compatibility - so old code will not work with the new version of the library.
|
||||
* Minor versions are incremented when new features are added.
|
||||
* Patch versions are for small fixes that do not change the public API, so no existing code should break.
|
||||
* When a minor version increments, the patch number is reset to 0. When a major version increments, both the minor and patch are reset to 0.
|
||||
|
||||
Examples:
|
||||
|
||||
* "0.0.1": A first release. Anything with a "0" for the major version is subject to change in the next release - no promises about API stability!
|
||||
* "0.1.0": Added a new feature! Increment the minor version, reset the patch version
|
||||
* "0.1.1": Realised the new feature was broken. Fixed it now, so increment the patch version
|
||||
* "1.0.0": New major version, so increment the major version, reset the minor and patch versions. You promise your users not to break this API until you bump to 2.0.0
|
||||
* "1.0.1": A minor fix
|
||||
* "1.1.0": A new feature
|
||||
* "1.2.0": Another new feature
|
||||
* "2.0.0": A new version, which might break compatibility with 1.0. Users are to upgrade cautiously.
|
||||
|
||||
If this release is a preview (Alpha, Beta or Release Candidate), you can also include that, with an optional release number:
|
||||
|
||||
```
|
||||
major.minor.patch-(alpha/beta/rc).release
|
||||
```
|
||||
|
||||
Examples:
|
||||
|
||||
* "1.0.0-alpha": The alpha of 1.0.0 - use with care, things are changing!
|
||||
* "1.0.0-alpha.2": The 2nd alpha
|
||||
* "1.0.0-beta": Beta - things are settling down, but still subject to change.
|
||||
* "1.0.0-rc.1": The 1st release candidate for 1.0.0 - you shouldn't be adding any more features now
|
||||
* "1.0.0-rc.2": The 2nd release candidate for 1.0.0
|
||||
* "1.0.0": The final release!
|
||||
|
||||
### extraParams.hxml
|
||||
|
||||
If you add a file named `extraParams.hxml` to your library root (at the same level as `haxelib.json`), these parameters will be automatically added to the compilation parameters when someone use your library with `-lib`.
|
||||
|
||||
### Submission process
|
||||
|
||||
* During development: Use `haxelib dev my_test_haxelib /path/to/my_test_haxelib/` to test the library.
|
||||
* Ready to test: Zip the current directory, and use `haxelib install my_test_haxelib.zip` to try the final version.
|
||||
- Submit: You can run `haxelib submit my_test_haxelib.zip` to submit the zip file to haxelib. Alternatively you can run `haxelib submit` without a zip file to have haxelib zip and submit the current directory.
|
||||
3
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/faq.md
generated
vendored
Normal file
3
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/faq.md
generated
vendored
Normal file
@@ -0,0 +1,3 @@
|
||||
# FAQ
|
||||
|
||||
More information to go here...
|
||||
24
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/index.md
generated
vendored
Normal file
24
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/index.md
generated
vendored
Normal file
@@ -0,0 +1,24 @@
|
||||
# Getting Started With Haxelib
|
||||
|
||||
Haxelib is the library manager that comes with any Haxe distribution. Connected to a central repository, it allows submitting and retrieving libraries and has multiple features beyond that. Available libraries can be found at <http://lib.haxe.org>.
|
||||
|
||||
A basic Haxe library is a collection of `.hx` files. That is, libraries are distributed by source code by default, making it easy to inspect and modify their behavior. Each library is identified by a unique name, which is utilized when telling the Haxe Compiler which libraries to use for a given compilation.
|
||||
|
||||
### Using with Haxe
|
||||
|
||||
Any installed Haxe library can be made available to the compiler through the `-lib <library-name>` argument. This is very similiar to the `-cp <path>` argument, but expects a library name instead of a directory path. These commands are explained thoroughly in [Compiler Usage](http://haxe.org/manual/compiler-usage.html).
|
||||
|
||||
For our exemplary usage we chose a very simple Haxe library called "random". It provides a set of static convenience methods to achieve various random effects, such as picking a random element from an array.
|
||||
|
||||
```haxe
|
||||
class Main {
|
||||
static public function main() {
|
||||
var elt = Random.fromArray([1, 2, 3]);
|
||||
trace(elt);
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
Compiling this without any `-lib` argument causes an error message along the lines of `Unknown identifier : Random`. This shows that installed Haxe libraries are not available to the compiler by default unless they are explicitly added. A working command line for above program is `haxe -lib random -main Main --interp`.
|
||||
|
||||
If the compiler emits an error `Error: Library random is not installed : run 'haxelib install random'` the library has to be installed via the `haxelib` command first. As the error message suggests, this is achieved through `haxelib install random`. We will learn more about the `haxelib` command in [Using Haxelib](/documentation/using-haxelib/).
|
||||
4
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/installation.md
generated
vendored
Normal file
4
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/installation.md
generated
vendored
Normal file
@@ -0,0 +1,4 @@
|
||||
# Installing and Upgrading Haxelib
|
||||
|
||||
|
||||
More information to go here...
|
||||
45
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/per-project-setup.md
generated
vendored
Normal file
45
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/per-project-setup.md
generated
vendored
Normal file
@@ -0,0 +1,45 @@
|
||||
TODO: this needs editing and adding to the website
|
||||
|
||||
|
||||
|
||||
## Per-project setup
|
||||
|
||||
Currently haxelib has two ways to have project local setups.
|
||||
|
||||
1. Using `haxelib newrepo`
|
||||
2. Using `haxelib install all`
|
||||
|
||||
### Using haxelib newrepo
|
||||
|
||||
When using `haxelib newrepo` you can have a project-local haxelib repository. This feature is quite new and a little rough around the edges.
|
||||
|
||||
Caveats:
|
||||
|
||||
- libraries get downloaded for each project
|
||||
- if you mistakenly run a haxelib command in a subdirectory of your project, it will be executed on the global repo ([to be fixed](https://github.com/HaxeFoundation/haxelib/issues/292))
|
||||
|
||||
### Using haxelib install all
|
||||
|
||||
Haxe allows you to define specific versions of the libraries you want to use with `-lib <libname>:<version>`. If you make sure to use this in all your hxmls, then `haxelib install all --always` (the `--always` avoiding you being prompted for confirmation) will be able to ensure the libraries your project needs are available in the necessary versions. If in fact you run this in a checkout hook, your get to track your dependencies in your git repo (some other VCSs should allow for a similar setup), allowing you to have a well defined and replicable setup for any state (commit/branch/etc.).
|
||||
|
||||
Disadvantages:
|
||||
|
||||
- the approach requires you to define all dependencies with specific versions and then running `haxelib install all` to grab them
|
||||
- with this approach, any other project that does not have specific versions defined may be affected, as under some circumstances `haxelib install all` may set the global "current" version of the libraries (to be fixed)
|
||||
|
||||
Advantages:
|
||||
|
||||
- as pointed out above, this approach allows defining a *versionable* and *replicable* state.
|
||||
- you don't have to download libraries for each project, which does make a difference for heavy weights like openfl and hxcpp
|
||||
|
||||
#### Sidestepping haxelib git issues
|
||||
|
||||
Because you cannot specify git versions with `-lib` paremeters, we suggest using git submodules instead, as again they provide an adequate way of definining a *versionable* and *replicable* state.
|
||||
|
||||
### Combining both approaches
|
||||
|
||||
You can of course combine both approaches, giving you the isolation provided by the first one, and the replicability provided by the second one.
|
||||
|
||||
### Future solutions
|
||||
|
||||
A solution that combines the strengths of both approaches is in the making. Stay tuned.
|
||||
3
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/tips-and-tricks.md
generated
vendored
Normal file
3
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/tips-and-tricks.md
generated
vendored
Normal file
@@ -0,0 +1,3 @@
|
||||
# Tips and Tricks when using Haxelib
|
||||
|
||||
More information to go here...
|
||||
618
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/using-haxelib.md
generated
vendored
Normal file
618
hGameTest/node_modules/haxe/downloads/haxelib/www/documentation-files/using-haxelib.md
generated
vendored
Normal file
@@ -0,0 +1,618 @@
|
||||
# Using Haxelib
|
||||
|
||||
If the `haxelib` command is executed without any arguments, it prints an exhaustive list of all available arguments. Access the <http://lib.haxe.org> website to view all the libraries available.
|
||||
|
||||
The following commands are available:
|
||||
|
||||
<div class="row">
|
||||
<div class="col-md-4">
|
||||
<h4><a href="#basic">Basic</a></h4>
|
||||
<ul>
|
||||
<li><a href="#install">install</a></li>
|
||||
<li><a href="#update">update</a></li>
|
||||
<li><a href="#remove">remove</a></li>
|
||||
<li><a href="#list">list</a></li>
|
||||
<li><a href="#set">set</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
<div class="col-md-4">
|
||||
<h4><a href="#information">Information</a></h4>
|
||||
<ul>
|
||||
<li><a href="#search">search</a></li>
|
||||
<li><a href="#info">info</a></li>
|
||||
<li><a href="#user">user</a></li>
|
||||
<li><a href="#config">config</a></li>
|
||||
<li><a href="#path">path</a></li>
|
||||
<li><a href="#version">version</a></li>
|
||||
<li><a href="#help">help</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
<div class="col-md-4">
|
||||
<h4><a href="#development">Development</a></h4>
|
||||
<ul>
|
||||
<li><a href="#submit">submit</a></li>
|
||||
<li><a href="#register">register</a></li>
|
||||
<li><a href="#dev">dev</a></li>
|
||||
<li><a href="#git">git</a></li>
|
||||
<li><a href="#hg">hg</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="row">
|
||||
<div class="col-md-4">
|
||||
<h4><a href="#miscellaneous">Miscellaneous</a></h4>
|
||||
<ul>
|
||||
<li><a href="#setup">setup</a></li>
|
||||
<li><a href="#newrepo">newrepo</a></li>
|
||||
<li><a href="#deleterepo">deleterepo</a></li>
|
||||
<li><a href="#convertxml">convertxml</a></li>
|
||||
<li><a href="#run">run</a></li>
|
||||
<li><a href="#proxy">proxy</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
<div class="col-md-4">
|
||||
<h4><a href="#flags">Flags</a></h4>
|
||||
<ul>
|
||||
<li><a href="#flat">--flat</a></li>
|
||||
<li><a href="#always">--always</a></li>
|
||||
<li><a href="#system">--system</a></li>
|
||||
<li><a href="#debug">--debug</a></li>
|
||||
<li><a href="#quiet">--quiet</a></li>
|
||||
<li><a href="#never">--never</a></li>
|
||||
<li><a href="#global">--global</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
<div class="col-md-4">
|
||||
<h4><a href="#parameters">Parameters</a></h4>
|
||||
<ul>
|
||||
<li><a href="#cwd">-cwd</a></li>
|
||||
<li><a href="#notimeout">-no-timeout</a></li>
|
||||
<li><a href="#R">-R</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<a name="basic" class="anch"></a>
|
||||
|
||||
## Basic
|
||||
|
||||
|
||||
|
||||
<a name="install" class="anch"></a>
|
||||
|
||||
#### `haxelib install`
|
||||
|
||||
|
||||
```
|
||||
haxelib install [project-name] [version]
|
||||
haxelib install actuate # Install latest version
|
||||
haxelib install actuate 1.8.2 # Install specific version
|
||||
```
|
||||
|
||||
> Install the given project. You can optionally specify a specific version to be installed. By default, latest released version will be installed.
|
||||
|
||||
```
|
||||
haxelib install [library-file]
|
||||
haxelib install actuate.zip # Install from zip file
|
||||
```
|
||||
|
||||
> Install the project contained in the zip file.
|
||||
|
||||
```
|
||||
haxelib install [hxml-file]
|
||||
haxelib install build.hxml # Install all dependencies listed in hxml file
|
||||
```
|
||||
|
||||
> Install all the dependencies from a hxml file.
|
||||
|
||||
```
|
||||
haxelib install all # Install all dependencies in all hxml files
|
||||
```
|
||||
|
||||
> Install all the dependencies from all hxml files in the current directory.
|
||||
|
||||
|
||||
|
||||
<a name="update" class="anch"></a>
|
||||
|
||||
#### `haxelib update`
|
||||
|
||||
```
|
||||
haxelib update [project-name]
|
||||
haxelib update minject
|
||||
```
|
||||
|
||||
> Update a single library to the latest version.
|
||||
|
||||
```
|
||||
haxelib update
|
||||
```
|
||||
|
||||
> Update all the installed projects to their latest version. This command prompts a confirmation for each updating project.
|
||||
|
||||
|
||||
|
||||
<a name="remove" class="anch"></a>
|
||||
|
||||
#### `haxelib remove`
|
||||
|
||||
```
|
||||
haxelib remove [project-name] [version]
|
||||
haxelib remove format # Remove all versions
|
||||
haxelib remove format 3.1.2 # Remove the specified version
|
||||
```
|
||||
|
||||
> Remove a complete project or only a specified version if specified.
|
||||
|
||||
|
||||
|
||||
<a name="list" class="anch"></a>
|
||||
|
||||
#### `haxelib list`
|
||||
|
||||
```
|
||||
haxelib list [search]
|
||||
haxelib list # List all installed projects
|
||||
haxelib list ufront # List all projects with "ufront" in their name
|
||||
```
|
||||
|
||||
> List all the installed projects and their versions. For each project, the version surrounded by brackets is the current one.
|
||||
|
||||
|
||||
|
||||
<a name="set" class="anch"></a>
|
||||
|
||||
#### `haxelib set`
|
||||
|
||||
```
|
||||
haxelib set [project-name] [version]
|
||||
haxelib set tink_core 1.0.0-rc.8
|
||||
```
|
||||
|
||||
> Change the current version for a given project. The version must be already installed.
|
||||
|
||||
|
||||
|
||||
<a name="information" class="anch"></a>
|
||||
|
||||
## Information
|
||||
|
||||
|
||||
|
||||
<a name="search" class="anch"></a>
|
||||
|
||||
#### `haxelib search`
|
||||
|
||||
```
|
||||
haxelib search [word]
|
||||
haxelib search tween
|
||||
```
|
||||
|
||||
> Get a list of all haxelib projects with the specified word in the name or description.
|
||||
|
||||
|
||||
|
||||
<a name="info" class="anch"></a>
|
||||
|
||||
#### `haxelib info`
|
||||
|
||||
```
|
||||
haxelib info [project-name]
|
||||
haxelib info openfl
|
||||
```
|
||||
|
||||
> Show information about this project, including the owner, license, description, website, tags, current version, and release notes for all versions.
|
||||
|
||||
|
||||
|
||||
<a name="user" class="anch"></a>
|
||||
|
||||
#### `haxelib user`
|
||||
|
||||
```
|
||||
haxelib user [user-name]
|
||||
haxelib user jason
|
||||
```
|
||||
|
||||
> Show information on a given Haxelib user and their projects.
|
||||
|
||||
|
||||
|
||||
<a name="config" class="anch"></a>
|
||||
|
||||
#### `haxelib config`
|
||||
|
||||
```
|
||||
haxelib config
|
||||
```
|
||||
|
||||
> Print the Haxelib repository path. This is where each library will be installed to. You can modify the path using <code>haxelib [setup](#setup)</code>.
|
||||
>
|
||||
> If you are in a local repository and want to print the global Haxelib repository path do <code>haxelib [--global](#global) config</code>.
|
||||
|
||||
|
||||
|
||||
<a name="path" class="anch"></a>
|
||||
|
||||
#### `haxelib path`
|
||||
|
||||
```
|
||||
haxelib path [project-name[:version]...]
|
||||
haxelib path hscript
|
||||
haxelib path hscript:2.0.0
|
||||
haxelib path hscript erazor buddy
|
||||
haxelib path hscript erazor buddy:1.0.0
|
||||
```
|
||||
|
||||
> Prints the path to one or more libraries, as well as any dependencies and compiler definitions required by those libraries.
|
||||
>
|
||||
> You can specify a version by appending `:version` to the library name. If no version is specified the set version is used.
|
||||
>
|
||||
> If a [development](#dev) version is set it'll be used even if a version is specified.
|
||||
>
|
||||
> This command is used by Haxe compiler to get required paths and flags for libraries.
|
||||
|
||||
|
||||
|
||||
<a name="version" class="anch"></a>
|
||||
|
||||
#### `haxelib version`
|
||||
|
||||
```
|
||||
haxelib version
|
||||
```
|
||||
|
||||
> Prints the version of Haxelib you are using.
|
||||
>
|
||||
> You can change the version of haxelib you are using with <code>haxelib --global [set](#set) haxelib version</code>
|
||||
|
||||
|
||||
|
||||
<a name="help" class="anch"></a>
|
||||
|
||||
#### `haxelib help`
|
||||
|
||||
```
|
||||
haxelib help
|
||||
```
|
||||
|
||||
> Print the list of available arguments.
|
||||
|
||||
|
||||
|
||||
<a name="development" class="anch"></a>
|
||||
|
||||
## Development
|
||||
|
||||
|
||||
|
||||
<a name="submit" class="anch"></a>
|
||||
|
||||
#### `haxelib submit`
|
||||
|
||||
```
|
||||
haxelib submit [project.zip]
|
||||
haxelib submit detox.zip
|
||||
haxelib sumbit
|
||||
```
|
||||
|
||||
> Submits a zip package to Haxelib so other users can install it.
|
||||
>
|
||||
> Alternatively you can run `haxelib submit` without argument to have Haxelib zip and submit the current directory (excluding names starting with a dot).
|
||||
>
|
||||
> If the user name is unknown, you'll be first asked to register an account.
|
||||
> If more the project has more than one developer, it will ask you which user you wish to submit as.
|
||||
> If the user already exists, you will be prompted for your password.
|
||||
>
|
||||
> If you want to modify the project url or description, simply modify your `haxelib.json` (keeping version information unchanged) and submit it again.
|
||||
|
||||
|
||||
|
||||
<a name="register" class="anch"></a>
|
||||
|
||||
#### `haxelib register`
|
||||
|
||||
```
|
||||
haxelib register [username] [email] [fullname] [password] [passwordconfirmation]
|
||||
```
|
||||
|
||||
> Register a new developer account to be used when [submitting](#submit).
|
||||
>
|
||||
> Missing parameters will be asked interactively.
|
||||
|
||||
|
||||
|
||||
<a name="dev" class="anch"></a>
|
||||
|
||||
#### `haxelib dev`
|
||||
|
||||
```
|
||||
haxelib dev [project-name] [directory]
|
||||
haxelib dev starling ../starling/ # Relative path to starling source.
|
||||
haxelib dev starling /opt/starling/ # Absolute path to starling source.
|
||||
haxelib dev starling # Cancel dev, use installed version.
|
||||
```
|
||||
|
||||
> Set a development directory for the given project.
|
||||
> This directory should either contain a `haxelib.json` or the source `*.hx` files.
|
||||
> This command is useful when developing a library and testing changes on a project.
|
||||
>
|
||||
> If the directory is omitted the development version of the library will be deactivated.
|
||||
|
||||
|
||||
<a name="git" class="anch"></a>
|
||||
|
||||
#### `haxelib git`
|
||||
|
||||
```
|
||||
haxelib git [project-name] [git-clone-path] [branch]
|
||||
haxelib git minject https://github.com/massiveinteractive/minject.git # Use HTTP git path.
|
||||
haxelib git minject git@github.com:massiveinteractive/minject.git # Use SSH git path.
|
||||
haxelib git minject git@github.com:massiveinteractive/minject.git v2 # Checkout branch or tag `v2`.
|
||||
```
|
||||
|
||||
> Use a git repository as library.
|
||||
>
|
||||
> This is useful for using a more up-to-date development version, a fork of the original project, or for having a private library that you do not wish to post to Haxelib.
|
||||
>
|
||||
> When you use `haxelib update` any libraries that are installed using GIT will automatically pull the latest version.
|
||||
|
||||
|
||||
|
||||
<a name="hg" class="anch"></a>
|
||||
|
||||
#### `haxelib hg`
|
||||
|
||||
```
|
||||
haxelib hg [project-name] [mercurial-clone-path] [branch]
|
||||
```
|
||||
|
||||
> Use a mercurial repository as library.
|
||||
>
|
||||
> Usage is identical to <code>haxelib [git](#git)</code>.
|
||||
|
||||
|
||||
|
||||
<a name="miscellaneous" class="anch"></a>
|
||||
|
||||
## Miscellaneous
|
||||
|
||||
|
||||
|
||||
<a name="setup" class="anch"></a>
|
||||
|
||||
#### `haxelib setup`
|
||||
|
||||
```
|
||||
haxelib setup [path]
|
||||
```
|
||||
|
||||
> Set the Haxelib repository path. To print current path use <code>haxelib [config](#config)</code>.
|
||||
>
|
||||
> Missing parameter will be asked interactively.
|
||||
|
||||
|
||||
|
||||
<a name="newrepo" class="anch"></a>
|
||||
|
||||
#### `haxelib newrepo`
|
||||
|
||||
```
|
||||
haxelib newrepo
|
||||
```
|
||||
|
||||
> Create a local repository in the current directory, to remove it use <code>haxelib [deleterepo](#deleterepo)</code>.
|
||||
>
|
||||
> [Basic](#basic) commands will only use the libraries stored in the local repository when you are located in this directory.
|
||||
>
|
||||
> To access the global repository add the <code>[--global](#global)</code> flag.
|
||||
|
||||
|
||||
|
||||
<a name="deleterepo" class="anch"></a>
|
||||
|
||||
#### `haxelib deleterepo`
|
||||
|
||||
```
|
||||
haxelib deleterepo
|
||||
```
|
||||
|
||||
> Remove a local repository created with <code>haxelib [newrepo](#newrepo)</code> from the current directory.
|
||||
>
|
||||
> This will remove all libraries contained in it.
|
||||
|
||||
|
||||
|
||||
<a name="convertxml" class="anch"></a>
|
||||
|
||||
#### `haxelib convertxml`
|
||||
|
||||
```
|
||||
haxelib convertxml
|
||||
```
|
||||
|
||||
> Convert the file `haxelib.xml` from the current directory in the Haxelib 2 xml specification into a file named `haxelib.json` which can be used by the current Haxelib.
|
||||
|
||||
|
||||
<a name="run" class="anch"></a>
|
||||
|
||||
#### `haxelib run`
|
||||
|
||||
```
|
||||
haxelib run [project-name[:version]] [parameters]
|
||||
haxelib run openfl
|
||||
haxelib run openfl:2.6.0
|
||||
haxelib run openfl setup
|
||||
haxelib run openfl create DisplayingABitmap
|
||||
```
|
||||
|
||||
> Libraries with either a `run.n` helper or a main class defined in `haxelib.json`, can be executed using `haxelib run`.
|
||||
>
|
||||
> You can specify the version to run by appending `:version`, if the library has a [development](#dev) version set the version will be ignored.
|
||||
>
|
||||
> The library will receive the `HAXELIB_RUN` environment variable with value `"1"` and `HAXELIB_RUN_NAME` with the name of the library as value.
|
||||
|
||||
|
||||
<a name="proxy" class="anch"></a>
|
||||
|
||||
#### `haxelib proxy`
|
||||
|
||||
```
|
||||
haxelib proxy [host port [username password]]
|
||||
```
|
||||
|
||||
> Configure Haxelib to use a HTTP proxy.
|
||||
>
|
||||
> Missing parameters will be asked interactively.
|
||||
>
|
||||
> Rerun with an empty host to deactivate the current proxy.
|
||||
|
||||
|
||||
|
||||
<a name="flags" class="anch"></a>
|
||||
|
||||
## Flags
|
||||
|
||||
|
||||
|
||||
**Warning**: when using the [run](#run) command you need to specify the flags before `run`,
|
||||
otherwise they'll be passed as arguments to the library.
|
||||
|
||||
|
||||
|
||||
<a name="flat" class="anch"></a>
|
||||
|
||||
#### `haxelib --flat`
|
||||
|
||||
```
|
||||
haxelib --flat
|
||||
```
|
||||
|
||||
> Used by <code>haxelib [git](#git)</code>, do not add the `--recursive` flag when cloning a git repository.
|
||||
|
||||
|
||||
|
||||
<a name="always" class="anch"></a>
|
||||
|
||||
#### `haxelib --always`
|
||||
|
||||
```
|
||||
haxelib --always
|
||||
```
|
||||
|
||||
> Answer all questions with yes, cannot be used at the same time as [--never](#never).
|
||||
|
||||
|
||||
|
||||
<a name="system" class="anch"></a>
|
||||
|
||||
#### `haxelib --system`
|
||||
|
||||
```
|
||||
haxelib --system
|
||||
```
|
||||
|
||||
> Use the version of Haxelib installed with Haxe in the system instead of the one currently [set](#set).
|
||||
>
|
||||
> Useful if your Haxelib update was broken.
|
||||
|
||||
|
||||
|
||||
<a name="debug" class="anch"></a>
|
||||
|
||||
#### `haxelib --debug`
|
||||
|
||||
```
|
||||
haxelib --debug
|
||||
```
|
||||
|
||||
> Display debug information during the execution, cannot be used at the same time as [--quiet](#quiet).
|
||||
|
||||
|
||||
|
||||
<a name="quiet" class="anch"></a>
|
||||
|
||||
#### `haxelib --quiet`
|
||||
|
||||
```
|
||||
haxelib --quiet
|
||||
```
|
||||
|
||||
> Display less messages during the execution, cannot be used at the same time as [--debug](#debug).
|
||||
|
||||
|
||||
|
||||
<a name="never" class="anch"></a>
|
||||
|
||||
#### `haxelib --never`
|
||||
|
||||
```
|
||||
haxelib --never
|
||||
```
|
||||
|
||||
> Answer all questions with no, cannot be used at the same time as [--always](#always).
|
||||
|
||||
|
||||
|
||||
<a name="global" class="anch"></a>
|
||||
|
||||
#### `haxelib --global`
|
||||
|
||||
```
|
||||
haxelib --global
|
||||
```
|
||||
|
||||
> Force the usage of the global repository even if inside a local repository created with <code>haxelib [newrepo](#newrepo)</code>.
|
||||
|
||||
|
||||
|
||||
<a name="parameters" class="anch"></a>
|
||||
|
||||
## Parameters
|
||||
|
||||
|
||||
|
||||
**Warning**: when using the [run](#run) command you need to specify the parameters before `run`,
|
||||
otherwise they'll be passed as arguments to the library.
|
||||
|
||||
|
||||
|
||||
<a name="cwd" class="anch"></a>
|
||||
|
||||
#### `haxelib -cwd`
|
||||
|
||||
```
|
||||
haxelib -cwd [dir]
|
||||
```
|
||||
|
||||
> Act like the Haxelib command was run from another repository. Affect all commands that use the "current directory".
|
||||
|
||||
|
||||
|
||||
<a name="notimeout" class="anch"></a>
|
||||
|
||||
#### `haxelib -no-timeout`
|
||||
|
||||
```
|
||||
haxelib -no-timeout
|
||||
```
|
||||
|
||||
> Remove timeout when connecting to the Haxelib server, downloading or [submitting](#submit) a library.
|
||||
|
||||
|
||||
|
||||
<a name="R" class="anch"></a>
|
||||
|
||||
#### `haxelib -R`
|
||||
|
||||
```
|
||||
haxelib -R [host:port[/dir]]
|
||||
```
|
||||
|
||||
> Allow the usage of a custom Haxelib server instead of `lib.haxe.org`.
|
||||
Reference in New Issue
Block a user