Well done! I know this wasn’t easy.
> On Jan 31, 2017, at 3:41 PM, Harshad Deshmukh <hars...@cs.wisc.edu> wrote:
>
> Hello all,
>
> At long last, we have dealt with the third party issue. Some highlights:
>
> 1. Most of the libraries are now downloaded through a shell script.
>
> 2. The download links point to the release versions of the libraries.
>
> 3. After downloading the source code, we apply appropriate patches.
>
> Some libraries don't have an official release yet, so we will wait until they
> have a release. Until then, we have copied their entire source code to our
> third party directory. I have updated the build instructions based on these
> changes.
>
> Thanks Julian, Marc and Zuyu for your help.
>
> On 01/23/2017 09:57 PM, Jignesh Patel wrote:
>> Thanks Zuyu for the nice summary! For this release, I’d support going with
>> Harshad’s lead, which is a single script to download the third party
>> libraries.
>>
>> Dear Harshad: If your life is simpler with any of the other option (e.g. the
>> issue you are having with an old version of Ubuntu in Travis), when feel
>> free to go with the Mesos approach.
>>
>> Cheers,
>> Jignesh
>>
>> On 1/23/17, 12:26 AM, "Zuyu Zhang" <hit...@gmail.com on behalf of
>> z...@cs.wisc.edu> wrote:
>>
>> FYI, there are some Apache projects in C++ (
>> https://projects.apache.org/projects.html?language), and more in github (
>> https://github.com/apache?language=c%2B%2B), including incubator
>> projects.
>> I summaries how typically they deal with the third parties and the
>> release.
>> - Apache Mesos (https://github.com/apache/mesos) has most third
>> parties
>> in release tar balls, along with patches.
>> - Apache Kudu (https://github.com/apache/kudu) has multiple scripts to
>> download and build third parties.
>> - Apache NiFi - MiNiFi (https://github.com/apache/nifi-minifi-cpp)
>> includes the whole codebase of third parties.
>> Cheers,
>> Zuyu
>>
>>
>
> --
> Thanks,
> Harshad
>
