Bug 17762 – Cannot compile with clean DMD.

Status
RESOLVED
Resolution
FIXED
Severity
normal
Priority
P1
Component
visuald
Product
D
Version
D2
Platform
x86_64
OS
Windows
Creation time
2017-08-19T11:50:12Z
Last change time
2019-06-23T18:13:27Z
Assigned to
No Owner
Creator
Vincent

Comments

Comment #0 by thornik — 2017-08-19T11:50:12Z
I have clean DMD 2.074 installation and some old visuald version. I open visuald project in VS2015-Ent, compile and... lot of bugs due to lack of packages: Error: module completion is in file 'vsi\completion.d' which cannot be read Error: module windef is in file 'sdk\win32\windef.d' which cannot be read Error: module commctrl is in file 'sdk\win32\commctrl.d' which cannot be read If you distribute product in sources, it's a MUST to describe what additional packages should be in system (better with original URL where you get 'em). PS I cannot use precompiled binaries, since author already compromised himself distributing infected DLL.
Comment #1 by greeenify — 2017-08-19T12:02:04Z
> I cannot use precompiled binaries, since author already compromised himself distributing infected DLL. What??? The official releases for Windows are signed and not infected. There was an issue with VisualD being FALSELY detected, but that was an issue on the side of the Antivirus company. > If you distribute product in sources, it's a MUST to describe what additional packages should be in system The release binaries contain everything . Nice run make..
Comment #2 by thornik — 2017-08-19T13:49:36Z
> The official releases for Windows are signed and not infected. Unfortunately, I already had infected visuald.exe and don't want my bad experience repeat, whatever you try to convince me. In any case, it's not bad idea to compile myself; why not? > > If you distribute product in sources, it's a MUST to describe what additional packages should be in system > > The release binaries contain everything . Nice run make.. I talk about SOURCES. If I download sources and compile, they SHOULD compile. If they don't, author should specify what dependencies have to be installed.
Comment #3 by r.sagitario — 2017-08-19T19:16:06Z
Please read http://rainers.github.io/visuald/visuald/BuildFromSource.html Check the appveyor.yml file in case you cannot find some dependencies.
Comment #4 by r.sagitario — 2017-08-19T19:21:08Z
BTW: I don't think there is an infected Visual D installer anywhere on the official download page https://github.com/dlang/visuald/releases If you think there is a not-falsely reported infected version please report the link.
Comment #5 by thornik — 2017-08-20T14:01:30Z
(In reply to Rainer Schuetze from comment #4) > BTW: I don't think there is an infected Visual D installer anywhere It was long time ago, maybe 2-3 years. But it doesn't eliminate the fact of infection. Anyway I don't see any reason to discuss viruses, while REAL REQUEST was about COMPILATION. Rainer, sources are useless if they are not compillable. If you have time/wish, please update "build from sources" page, so people can follow instruction and build add-in w/o any stupid issues. Sources itself is fine, we just need missed packages.
Comment #6 by r.sagitario — 2017-12-02T16:53:25Z
I have updated http://rainers.github.io/visuald/visuald/BuildFromSource.html and cleaned up the Makefile (it is used for building the release and installer only, though).
Comment #7 by r.sagitario — 2019-06-23T18:13:27Z
cleaned up https://rainers.github.io/visuald/visuald/BuildFromSource.html again and removed some outdated solution files that might be confusing.