-
Notifications
You must be signed in to change notification settings - Fork 15
Use fletch #30
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
base: master
Are you sure you want to change the base?
Use fletch #30
Conversation
Fletch is part of the KWIVER (http://www.kwiver.org/) ecosystem, of which ViViA is also a part. The purpose of fletch is to provide external third-party dependencies required by KWIVER software. Previously, we have had an implicit dependency on fletch, in that some or all of ViViA's third-party dependencies would typically be provided by fletch, with the developer manually specifying their paths. Adding fletch as an optional dependency allows us to discover those dependencies which are provided by fletch without additional user intervention, which makes it easier to configure ViViA.
|
@dstoup, PTAL. Note also that this has a "soft" dependency on Kitware/fletch#384; that PR is necessary for ViViA to find KML from fletch without additional intervention. (I tested on my machine that this, with both PR's, suffices to find KML and libjson, which are the only dependencies I am consuming through fletch.) |
|
Looks reasonable. When it lands in gitlab, I can verify that it works against all other packages as well. |
|
👍 |
|
FWIW, I needed to specify PROJ4_LIBRARY |
|
Another pass from scratch. I had to specify (in order) VXL_DIR (fletch not build with VXL), vidtk_DIR, kwiver_DIR, and then PROJ4_LIBRARY. |
|
The VXLDIR is troubling as is the PROJ4_DIR. Proj4 is likely a difference
between what fletch exports and what you're expecting, but VXL should be
found assuming you built it in fletch.
…On Fri, Jun 8, 2018 at 5:43 PM, Rusty Blue ***@***.***> wrote:
Another pass from scratch. I had to specify (in order) VXL_DIR (fletch not
build with VXL), vidtk_DIR, kwiver_DIR, and then PROJ4_LIBRARY.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#30 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFRAWqaRrdlrhCvqbepfZhfz4f6S-jxbks5t6u_sgaJpZM4UVTfq>
.
--
David Stoup
Principal Engineer
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY. 12065
518-881-4949 (W)
518-312-3946 (M)
518-371-4573 (F)
|
He didn't (as noted in previous comment). I'm also somewhat concerned about PROJ, though I suppose that's a fletch issue rather than a problem with the PR. |
|
I suspect the PROJ issues is a mismatch of which variables are being
exposed. PROJ vs PROJ4 maybe?
…On Tue, Jun 12, 2018 at 10:04 AM, Matthew Woehlke ***@***.***> wrote:
VXL should be found assuming you built it in fletch
He didn't (as noted in previous comment). I'm also somewhat concerned
about PROJ, though I suppose that's a fletch issue rather than a problem
with the PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#30 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFRAWq6g0VfXURcxpTw0RcZ6Sia0BJ2Aks5t78p6gaJpZM4UVTfq>
.
--
David Stoup
Principal Engineer
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY. 12065
518-881-4949 (W)
518-312-3946 (M)
518-371-4573 (F)
|
Fletch is part of the KWIVER ecosystem, of which ViViA is also a part. The purpose of fletch is to provide external third-party dependencies required by KWIVER software. Previously, we have had an implicit dependency on fletch, in that some or all of ViViA's third-party dependencies would typically be provided by fletch, with the developer manually specifying their paths. Adding fletch as an optional dependency allows us to discover those dependencies which are provided by fletch without additional user intervention, which makes it easier to configure ViViA.