While I appreciate enthusiasm to add new apps to the repository, we should convert all new apps to cmake right away. Otherwise we just keep digging ourselves a deeper hole with cmake conversions.
Thoughts?
Darrell
On 02/26/2014 05:15 PM, Darrell wrote:
While I appreciate enthusiasm to add new apps to the repository, we should convert all new apps to cmake right away. Otherwise we just keep digging ourselves a deeper hole with cmake conversions.
Thoughts?
Darrell
After 4 hours figuring out how to set a GD preprocessor flag, unless we have cmake experts with free time on their hands, I don't see it being realistic from a manpower standpoint. I wish it was all cmake, and the TDE tools have gotten much better, but I don't have the days to commit to converting even simple builds to cmake. Hopefully others do.
cmake would be the preferred choice, but if not possible autotools will do. Of course it will require more cmake conversion time later, but better an app with autotools than no app at all. Just my 2 cents.
Michele
On Thursday 27 of February 2014 02:54:45 Michele Calgaro wrote:
cmake would be the preferred choice, but if not possible autotools will do. Of course it will require more cmake conversion time later, but better an app with autotools than no app at all. Just my 2 cents.
Michele
First, I agree that it is better to have an application with autotools, than not having application.
Second, because the integration of applications into GIT always start incorporating original source code, converting to cmake will always be a subsequent patch. So it's just a matter of how long after the initial integration application into GIT will be pushed patch to convert to cmake.
-
Darrell -
David C. Rankin -
Michele Calgaro -
Slávek Banko