On 4/17/20 4:37 AM, WebFreak001 wrote:
On Thursday, 16 April 2020 at 19:56:44 UTC, Adam D. Ruppe wrote:
For future reference, newer dubs (v 1.17 + i think) allow
--compiler=dmd-version for example.
You need to put the exe in your PATH and rename it yourself, but it
recognizes *dmd-* (or *ldc2
On Thursday, 16 April 2020 at 19:56:44 UTC, Adam D. Ruppe wrote:
For future reference, newer dubs (v 1.17 + i think) allow
--compiler=dmd-version for example.
You need to put the exe in your PATH and rename it yourself,
but it recognizes *dmd-* (or *ldc2-* or *gdc-*) all the same so
you can s
For future reference, newer dubs (v 1.17 + i think) allow
--compiler=dmd-version for example.
You need to put the exe in your PATH and rename it yourself, but
it recognizes *dmd-* (or *ldc2-* or *gdc-*) all the same so you
can specifiy them.
I was doing that in early versions of my android t
On 4/16/20 3:34 PM, Jonathan M Davis wrote:
I_was_ going to suggest just building dub yourself
I already tried that of course ;)
-Steve
On Thursday, April 16, 2020 12:41:14 PM MDT Steven Schveighoffer via
Digitalmars-d-learn wrote:
> On 4/16/20 2:28 PM, Steven Schveighoffer wrote:
> > OK, I thought, just put it in ~/bin, and run it from there. Doesn't
> > work, now it looks in ~/bin (where there is no compiler), and fails.
>
> I w
On 4/16/20 2:28 PM, Steven Schveighoffer wrote:
OK, I thought, just put it in ~/bin, and run it from there. Doesn't
work, now it looks in ~/bin (where there is no compiler), and fails.
I wish I could delete this idiotic post.
I had a broken link to a dmd compiler in ~/bin. Removing that now i
I'm running into an issue where I need to run an old compiler to build
something, but the dub installation included with that compiler seems to
have an infinite loop problem. So I want to run a standalone version of
dub, but whatever compiler is selected with my path. Problem is, when I
run the
