[
https://issues.apache.org/jira/browse/MINIFICPP-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899174#comment-16899174
]
Mr TheSegfault commented on MINIFICPP-994:
------------------------------------------
[~aboda] I just happened to notice an affects version of 0.6.0. This extension
didn't exist in that release.
> Opencv shouldn't be build by bootstrap (cmake), just cloned. Building it
> should be part of MiNiFi build.
> --------------------------------------------------------------------------------------------------------
>
> Key: MINIFICPP-994
> URL: https://issues.apache.org/jira/browse/MINIFICPP-994
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
> Affects Versions: 0.6.0
> Reporter: Arpad Boda
> Assignee: Nghia Le
> Priority: Minor
>
> Opencv is built when executing a cmake command (for eg. using bootstrap),
> which seems to be wrong as:
> * This build is single-threaded, takes a lot of time
> * Linker warnings are generated when building MiNiFI:
> {code}
> ld: warning: direct access in function '___cxx_global_var_init.35' from file
> '../thirdparty/opencv/opencv-external/src/opencv-external-build/lib/libopencv_flann.a(miniflann.cpp.o)'
> to global weak symbol 'guard variable for
> cvflann::anyimpl::SinglePolicy<std::__1::basic_string<char,
> std::__1::char_traits<char>, std::__1::allocator<char> > >::policy' from file
> 'CMakeFiles/CaptureRTSPFrameTest.dir/CaptureRTSPFrameTest.cpp.o' means the
> weak symbol cannot be overridden at runtime. This was likely caused by
> different translation units being compiled with different visibility settings.
> {code}
> Static linking should be kept when integrating opencv build to the build
> process of MiNiFi.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
