FiveTech Software tech support forums

... del Resedit , utilizo estos. (aunque no creo que sea el problema ya que me da error al construir el ejecutable)

C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt
C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\shared
C:\Program Files (x86)\Windows Kits\10\include\10.0 ...

ODBC32 is a library from your C compiler,
if you are using BCC:
C:\bcc7\lib\psdk

I use MSVC
C:\Program Files (x86)\Windows Kits\10\Lib\10.0.26100.0\um\x86

... exe (found version "2.43.0.windows.1")
3>Building Custom Rule F:/llama.cpp/common/CMakeLists.txt
3>build-info.cpp
2>C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um\winbase.h(9531,5): warning C5105: Die Makroerweiterung, die "defined" erzeugt, weist ein nicht definiertes Verhalten auf ...

... Visual Studio Enterprise tengo el compilador de recursos rc en esta ruta.
Tambien lo teneis ahi vosotros o esta en otra, lo digo por acotar el problema con FivEdit.
C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x86\rc.exe

Muchisimas gracias por vuestra inestimable ayuda.

Saludos.

Jose.

... donde están los ficheros de cabecera para el comando de compilación en línea de comandos con:
cl -TC -W3 -O2 -c /I"C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um" /I%hdir%\include %1.c


Y obtengo los errores siguientes:
.Compila con Harbour 64 ...Harbour 3.2.0dev (r1412151448 ...

... al compilar me dice que faltan y resulta que estaban presentes en varios directorios, entre otros por ejemplo en: C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um

Aunque me ha extrañado que los ficheros de cabecera, que son estandard, no se encuentren en ningún directorio de la ...

Hi mr. Navarro,

I use w10.

There is a directory like that.
[url]C:\Program Files (x86)\Windows Kits\10\Lib\10.0.18362.0\um\x86[/url]

... Microsoft Visual Studio \ 2019 \ Community \ VC \ Tools \ MSVC \ 14.26.28801 \ include"
SDK folder: SDKDIR = "C: \ Program Files (x86) \ Windows Kits \ 10 \ Lib \ 10.0.18362.0 \ um \ x86"
SDK include folder: SDKDIRINC = "C: \ Program Files (x86) \ Windows Kits \ 10 \ Include \ 10.0.18362.0 \ um ...

... exe
64=C:\Program Files\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\bin\Hostx86\x86\link.exe
65=C:\Program Files (x86)\Windows Kits\8.1\bin\x86\rc.exe
68=.F.
74=C:\Program Files\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\bin\Hostx86\x86\cl.exe
1=c:\fwh
3=
4 ...

... exe
64=C:\Program Files\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\bin\Hostx86\x86\link.exe
65=C:\Program Files (x86)\Windows Kits\8.1\bin\x86\rc.exe
68=.F.
74=C:\Program Files\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\bin\Hostx86\x86\cl.exe
1=c:\fwh
3=
4 ...

... and #using available only in C++ compiler
dshow.prg(57): error C2039: 'Run': is not a member of 'IMediaControl'
C:\Program Files (x86)\Windows Kits\10\include\10.0.14393.0\um\control.h(473): note: see declaration of 'IMediaControl'
dshow.prg(64): error C2039: 'Stop': is not a member of ...

... Harbour, after a minor modifications to the instructions provided here (for example the windows libraries are in " C:\Program Files (x86)\Windows Kits\8.1\Lib\winv6.3\um\x86 ").

It is working just fine so far, I have been using MSVC 2013+Fivewin1602+harbour and changing to the new versión of ...

... Files (x86)\Microsoft Visual Studio 14.0\VC\lib\ and look for such name in all libs.
I use Total Commander to do it. If it is not found then next step:

3. Go to c:\Program Files (x86)\Windows Kits\8.1\Lib\ and repeat the step 2.

In this case, I found: shell32.lib

This way you can fix all of them

Hakan,

You have to link:

..\..\Program Files (x86)\Windows Kits\8.1\Lib\winv6.3\um\x86\gdiplus.lib

... told to add the windows libraries from a path specified as Windows SDKs. Now the path for those files needs to be:
c:\Program Files (x86)\Windows Kits\8.1\bin\x86
Follow the same procedure but get the files from this new location for VS 2015.

4) Finally, VS IDE has a decent editor if you want to ...