Ok, thanks for the information. As I understand it, I can use vs 2019.
How ever, I am not very sure which components to install. The README says that I should install:
◾ In the Installation details section, under Individual components, ensure the following are selected:
◾ Visual C++ compilers and libraries for ARM64
◾ Visual C++ ATL for ARM64
I cannot find those specific names, so I tried to install the following:
* MSVC v141 - VS 2017 C++ ARM64 build tools (v14.16)
* C++ ATL for v141 build tools (ARM64)
But when I run scons source I get the following error:
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
link /nologo /incremental:no /WX /subsystem:windows,6.02 /release /OPT:REF /export:DllGetClassObject,private /export:DllCanUnloadNow,private /export:GetProxyDllInfo,private /manifest:embed /manifestinput:build\a
rm64\IAccessible2proxy.manifest /dll /out:build\arm64\IAccessible2proxy.dll /implib:build\arm64\IAccessible2proxy.lib rpcrt4.lib oleaut32.lib ole32.lib /PDB:build\arm64\IAccessible2proxy.dll.pdb /DEBUG build\arm
64\ia2_i.obj build\arm64\ia2_p.obj build\arm64\ia2_data.obj
LINK : fatal error LNK1104: cannot open file 'LIBCMT.lib'
scons: *** [build\arm64\IAccessible2proxy.dll] Error 1104
scons: building terminated because of errors.
Can anyone help me to solve the problem and build NVDA?
On 8/31/2019 6:44 PM, Brian's Mail list account via Groups.Io wrote:
I suppose you could prove it by using jaws demo and see if it works differently?
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message ----- From: "Karl-Otto Rosenqvist" <Karl-otto@...>
Sent: Saturday, August 31, 2019 9:35 AM
Subject: Re: [nvda-devel] Visual studio version
I’m using NVDA with both Visual Studio 2017 and 2019 and it works quite well.
The most annoying thing is that Visual Studio compiles your code in the background and that takes quite a lot of processing power so NVDA stops talking sometimes.
This occurs when moving in the solution tree with the keyboard and when a file is selected Visual Studio automatically opens it in the editor which seems to be a heavy task. It’s probably NVDA that processes the text in the file that’s beeing shown in the editor and that’s why it stops talking.
When I build a solution and there are errors that’s shown in the error list there’s a looong silence before NVDA starts talking again. That’s probably the compilation that kills it.
I’ve tried to lower the execution priority for the compiler and ide and increased the priority of NVDA but it tidn’t make any difference.
0701-75 98 56
Även om det är ett äpple på baksidan så får du inte tugga på min mobil!
31 aug. 2019 kl. 05:51 skrev Luke Davis <luke@...>:
You may want to search the archives, this question has come up before. I believe the answer was that it's fine to use 2019, but there was a small issue or two. I can't remember exactly.
On Fri, 30 Aug 2019, Tage Johansson wrote:--
Do I need visual studio 2017 specificly or is it fine to use visual studio 2019?
Moderator: the new NVDA Help mailing list! (https://groups.io/g/NVDAHelp)
Author: Debug Helper NVDA add-on (https://github.com/XLTechie/debugHelper)