-
Notifications
You must be signed in to change notification settings - Fork 178
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
Fix azure on windows #388
Merged
Merged
Fix azure on windows #388
Changes from 12 commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
7bf3a3c
Update ccache for 07.04.2020
95f5efb
Update variable used for indicate boost headers location
488fdef
Fix BOOST_ROOT unset in azure-pipelines for windows
6bef88a
Fix BOOST_ROOT has been deprecated in azure pipelines
088dafe
Try to fix azure-pipeline
aaea2b8
Try to fix azure-pipeline
13f1bda
Try to fix azure-pipeline
861684a
Try to fix azure-pipeline
1f2048e
Try to fix azure-pipeline
29c0eb9
Try to fix azure-pipeline
00fe94f
Try to fix azure-pipeline
3ae182e
Try to fix azure-pipeline
8a3d96b
Try to fix azure-pipeline
3b9adf0
Try to fix azure-pipeline
97ba02a
Try to fix azure-pipeline
fcc38d1
Try to fix azure-pipeline
b355ba0
Try to fix azure-pipeline
8224338
Try to fix azure-pipeline
33cbff9
Try to fix azure-pipeline
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps this is just experimentation, but isn't it dangerous to tie ourselves to this particular version (1.72.0)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, we only have 2 versions of boost in the pipeline see.
It's necessary to chose one or the other. Or, another option would be to add a shell scripts which can download latest version of boost and put it in a specific folder.
At the moment I could resolve the initial issue, but now the compilation cannot find the boost header files ...
It's really hard to debug like that, if you have any suggestion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My point is about these lines being not tied to our Azure set-up. They should work outside of our CI, and hence with arbitrary versions, or am I missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am looking at the log but I can only see a massive amount of warnings and no error in the compilation itself. Did I miss the error?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Look for
fatal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, printing the content of
boost
folder on the pipeline shows that headers are missing (likerange.hpp
).I'll ask directly the maintainers of the azure pipelines is there's an issue here or we're missing something.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just out of curiousity, was there a problem from azure or was it something else?