[
https://issues.apache.org/jira/browse/MINIFICPP-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777079#comment-16777079
]
Mr TheSegfault commented on MINIFICPP-672:
------------------------------------------
For the agent this process is done at build time – we collect arch, build info,
etc ( not necessarily OS) . Could do something similar for nanofi – and make
that information available...but I'm not sure if this ticket can pull that
information in.
In that case, generateVersion.sh from the root folder populates a class with
extensions and build info. Something like this could be done for MINIFICPP-622,
but not sure if that's the right case. This ticket is hoping that we can python
( instead of bash ) to send around that allow us to download what is needed and
bootstrap easily. Could probably do this through the existing bash script, but
I suspect more people would prefer python versus bash.
I don't want to assume systems have python installed for the build process, so
I would keep bash for generateVersion.sh OR you can supplement and have
generateVersion be a fallback if python doesn't exist....but you could
certainly use the same resulting information for MINIFICPP-622.
> Bootstrap agent through Python
> ------------------------------
>
> Key: MINIFICPP-672
> URL: https://issues.apache.org/jira/browse/MINIFICPP-672
> Project: NiFi MiNiFi C++
> Issue Type: New Feature
> Reporter: Mr TheSegfault
> Assignee: Arpad Boda
> Priority: Major
> Labels: nanofi
>
> Create library that will automatically bootstrap device/agent/lib. Users
> should be able to use our library standalone and download code to build or
> necessary artifacts ( preferred ). We can use the Apache hosted generic libs
> if needed. We may not have the necessary components – such as extension
> registry – so we might have to stub these interactions out.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
