-
Notifications
You must be signed in to change notification settings - Fork 170
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
Building gtk fails with a too long string (>65536 chars) [VisualCode 2019/v16] #827
Comments
Hi @F-Loyer, do you have long paths enabled in Windows? |
It is not about the path, but the compilator doesn't like some long strings inside the I have tried to remplace the string by a list or number... but get the following error:
The heap space is not suffisient for the compiler. I note the progress... the error is produced at the line 15612... and not 4105... But we need to handle 10 times more lines ! The error is covered here https://learn.microsoft.com/en-us/cpp/error-messages/compiler-errors-1/fatal-error-c1060?view=msvc-170, but with an x64 system, I am surprised by this error. |
Do you have the Diskuv OCaml setup instructions that you are following so that we can try to reproduce this? I haven't seen this issue before, so there must be something unique with your setup. |
I have followed https://diskuv-ocaml.gitlab.io/distributions/dkml/# (and use the Diskuv installer). But, the Visual Studio 2019 is installed automatically in a fancy directory, but this installation is made by the Visual Studio Installer. I don't think the compiler installation is wrong (the 65535 characters limit is documented by Microsoft). The issue can come from the |
I finally solved my issue, using VS2022. The |
I have tried
gvsbuild build --vs-ver 16 --vs-install-path C:\DiskuvOCaml\BuildTools gtk3
. Since I have Visual Code 2019 which is proposed by the Diskuv project (an Windows Ocaml port).I have the following errors:
Since the compiler is limited to 65536 characters strings, I guess I should process the file to replace "\000\001\002..." by 0, 1, 2 or somehing like this.
The text was updated successfully, but these errors were encountered: