I want to move away from the `autoconf` build that we are currently using. It has not been supported by the google test framework since version 1.4 of google test. I was trying to get the framework move over to github while making the smallest change to our scripts as possible. I was going to look into moving away from `autoconf` once I got the scripts pulling gtest from github. If I have to make larger changes in the commit, due to `autoreconf` not being available on OSx, I will. I was just hoping to make the change in small increments.
George -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Thiago Macieira Sent: Tuesday, November 22, 2016 3:55 PM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Assistance from someone building for OSx On ter?a-feira, 22 de novembro de 2016 15:51:54 PST Thiago Macieira wrote: > Projects that use GNU Autoconf or GNU Automake (e.g., the "Autotools") > need an extra step for releasing: their tarballs are not simple > snapshots of the Git repository. That extra step is what autoreconf does. > > Do I understand that Google Test does not have an official 1.7.0 > release? Is that the issue? Actually, their README explains that "Before settling on CMake, we have been providing hand-maintained build projects/scripts for Visual Studio, Xcode, and Autotools." So please don't use autoreconf. Instead, use CMake to build GTest. Requiring users to have it is acceptable. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
