Gildor's Forums

Author Topic: Build system fails (Windows sdk)  (Read 68 times)
Martinn
Newbie
*
Posts: 5


View Profile
Build system fails (Windows sdk)
« on: October 24, 2021, 20:53 »

The build system fails to find the windows sdk headers. Any help to get this working would be appreciated

visual studio version:
Microsoft Visual Studio Community 2019
Version 16.11.2

Windows SDK versions installed:
10.0.18362.0
10.0.19041.0

When I click F12 in the IDE it manges to find the correct header.

My goal was to merge in this to make a more recent version of the software compatible with rocket league packages:
https://github.com/AltimorTASDK/UModel/commit/3dae13f10afb0df0c95a4045c4d6251ce71e2129


Build Log:

Code:
>------ Build started: Project: umodel, Configuration:  ------
  Visual Studio Community 2019 toolset 142 (14.29.30133) [64 bit] found at "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community" ...
  Generating makefile from UmodelTool/umodel.project ...
  ./libs/oodle/lib/Win64/oo2core_win64.lib doesn't exist
  jom ./obj/umodel-vc-win64.mak
  SDL2Loader.cpp
C:\Projects\UEViewer\libs\SDL2\SDL2Loader.cpp(1): fatal error C1083: Cannot open include file: 'Windows.h': No such file or directory
  ExportMd5.cpp
C:\Projects\UEViewer\Core\Core.h(8): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
  ExportGLTF.cpp
C:\Projects\UEViewer\Core\Core.h(8): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
  GameDatabase.cpp
C:\Projects\UEViewer\Core\Core.h(8): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
  ExportMaterial.cpp
C:\Projects\UEViewer\Core\Core.h(8): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
  ExportSound.cpp
C:\Projects\UEViewer\Core\Core.h(8): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
  Exporters.cpp
C:\Projects\UEViewer\Core\Core.h(8): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
  ExportTexture.cpp
C:\Projects\UEViewer\libs\nvtt\nvcore\Debug.h(13): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
  jom: C:\Projects\UEViewer\./obj/umodel-vc-win64.mak [.\obj\libs-win64\SDL2Loader.obj] Error 2
  Export3D.cpp
C:\Projects\UEViewer\Core\Core.h(8): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
  ExportPsk.cpp
C:\Projects\UEViewer\Core\Core.h(8): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
  ExportThirdParty.cpp
C:\Projects\UEViewer\Core\Core.h(8): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
  TypeInfo.cpp
C:\Projects\UEViewer\Core\Core.h(8): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
  jom: C:\Projects\UEViewer\./obj/umodel-vc-win64.mak [.\obj\umodel-win64\Export3D.obj] Error 2
  jom: C:\Projects\UEViewer\./obj/umodel-vc-win64.mak [.\obj\umodel-win64\ExportPsk.obj] Error 2
  jom: C:\Projects\UEViewer\./obj/umodel-vc-win64.mak [.\obj\umodel-win64\TypeInfo.obj] Error 2
  jom: C:\Projects\UEViewer\./obj/umodel-vc-win64.mak [.\obj\umodel-win64\ExportThirdParty.obj] Error 2
  jom: C:\Projects\UEViewer\./obj/umodel-vc-win64.mak [.\obj\umodel-win64\ExportMd5.obj] Error 2
  jom: C:\Projects\UEViewer\./obj/umodel-vc-win64.mak [.\obj\umodel-win64\Exporters.obj] Error 2
  jom: C:\Projects\UEViewer\./obj/umodel-vc-win64.mak [.\obj\umodel-win64\ExportGLTF.obj] Error 2
  jom: C:\Projects\UEViewer\./obj/umodel-vc-win64.mak [.\obj\umodel-win64\ExportMaterial.obj] Error 2
  jom: C:\Projects\UEViewer\./obj/umodel-vc-win64.mak [.\obj\umodel-win64\ExportSound.obj] Error 2
  jom: C:\Projects\UEViewer\./obj/umodel-vc-win64.mak [.\obj\umodel-win64\ExportTexture.obj] Error 2
  jom: C:\Projects\UEViewer\./obj/umodel-vc-win64.mak [.\obj\umodel-win64\GameDatabase.obj] Error 2
  Build time: 0.4 sec

Build failed.
Logged
Gildor
Administrator
Hero Member
*****
Posts: 7997



View Profile WWW
Re: Build system fails (Windows sdk)
« Reply #1 on: October 24, 2021, 22:08 »

BuildTools (vs32tools script) is looking for Windows 10 SDK at "Program Files/Windows Kits/10". It looks for highest SDK version which has "Include" subfolder. If SDK is not found, the error will be displayed.

This is how CURRENT version of UModel/build.sh and vc32tools works. The repository you're pointing at is 4 years old. I'd suggest trying to build current state of my repository just to find the place where the problem exists: VS installation, vc32tools, build.sh in old repository etc.
Logged
Martinn
Newbie
*
Posts: 5


View Profile
Re: Build system fails (Windows sdk)
« Reply #2 on: October 24, 2021, 22:27 »

https://imgur.com/a/wWrAI5X

it should detect these folders just fine then?
Both sdk folders have a um folder which contains a windows.h

I did fork the current repo and tried to build that.
Once I had that working my plan was to start debugging why the current repo fails for the rocket league packages (after decrypting them), while that ancient repo still works.
Logged
Martinn
Newbie
*
Posts: 5


View Profile
Re: Build system fails (Windows sdk)
« Reply #3 on: October 24, 2021, 22:51 »

Looking at the script. it seems to be picking the wdf folder. So that would be my issue

hacky solution as I don't really know bash at all
Code:
if [[ $d > $win10sdk_ver && $d != 'wdf' ]]; then
« Last Edit: October 24, 2021, 22:59 by Martinn » Logged
Martinn
Newbie
*
Posts: 5


View Profile
Re: Build system fails (Windows sdk)
« Reply #4 on: October 25, 2021, 00:03 »

I made a pull request with the required changes
https://github.com/gildor2/UEViewer/pull/245
Logged
Gildor
Administrator
Hero Member
*****
Posts: 7997



View Profile WWW
Re: Build system fails (Windows sdk)
« Reply #5 on: October 25, 2021, 00:08 »

This PR contains a very strange and hacky solution for the game which is probably not supported by "vanilla" UModel for a long time.
Logged
Martinn
Newbie
*
Posts: 5


View Profile
Re: Build system fails (Windows sdk)
« Reply #6 on: October 25, 2021, 00:43 »

Fair enough. The decryptor doesn't modify the header of the package at all, so the modified name is really the only way of detecting those that I can think of. If you don't want that hacky solution in your repo, I'll just have to maintain my fork.
Logged
Jump to:  

Powered by SMF | SMF © 2006-2009, Simple Machines LLC
Leviathan design by Bloc | XHTML | CSS