Why not dub packaging?
Closed this issue · 7 comments
Expected improvements:
- users discovering LuaD
- drop maintaining VisualD packages.
- As https://github.com/Kelet/DerelictLua supports 5.2, it will be possible to use the "configurations" field to use either dynamic or static binding
- dub is great all around
I was simply waiting for dub to mature. At this point, making a dub package makes a lot of sense.
drop maintaining VisualD packages.
Are the generated VisualD project files as good as the manually maintained ones? The current solution file and project file are both very simple so I'm guessing the answer is yes.
As https://github.com/Kelet/DerelictLua supports 5.2, it will be possible to use the "configurations" field to use either dynamic or static binding
The whole Lua version thing is not so simple, but yeah, switching between bindings shouldn't be hard. I guess the easiest way would be to make luad.c.all
contain a version statement that switched between the two and then import luad.c.all
in all the higher-level modules. In theory, this hurts compilation times for separate compilation, but is probably not an issue in practice.
Are the generated VisualD project files as good as the manually maintained ones?
You often have to turn on warnings, and choose "Mago" debugger, and that's about it.
I'm not very knowledgeable when it comes to dub configurations, I believe gl3n and glamour use it for optional dependencies.
Is there plan to have this implemented soon?
Added a dub.json
just now: 04bb9ff
I can also confirm that dub test
works correctly with this.
I don't want to close this issue just yet though - how can I best handle the examples?
edit:
Seems to have updated on the repository now: http://code.dlang.org/packages/luad
What I do is having a single dub.json for each example.
Yeah even vibe.d does it this way (Sonke must know it, he develops dub too
^^)
On Tue, Feb 11, 2014 at 11:40 PM, ponce notifications@github.com wrote:
What I do is having a single dub.json for each example.
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-34817417
.
Added dub.json
files to all the examples. The hello
example doesn't link due to bug #12144, but the other examples work!
Support for Lua 5.2 should be handled in #19, and I'll open a new issue about the auto-generated VisualD files.