• via Digitalmars-d-bugs (37/37) Sep 24 2015 https://issues.dlang.org/show_bug.cgi?id=15105

via Digitalmars-d-bugs <digitalmars-d-bugs puremagic.com> writes:

https://issues.dlang.org/show_bug.cgi?id=15105

          Issue ID: 15105
           Summary: paths never work
           Product: D
           Version: D2
          Hardware: x86_64
                OS: Windows
            Status: NEW
          Severity: enhancement
          Priority: P1
         Component: visuald
          Assignee: nobody puremagic.com
          Reporter: turkeyman gmail.com

I've run into yet more cases where default configuration seems to fail.

I'm trying to 'Compile and Disassemble', and my compiler is set to LDC (x64
build).
It just says:
  'ldc2' is not recognized as an internal or external command,
  operable program or batch file.

In the options -> 'LDC install path', I have the LDC install path (not /bin)
I have also tried to set that to the /bin subdirectory, it doesn't work either
way. When I press F7 to build, it does build. It's like it can find LDC when
building, but not when disassembling...?

Getting paths right is an endless nightmare. I've been using VisualD for 6
years, and I still can't seem to get the paths right.

I'm gonna suggest a new strategy; rather than requiring user configuration,
when VisualD can't find a path or tool, or for any other pathing related
problem, I think it should present a dialog box prompting the user to find the
path to the thing it wants. It should give a message saying what it wants (ie,
"where is ldc2.exe?"), and then when the user selects a path, it should write
that to the settings.
This way, if the user fails to configure paths correctly (seems to be close to
100% of the time, especially on initial installation), rather than getting
annoying errors, they will get a prompt to fix it, and it should just work from
there on.

Sound reasonable?

--