[
https://issues.apache.org/jira/browse/MINIFI-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556554#comment-15556554
]
ASF GitHub Bot commented on MINIFI-34:
--------------------------------------
Github user trixpan commented on the issue:
https://github.com/apache/nifi-minifi-cpp/pull/18
@apiri indeed. solving the INTERFACE was a matter of using what seems to be
called the "infamous `dummy.cpp `".
Good news is that this should be working now (it works locally).
once you confirm travis-ci precise is working, I will be happy to proceed
with enabling trusty tahr again and setup a docker based test to ease cross
platform development.
Major changes of the last commit
- the CMake has been adjusted to compile against existing libuuid
- travis adjusted to use whatever version of libboost-all-dev is available
> Establish build system for MiNiFi C++
> -------------------------------------
>
> Key: MINIFI-34
> URL: https://issues.apache.org/jira/browse/MINIFI-34
> Project: Apache NiFi MiNiFi
> Issue Type: Task
> Components: Build
> Reporter: Aldrin Piri
> Assignee: Aldrin Piri
> Labels: C++, native
>
> Given the need to run on varied and disparate environments, a build procedure
> is imperative in ensuring consistent project compilation and in assisting
> folks in contributing. There are a few tools that go beyond a Makefile to
> aid in this process. Among these are Autotools, CMake, and Scons
> Key things to keep in mind are the need to support deployment and development
> in Windows, Linux and OS X. This likely precludes Autotools without
> significant effort to work in Windows environments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
