On Wednesday, 24 June 2015 at 06:54:57 UTC, weaselcat wrote:
On Tuesday, 23 June 2015 at 06:50:28 UTC, Charles Hawkins wrote:
On Tuesday, 23 June 2015 at 03:31:37 UTC, weaselcat wrote:
On Tuesday, 23 June 2015 at 03:29:14 UTC, Charles Hawkins
wrote:
[...]
Try to compile with either ldc or gdc and the -g flag, it
should give you a backtrace. dmd seems to not like linux wrt
backtraces.
Thanks. I wish! I haven't had any success in compiling with
anything but dub. gdc, dmd, rdmd always give me "module mylib
is in file 'mylib.d' which cannot be read" on my "import
mylib;" statement. I've tried every permutation of -I and -L
that I can think of. It almost appears that one either uses
dub for everything or nothing and I'm getting pretty
frustrated with it as well. Perhaps I should just go back to
old-fashioned make files?
you can instruct dub to use other compilers with the --compiler
option
valid options include dmd,ldc,gdc,gdmd,ldmd
Ah, a "sort of" hidden option. I've only been typing "dub" and
thus, "dub --help". Didn't think to do "dub build --help".
Is there a quick way to get gdc to recognize
std.experimental.logger? I'm already spoiled by it. Choosing
between it and a backtrace is difficult.
