-
Notifications
You must be signed in to change notification settings - Fork 83
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
KWIVER_TEST_ADD_TARGETS breaks CMake generation step #1138
Comments
Can you please post the following information?
|
KWIVER:
Fletch:
I used CMake 3.18.3 for the latest tests of both Fletch and KWIVER, but this issue has also happened with versions 3.15.0 and and 3.19.0. Steps to reproduce
|
I assume you mean I wonder if this has ever worked... are you actually trying to use the individual test targets? |
Good catch, yes I meant |
Is removing this unneeded flag useful or should I just close this? |
Probably less chance of confusion if it didn't exist; if you're interested, I'd say go for it. |
I second that. Removing the flag would be much less confusing for future
generations.
…On Tue, Jan 12, 2021 at 3:28 PM Matthew Woehlke ***@***.***> wrote:
Is removing this unneeded flag useful
Probably less chance of confusion if it didn't exist; if you're
interested, I'd say go for it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1138 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKEAWXZVNBAXNTQOXDKNHTSZSWFZANCNFSM4TYTJWYQ>
.
--
David Stoup
Principal Engineer
Kitware, Inc.
1712 Route 9, Suite 300
Clifton Park, NY 12065-3104
518-881-4949 (W)
518-312-3946 (M)
518-371-4573 (F)
|
I am trying to build the up-to-date master on Ubuntu 18.04. Generally it builds fine, but I have been having issues trying to get unit tests for the arrows. After setting
KWIVER_TEST_ADD_TARGETS=True
, CMake will configure fine but fail at the generation step with the following error:Which points to here. Unfortunately, my CMake understanding is very poor, so I don't know if this is a simple error. This issue has persisted for CMake versions 3.15.0, 3.18.0, and 3.19.0.
The text was updated successfully, but these errors were encountered: