On 2018-01-11 13:27, DanielG wrote:
I want to create a library and eventually publish it via the DUB registry.
Is there a simple example that shows how to test the library during
development, before publishing (ie, before being able to add it as a
dependency to another project)?
I guess I'm
On Wednesday, 31 January 2018 at 04:57:14 UTC, Joel wrote:
When I try 'dub test' I get errors like 'Source file
'/Users/joelchristensen/jpro/dpro2/JMiscLib/source/jmisc/base.d' not found in any import path.'
You might want to ask this in a new thread so more people see it.
On Thursday, 11 January 2018 at 12:36:22 UTC, Guillaume Piolat
wrote:
On Thursday, 11 January 2018 at 12:27:27 UTC, DanielG wrote:
[snip]
You may have some unittest blocks in your source files, and
then type:
$ dub test
[snip]
When I try 'dub test' I get errors like 'Source file
On Thursday, 11 January 2018 at 14:59:18 UTC, DanielG wrote:
Ah, thank you! I replaced:
"libs-windows-x86-dmd"
with:
"sourceFiles-windows-x86-dmd" (and added a .lib suffix)
and now everything works as expected.
I see now that I was using "libs" improperly. It seems more for
Ah, thank you! I replaced:
"libs-windows-x86-dmd"
with:
"sourceFiles-windows-x86-dmd" (and added a .lib suffix)
and now everything works as expected.
I see now that I was using "libs" improperly. It seems more for
system-wide libraries / things in the library search path, not to
On Thursday, 11 January 2018 at 14:22:50 UTC, DanielG wrote:
If I manually override "libs-windows-x86-dmd" in the example's
dub.json, it links despite the error, but if possible I would
like users of my library to not have to concern themselves with
linkage issues.
vibe.d seems to do it
Thank you very much, very helpful!
I'm currently attempting the (A) suggestion, but find that dub
isn't fixing up the relative path to one of the parent's
prerequisite libraries.
In the parent:
"libs-windows-x86-dmd": ["./lib/32/dmd/SomeLibrary"]
This causes a warning when building the
On Thursday, 11 January 2018 at 12:27:27 UTC, DanielG wrote:
Is there a simple example that shows how to test the library
during development, before publishing (ie, before being able to
add it as a dependency to another project)?
I guess I'm just asking, what's the convention here? Do I
I want to create a library and eventually publish it via the DUB
registry.
Is there a simple example that shows how to test the library
during development, before publishing (ie, before being able to
add it as a dependency to another project)?
I guess I'm just asking, what's the convention
