Closed yar3333 closed 7 years ago
This should be a relatively small change in path
. It's important to handle paths first and dependencies and named libs after them, otherwise if you have -lib ./liba -lib ./libb
and liba
depends on libb
you're going to get a conflict between the libb
from the haxelib repo and the one from the path.
Now I think, what -lib path_to_lib
feature is not intuitive and brings the unnecessary complexity to haxe. If nobody think else, I close this issue.
In my case I have a set of projects with a references to my own libraries (with dependencies). Local haxelib repo looks like a not good solution:
.haxelib
to every project);.dev
(inside.haxelib
) are absolute andSo, I think,
haxe -lib path_to_the_library
is a good solution...