Unresolved external symbols when importing a foreign library

[pJotoro]

Context

The version of raylib is 3.7. The version of raygui is the latest version.

Windows 10 odin version dev-2021-10-nightly:3337d386

Expected Behavior

I expect to be able to import a foreign library without getting errors.

Current Behavior

Error messages like this pop up:

C:\Dev\raygui_test>odin build main.odin -build-mode:exe Creating library C:/Dev/raygui_test/main.lib and object C:/Dev/raygui_test/main.exp main.obj : error LNK2019: unresolved external symbol GuiScrollPanel referenced in function raygui_test.main main.obj : error LNK2019: unresolved external symbol GuiGrid referenced in function raygui_test.main main.obj : error LNK2019: unresolved external symbol GuiCheckBox referenced in function raygui_test.main main.obj : error LNK2019: unresolved external symbol GuiSliderBar referenced in function raygui_test.main main.obj : error LNK2019: unresolved external symbol GuiGroupBox referenced in function strconv_decimal.round_down main.obj : error LNK2019: unresolved external symbol GuiGetStyle referenced in function strconv_decimal.round_down main.obj : error LNK2019: unresolved external symbol GuiLabel referenced in function strconv_decimal.round_down main.obj : error LNK2019: unresolved external symbol GuiSpinner referenced in function strconv_decimal.round_down main.obj : error LNK2019: unresolved external symbol GuiSetStyle referenced in function strconv_decimal.round_down main.obj : error LNK2019: unresolved external symbol GuiToggle referenced in function strconv_decimal.round_down C:/Dev/raygui_test/main.exe : fatal error LNK1120: 10 unresolved externals

Interestingly not every procedure gets an error, only some of them, and it's the same procedures every time.

Failure Information (for bugs)

I think this would be the same as for Current Behavior.

Steps to Reproduce

1. Put raygui.lib (I can't attach it here, but I will post it to discord in a sec) and raygui.odin (same as with the other file) in vendor:raylib.
2. Make a new folder and put main.odin (same as with the other files) in there.
3. odin run main.odin

Failure Logs

Already did this earlier.

[github-actions[bot]]

Hello!

I am marking this issue as stale as it has not received any engagement from the community or maintainers 120 days. That does not imply that the issue has no merit! If you feel strongly about this issue

• open a PR referencing and resolving the issue;
• leave a comment on it and discuss ideas how you could contribute towards resolving it;
• leave a comment and describe in detail why this issue is critical for your use case;
• open a new issue with updated details and a plan on resolving the issue.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone..