-
Notifications
You must be signed in to change notification settings - Fork 21
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 Windows Build #90
Conversation
@Levi-Armstrong is |
We had to turn ninja off on tesseract because of an issue with osqp but not sure why it is now an issue. |
What did you use to build instead? Also it appears that Windows 2022 doesn't install the |
It is using nmake and I think that should be the default. |
4eab51b
to
7b67406
Compare
@Levi-Armstrong how did you get |
508110e
to
d628dc9
Compare
I am not sure what is going on with the windows CI build |
I can get a successful build if I make it install ROS and source the |
Yea I ran into several issues like this. It is very touchy on how you install non ros dependencies and when you source ros, but the order does matter for some reason. |
63d48f8
to
8c71fc1
Compare
choco install openblas -y --no-progress | ||
choco install boost -y --no-progress | ||
choco install eigen -y --no-progress | ||
refreshenv |
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.
This needs to be switched to call RefreshEnv.cmd
calling refreshenv
automatically exits the bash and never builds or runs the test.
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.
Good find. Now that you mention it, I do vaguely recall trying that in a prior attempt and seeing the same thing. I just opened #91 to address. I'll check that it actually builds before merging
* Renamed windows build CI configuration file * Set windows image to 2019 and use nmake
No description provided.