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

Jump to bottom

Haxelib extraction does not need to happen in each sub-module separately #5

Open
lptr opened this issue Sep 10, 2013 · 0 comments
Open

Haxelib extraction does not need to happen in each sub-module separately #5

lptr opened this issue Sep 10, 2013 · 0 comments

Comments

@lptr
Copy link
Contributor

lptr commented Sep 10, 2013

Currently each sub-module extracts its haxelib dependencies into build/haxelibs. This is redundant, and instead the libs could be stored in the root project, and only extracted once per project instead of once per sub-module.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lptr