Skip to content
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

Qt 5.11.2 fails to build in Visual Studio 2017 #451

Open
mleotta opened this issue Sep 27, 2018 · 7 comments
Open

Qt 5.11.2 fails to build in Visual Studio 2017 #451

mleotta opened this issue Sep 27, 2018 · 7 comments
Assignees

Comments

@mleotta
Copy link
Member

mleotta commented Sep 27, 2018

Fletch build fails with Qt 5.11.2 on Windows (Visual Studio 2017). The error seems to be this known issue:

https://bugreports.qt.io/browse/QTBUG-66652?attachmentSortBy=dateTime

I suppose we will need to find a patch for this.

@Cookt2
Copy link
Contributor

Cookt2 commented Oct 1, 2018

According to that link, the build should fail when the path to the QT base directory is 63 or more characters. Our dashboard comes in at 67 characters... I shortened the path and I am running the dashboard now to confirm that this is indeed the problem. Looks like Qt doesn't even have a patch for this problem (yet).

Qt5 in KWIVER is in a weird state for me currently, I cannot seem to get version 5.11.2 to compile successfully on any platforms (win/mac/linux). I'd like to know if any others experience the same troubles..

@aaron-bray
Copy link
Member

aaron-bray commented Oct 1, 2018 via email

@dstoup
Copy link
Collaborator

dstoup commented Oct 2, 2018 via email

@mleotta
Copy link
Member Author

mleotta commented Oct 2, 2018 via email

@Cookt2
Copy link
Contributor

Cookt2 commented Oct 19, 2018

Qt 5.11.2 is building successfully on VS2017. This success looks to be a result of limiting the build path, and a few patches to master.

Nightly: https://open.cdash.org/buildSummary.php?buildid=5586897

Can this issue be closed?

@mleotta
Copy link
Member Author

mleotta commented Oct 22, 2018

If the solution requires that you build Fletch in a path of limited character length, then I think we need to document that requirement in the build instructions before closing this issue.

@dstoup
Copy link
Collaborator

dstoup commented Oct 22, 2018

I agree with Matt. Further, as long as that's the solution, I would prefer this ticket remain open as a reminder that the real solution needs to be found and integrated, even if it's just monitoring upstream to see if they have finally addressed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants