You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Marton Szasz (Jira)" <ji...@apache.org> on 2021/01/21 15:52:15 UTC

[jira] [Updated] (MINIFICPP-1036) Review libarchive compilation

     [ https://issues.apache.org/jira/browse/MINIFICPP-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marton Szasz updated MINIFICPP-1036:
------------------------------------
    Fix Version/s:     (was: 0.8.0)
                   0.9.0

> Review libarchive compilation
> -----------------------------
>
>                 Key: MINIFICPP-1036
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-1036
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Task
>            Reporter: Dániel Bakai
>            Assignee: Dániel Bakai
>            Priority: Major
>             Fix For: 0.9.0
>
>          Time Spent: 6h 50m
>  Remaining Estimate: 0h
>
> libarchive automatically decides whether to use libz, libbz2 and liblzma based on the build host, and then dynamically links with the ones it found.
> This means that we don't have propert control over what libraries we end up linking with (unless we have complete control over the build host), and it makes it hard to convert libarchive to an ExternalProject. It also prevents proper Windows build.
> Because we almost always build zlib as it is, and neither libbz2 nor liblzma takes too long to build, I suggest that we bundle them. This would make hard-to-control dynamic depenencies go away, and make it easier to have complete libarchive support on Windows.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)