"The ordinal 380 could not be located in the dynamic link library"

CFiggers commented 2 months ago

I receive this message after building jwno:

Steps to reproduce:

Clone janet-lang/janet
Clone agent-kilo/jw32
Clone agent-kilo/jwno
Open x64 Native Tools Command Prompt for VS 2022
Run set JANET_SOURCE_PATH=%HOMEPATH%/projects/janet/janet
Change directory into jw32, run jpm -l build and jpm --tree=../jwno/jpm_tree install
Change director into jwno, run jpm -l build
All build steps complete without warnings
Try to run built jwno.exe

agent-kilo commented 2 months ago

There's one more step: Run jpm -l run embed-manifest after jpm -l build in Jwno's source tree.

This is caused by using a wrong version of Common Controls DLL. The embed-manifest task will put manifest/jwno.manifest into jwno.exe, specifying the right version, so that windows knows which DLL to use when launching the exe. That step is mandatory.

I tried to remove this extra step, but failed due an error I don't fully understand. Check the comment at the bottom of project.janet if you're curious 😅

And it's better to use the latest Janet release version when building. Jwno is only tested against the latest release.

Edit: Links to the mentioned files

CFiggers commented 2 months ago

That was it—failure to follow the instructions. 😅 Thank you!

agent-kilo / jwno

"The ordinal 380 could not be located in the dynamic link library" #2