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

Fix Windows and Mac OS Github Actions #489

Merged
merged 13 commits into from
Jul 29, 2024

Conversation

johnwason
Copy link
Contributor

No description provided.

@johnwason
Copy link
Contributor Author

Windows will not automatically export const static fields in classes such as these:

https://github.com/johnwason/tesseract_planning/blob/0c28710612a19baa1f2cb6e322d767e56cb39463/tesseract_task_composer/planning/include/tesseract_task_composer/planning/nodes/continuous_contact_check_task.h#L48

Either we need to manually export these symbols or use something other than const static fields.

Copy link

codecov bot commented Jul 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.81%. Comparing base (70e013f) to head (83f3121).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #489   +/-   ##
=======================================
  Coverage   84.81%   84.81%           
=======================================
  Files         231      231           
  Lines       15737    15737           
=======================================
  Hits        13347    13347           
  Misses       2390     2390           

see 19 files with indirect coverage changes

@Levi-Armstrong
Copy link
Contributor

Windows will not automatically export const static fields in classes such as these:

https://github.com/johnwason/tesseract_planning/blob/0c28710612a19baa1f2cb6e322d767e56cb39463/tesseract_task_composer/planning/include/tesseract_task_composer/planning/nodes/continuous_contact_check_task.h#L48

Either we need to manually export these symbols or use something other than const static fields.

I will add the export header and export the static variables.

@johnwason
Copy link
Contributor Author

It looks like the Mac OS build is going to need more upstream fixes. Let's merge this for now to get the Windows fixes.

@Levi-Armstrong
Copy link
Contributor

Why do you have to generate export file for each library? The files are identical except the name of the variable. Could we not just generate one for the core library and use it for everything?

@@ -60,3 +60,4 @@ jobs:
upstream-args: --cmake-args -G "Ninja" -DVCPKG_TARGET_TRIPLET=x64-windows-release -DCMAKE_BUILD_TYPE=Release -DBUILD_IPOPT=OFF -DBUILD_SNOPT=OFF -DTESSERACT_BUILD_TRAJOPT_IFOPT=OFF -DVCPKG_APPLOCAL_DEPS=OFF
target-path: target_ws/src
target-args: --packages-ignore tesseract_examples --cmake-args -G "Ninja" -DVCPKG_TARGET_TRIPLET=x64-windows-release -DCMAKE_BUILD_TYPE=Release -DTESSERACT_ENABLE_TESTING=ON -DTESSERACT_BUILD_TRAJOPT_IFOPT=OFF -DVCPKG_APPLOCAL_DEPS=OFF
run-tests-args: --packages-ignore tesseract_examples
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the current issue with the examples?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't cleaned up the examples for Windows. I don't want to spend the time right now to work on them.

@johnwason
Copy link
Contributor Author

Why do you have to generate export file for each library? The files are identical except the name of the variable. Could we not just generate one for the core library and use it for everything?

Each individual DLL needs to have its own import/export since they may reference each other.

@johnwason
Copy link
Contributor Author

I have the Mac OS working but I need to merge this pull request and a few others in different places.

@Levi-Armstrong Levi-Armstrong merged commit b321b52 into tesseract-robotics:master Jul 29, 2024
10 of 14 checks passed
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

Successfully merging this pull request may close these issues.

2 participants