Failed to build CDK

[JustMinna]

Been trying to build the CDK tools but I keep getting an error

Am I doing something wrong or am I missing something?

[OshidaBCF]

i created a random file in the bin inside the simlink to find where it was, and it seem to use vc2022

the py code that make link open the path Program Files (x86)\Microsoft Visual Studio\2022\BuildTools so it make sense that i would take 22 no ?

Am i mixing up names again ?

[NicSavichev]

i created a random file in the bin inside the simlink to find where it was, and it seem to use vc2022

the py code that make link open the path Program Files (x86)\Microsoft Visual Studio\2022\BuildTools so it make sense that i would take 22 no ?

Am i mixing up names again ?

Yes, change symlink manually to 2019. We will fix script later to avoid this bug

[OshidaBCF]

i don't have any "2019" folder next to the 2022, i guess i would need to install VS 2019

I'm not sure how to edit symlink, should i just modify the pyscript, and run it again after deleting the folder ?

[OshidaBCF]

log.txt

I got some external help to install VCR2019, after redoing the symlink, this is what the build did.

It seems to have managed to build Dav1d's lib

Now it's having some error on what looks to be previously build files, so i guess i should rebuild from scratch

[NicSavichev]

Now it's having some error on what looks to be previously build files, so i guess i should rebuild from scratch

Yes, this is true. jam tries to check dependences as much as possible but it doesn't handle case when changing compiler for the same output PDB will likely fail

[OshidaBCF]

I mean that does make some sense, if the file is already there it's a good guess that it was just already built before

Right now i'm recompiling and it seems to have no error... yet

[OshidaBCF]

After 2 hours, building finally finished, how long does it usually take you ? log.txt

i think i got a few errors about "shaders", but otherwise everything should be alright

[NicSavichev]

After 2 hours, building finally finished, how long does it usually take you ? [log.txt]

compilation takes 30 min (but I use 36-cores i9 and SSD)

[OshidaBCF]

Yeah i have a 8 core R7

sadly this didn't helped me fix my problem mentioned in #2

I couldn't find in the files a reason why oodle wouldn't open

[NicSavichev]

I couldn't find in the files a reason why oodle wouldn't open

what Oodle do you have? we use 2.9.2 for runtime (game and unpack) and 2.7.6 for packing in tools (hold older version to avoid updating 50Gb of texture packs) if Oodle is linked then tools should be able to unpack them did you try ddsx2dds with -dump option to see header's dump?

[OshidaBCF]

-dump works and -check:OODLE also work

As for the Oodle version, i have no idea the only thing i have is the name, oo2core_6_win64.dll

it works with the previous tool i had so it should work with this one

how do i link the dll ?

[NicSavichev]

how do i link the dll ?

I don't think it is possible since we use static libs case win32 : AddLibs += $(oodle_dir)/static_lib/oo2core_win32.lib ; case win64 : AddLibs += $(oodle_dir)/static_lib/oo2core_win64.lib ; If you do have license for OODLE then you have these headers and libs C:\devtools\oodle.2.9\include\oodle2.h C:\devtools\oodle.2.9\include\oodle2base.h C:\devtools\oodle.2.9\include\oodle2x.h C:\devtools\oodle.2.9\static_lib\oo2core_win32.lib C:\devtools\oodle.2.9\static_lib\oo2core_win32_debug.lib C:\devtools\oodle.2.9\static_lib\oo2core_win64.lib C:\devtools\oodle.2.9\static_lib\oo2core_win64_debug.lib and import libs must be located here C:\devtools\oodle.2.9\lib\oo2core_win32.lib C:\devtools\oodle.2.9\lib\oo2core_win64.lib but you should change prog/engine/ioSys/jamfile too in order to link import libs instead of static ones

[OshidaBCF]

right now i only have the dll, but i'll try to aquire the lib.

if i can get the lib, do i just put in a folder in the "build folder" ?

like Build/oodle.2.7.oo2core_win_64.lib ?

[NicSavichev]

As for the Oodle version, i have no idea the only thing i have is the name, oo2core_6_win64.dll also I suspect this name means Oodle ver 2.6.x and it may be just incompatible with 2.7.6 that we use for packing you need newer lib anyway

[OshidaBCF]

i see....

well if i can find a lib i can probably find newer

[NicSavichev]

well if i can find a lib i can probably find newer

I need lib anyway, static one or import one you cannot use DLL without any lib (import libs loads that DLL and resolves symbols)

[OshidaBCF]

oh god... it's starting to get quite complicated

[OshidaBCF]

i found a lib, that was easier than expected, 3 month old so it should be fine no ?

[OshidaBCF]

case win64 : AddLibs += $(oodle_dir)/static_lib/oo2core_win64.lib ;

Do i just have to do that an rebuild the tool ?

[NicSavichev]

Do i just have to do that an rebuild the tool ? ![image](https://user-images.githubusercontent.com/61458287/278892235- yes, run X:\github\DagorEngine.git\prog\tools\build_dagor3_cdk_mini.cmd or jam in X:\github\DagorEngine.git\prog\tools\converters\ddsx2dds\

[OshidaBCF]

Oh yeah i guess that now that it can find the lib it'll build it

[OshidaBCF]

log.txt

It build some new files but still failed because it couldn't find all the headers and things (i forgot to log the first build)

[NicSavichev]

log.txt

It build some new files but still failed because it couldn't find all the headers and things (i forgot to log the first build)

you need ...\build\oodle.2.7\include\oodle2.h to compile

[NicSavichev]

also you can use jam -dx to see actual commandline (so you know what folders are added for includes, etc.)

[OshidaBCF]

IT WORKEDDDDDDDDDDDDDDDDDDDD

HAHAHAHAHAHAHA

[OshidaBCF]

Thanks a lot <3

[NicSavichev]

@JustMinna You need to build Gaijin fork of jam build.vc.cmd was not working for me for some reason. I used generated cmake to build it. Check the VC_DIR and WINKIT_DIR before running.

You don't need to build 'jam' at all, get EXE from releases https://github.com/GaijinEntertainment/jam-G8/releases/download/2.5-G8-1.2-2023%2F05%2F04/jam-win64.zip just unpack it to any folder that exists in PATHs

[JustMinna]

Alrighty, thanks

[JustMinna]

Did you find a fix for this issue?

It has been fixed

[JustMinna]

However I'm having another issue... I can probably download this dll from somewhere though... I assume

[NicSavichev]

However I'm having another issue... I can probably download this dll from somewhere though... I assume

This DLL (as well as many other important files) are located in tools-base.7z (downloadable from releases) and that these files must be unpacked to repo folder before building and using built tools

[OshidaBCF]

I had it downloaded and copied the PVRTexLib, it could launch but then crashed because of shaders not being compiled

now i understand why i should have merged the two folder, the building override the exes right ?

[NicSavichev]

now i understand why i should have merged the two folder, the building override the exes right ? Yes, initially we combine GIT repo + 2 unpacked base archives (refer to newly added README.md for details). Then we build tools (build_dagor3_cdk_mini.cmd) and samples (EXE with jam, shaders with compileshaders*.bat and game resources with dabuild.cmd; sometimes we need to build pre-rasterized fonts). After building these (it is development pipeline) we can run samples.

Instead of building tools you can download and unpack tools-prebuilt.7z Instead of building samples you can download prebuilt data and EXE samples-prebuilt-game.7z Rebuilding EXE is easiest part of build pipeline.

[OshidaBCF]

I see that a lot of files changed

Should i delete everything and redo everything from 0 ?

[NicSavichev]

Should i delete everything and redo everything from 0 ?

No, just update, run make_devtools.py once more (it will download missing pre-requisites) and build code incrementally with jam. It was essentially what I did when tested changes in repo before pushing. _Output can be removed/cleaned at any time to force clean build but this will take much time to rebuild everything from scratch. Also you could jam only tool you need (instead of building everything with batch script), I think you need this folder DagorEngine.git\prog\tools\converters\ddsx2dds\

[OshidaBCF]

Well i was curious and have time to spend, so i just redid everything from scratch

The py script seems to have removed a couple of elements from my Path variable, a few programs (jam included) couldn't be called anymore

[NicSavichev]

The py script seems to have removed a couple of elements from my Path variable, a few programs (jam included) couldn't be called anymore

Really strange, when I tested it script downloaded jam to root of devtools folder and asked to add devtools folder to the paths (but I never tried to confirm adding)

[OshidaBCF]

i had jam.exe on my pc from yesterday, the py script didn't download jam at all

Maybe it checked if i had jam and noticed i did ?

[NicSavichev]

Maybe it checked if i had jam and noticed i did ?

it searches jam.exe in PATH folders and skips installing if found

[OshidaBCF]

then perhaps it found it and overwrote everything after it + a few lines before.

When i opened the path, the last line onlt had "C:/P" inside probably the start of C:/Program x86

[NicSavichev]

When i opened the path, the last line onlt had "C:/P" inside probably the start of C:/Program x86

Don't use folders with spaces in name when dealing with jam. This wil cause awful headache

[OshidaBCF]

it's just the translation, iirc the actual folder doesn't have spaces.

[OshidaBCF]

Well i was curious and have time to spend, so i just redid everything from scratch

The py script seems to have removed a couple of elements from my Path variable, a few programs (jam included) couldn't be called anymore

It seems that this was actually caused by my global Path variable being too long, after starting my computer this morning, a few lines have been removed again

[NicSavichev]

It seems that this was actually caused by my global Path variable being too long, after starting my computer this morning, a few lines have been removed again

fixed script