[
https://issues.apache.org/jira/browse/MINIFICPP-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893996#comment-16893996
]
Mr TheSegfault commented on MINIFICPP-956:
------------------------------------------
We can and should support doing this. I have a branch based on a NiFi registry
PR ( for bootstrapping agents ) that does just this ( i have my toolchain
compiled b/c of cross compilation needs ). It works quite well, but required a
few changes – wasn't too bad – however, it's predicated upon selecting an
option.
As a result we will always have Apache releases that support this and other
ways of building. This will work to increase the number of travis targets and
increase the complexity. How do you think we can balance those complexities? Do
you think that's something we'll have to figure out over time or do you have a
plan to address those various deployments?
I agree this is a lovely goal that I hope we implement sooner rather than later
but am concerned with the potential implications or complexities of supporting
this – not in a way that we shouldn't do this but rather can we mitigate those
concerns up front?
> Support compiling and linking our own libc++ and depend on libc only as a
> dynamic dependency.
> ---------------------------------------------------------------------------------------------
>
> Key: MINIFICPP-956
> URL: https://issues.apache.org/jira/browse/MINIFICPP-956
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: Daniel Bakai
> Priority: Major
>
> * It would enable us to use C++14/C++17 on all platforms without losing
> compatibility with older Linux systems
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
