-
Notifications
You must be signed in to change notification settings - Fork 615
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alpha-4 static MSVC2017 doesn't work with cl
#412
Comments
When statically linking, you'll need to include the list of libraries libui links against, which is, for alpha 4:
So you'll need to add this to the linker flags:
If you're using |
Thanks for the quick reply. I still have two more errors:
Not sure how to fix those. Should there be instructions to include those libraries in |
Oh right, you'll also need the proper |
I got this error message:
|
Note: I am using Visual Studio 2019, 16.0.0-pre2.0 NOT 2017. Is that the problem? Output of
|
It seems like the |
Thanks for your reply. I'm currently not on that computer, but I wil try that as soon as I can. |
I am not very familiar with Windows, but I have mostly identified the cause. The problem occurs when calling MsgBox, which is implemented with TaskDialog. TaskDialog needs comctl32 version 6, but the default is version 5. To fix this, you need to specify version 6, for example, by creating a manifest file in the same folder as the executable. While this may be a bit inconvenient for a portable library like libui, it is a workable solution. |
I'm using the x64 Native Tools Command Prompt for VS 2017, and I'm trying to convert a
.o
file generated via Crystal code (code here, the.o
file generated using these instructions).I have the
libui.lib
from the release file for 64-bit VS 2017, and I've copied it intoC:\Crystal
, along with otherlib
files required for Crystal (gc.lib
,pcre.lib
) andcontrol_gallery.o
. However, once I run thecl
command, it doesn't work and raisesLNK2001
andLNK2019
errors.Here is my folder structure:
Here is the full error log:
The text was updated successfully, but these errors were encountered: