Nandor Soma Abonyi created MINIFICPP-1528:
---------------------------------------------

             Summary: Inconsistent dependency listing in README
                 Key: MINIFICPP-1528
                 URL: https://issues.apache.org/jira/browse/MINIFICPP-1528
             Project: Apache NiFi MiNiFi C++
          Issue Type: Bug
            Reporter: Nandor Soma Abonyi


I've tried to compile minifi on macOS Catalina 10.15.7 based on the README and 
I've found a few issues which might need improvement:

_In README / System requirements / To build / Utilities:_

This part is a bit misleading because it mixes compilers and only a part of the 
required libraries. If the goal is to highlight the required versions then it's 
clearer to list all of the libraries there. However, I think it would be better 
if only those dependencies would be listed there which are needed to run 
bootstrap.sh.

_In README / System requirements / To run /  OS X Using Homebrew (with XCode 
Command Line Tools installed):_

Here the script installs dependencies that are needed purely for compile, like 
cmake. Also lists dependencies that are statically linked into the binary. 
Neither of them needed to run minifi. The rest are dynamically linked 
dependencies and runtimes that make sense but they need a bit more description 
when and why they are needed.

_Running "bootstrap.sh" -b -p does not install pkg-config:_

related log:

 
{code:java}
[ 35%] Performing patch step for 'coap-external'


[HINT] You can run 'autogen.sh --clean' to remove all generated files by the 
autotools.


Found 'autoconf'.
Found 'aclocal'.


Couldn't find 'pkg-config'!
You probably need to install the package 'pkg-config|pkgconf'.
Found 'libtool'.


One or more needed tools are missing, exiting ...
Please install the needed software packages and restart 'autogen.sh' again.


make[2]: *** [coap-external-prefix/src/coap-external-stamp/coap-external-patch] 
Error 1
make[1]: *** [CMakeFiles/coap-external.dir/all] Error 2
make: *** [all] Error 2
{code}
 

 



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

Reply via email to