Open AustinEast opened 3 years ago
For local development, you can put the hdll
into the library path along with the base ones that ship with HashLink. See HashLink's Makefile
for the path, it's /usr/local/lib
for me. Then you shouldn't need to have a .hdll
copy per project, unless you want to ship it.
In terms of a Haxe feature, this sounds like something a build macro could do.
I actually made a macro on my sub projects that haxe hdll files to copy them to the output of the current target build along with any other runtime files needed. So in this case, you can add a build macro to hlimgui that copies the prebuilt hdll over to any project that includes the -lib
Keep in mind other targets that use hashlink won't necessarily have hdll files but .so?
Not sure if this is feasible, but it would be very handy if there was a way for a haxelib to automatically import
.hdll
files from a haxe lib into your project.Take my use case for example - I use hlimgui in several Heaps projects. Whenever I need to make a change to
hlimgui
, I have to rebuild the.hdll
, then copy/paste it into all my projects. This can be tedious as the number of projects usinghlimgui
increases.It would make this process much more convenient if haxelib was able to find any
.hdll
files in the root of the library (or from some user-defined directory in the library), then automatically link them to your project.