-
Notifications
You must be signed in to change notification settings - Fork 953
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
Build on Windows fails due to a path-limit error #61
Comments
Hi. Could you please provide output from the following two files so we can investigate this further?
|
So, I made a new clean build, this is the result (sry thats it's in german, do you need it in english? Can I change the language for msbuild output?) The jsoncpp-project-build-err log is empty. |
Thank you for the outputs. German is alright I guess :-). In the outputs, I found the following two errors: 1:
This says that the complete path to the file is too long (longer than 260 characters, which represents a limit on Windows). Could you please try to clone the repository into a shorter path (e.g. 2:
This is a similar error that is reported here. However, we were not able to reproduce it (see this comment). Maybe this is caused by the previous error. I would suggest you to try the build in a shorter path first (see above) and let us know. |
ah nice, I was able to fix it. I changed there
to
I simply took >= 1910 because my _MSC_VER was 1912 EDIT: Well, the path limit fix does not work with msbuild |
I am going to fix |
On VS 2017, _MSC_VER is > 1910, and so the build fails with the following error: Unknown Visual Studio version The fix is based on the sources of LLVM 5.0, where this has been fixed: https://github.com/llvm-mirror/llvm/blob/master/lib/DebugInfo/PDB/DIA/DIASession.cpp#L76 The reason we were unable to reproduce this build issue is that when you open llvm/src/lib/DebugInfo/PDB/CMakeLists.txt, you can see that DIASession.cpp is built only if you have Debug Interface Access SDK (DIA SDK) in your system. For more information, see the following issues: * https://github.com/avast-tl/fileformat/issues/4 * avast/retdec#61
In
Please, can you elaborate? Did it fail with the same error as before or with a different one? |
With exactly the same error. As far as I can see there is nothing you can do about it (except changing the directory structure). MSBuild needs to be "patched" which seems to be quite hard. |
This is strange as we are able to build it on Windows. Nevertheless, we will most definitely try to reduce the length and depth of the directory structure. |
Just to clarify, I can also build the project(s), but just not from my normal path where my other projects are located. Building it from C:\retdec directly works just fine. |
Ah, I see. OK. We will try to do something with the long paths that we create during the build. |
This reduces path lengths, which is important on Windows as there is a limit on how long a path can be (#61).
In ecba1a6, I have reduced the length of paths created by external projects. In the case of Would you be able to test the build of the current |
Works fine now, thx for the fast changes :) |
Perfect, thanks for the verification! |
I currently don't have much time, so forgive me if there is not much detail.
I was able to successfully create the solution by following your description(s), but sadly I got some errors when building the project/solution in VS2017 (latest version).
Added the log, may you can see something.
retdec build log.txt
My setup:
Win 10 Pro x64 (latest version)
VS2017 (latest version)
The text was updated successfully, but these errors were encountered: