[Issue 13759] VS2010 Win64 linker path wrong
    via Digitalmars-d-bugs 
    digitalmars-d-bugs at puremagic.com
       
    Sat Nov 22 07:26:21 PST 2014
    
    
  
https://issues.dlang.org/show_bug.cgi?id=13759
Rainer Schuetze <r.sagitario at gmx.de> changed:
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |r.sagitario at gmx.de
--- Comment #1 from Rainer Schuetze <r.sagitario at gmx.de> ---
Actually the 32-bit linker is used explicitely because 
- it works just as well to build x64 binaries
- it allows building x64 executables on 32-bit systems
- the filemonitor that records dependencies only works with the 32-bit linker
I guess what's wrong instead is that the PATH environment variable or the
executable path settings contain the path to the amd64 folder, so that the
wrong mspdb100.dll is found.
Maybe the linker executable has to be analyzed for its architecture to set the
appropriate PATH.
> Fresh install of VisualD (0.3.40-b1) into VS2010.
BTW: in case you missed that, there is a beta2 with basic C++ support.
--
    
    
More information about the Digitalmars-d-bugs
mailing list