Hi Chris It is still a CMake project and there are instructions in the README for building with CMake.
The top level Makefile is used to aid docker builds, formatting and testing. Regards Kealan [image: MIRACL Logo] <http://www.miracl.com/?utm_campaign=Email%20Signature&utm_source=email&utm_content=email_miracl_logo> *Try MIRACL Trust® in Five Minutes* *Download Guide* <http://www.miracl.com/try-miracl-trust-in-5-minutes?utm_campaign=Email%20Signature&utm_source=email&utm_content=email_download_guide> | *Read FAQs* <http://www.miracl.com/faqs-miracl-trust?utm_campaign=Email%20Signature&utm_source=email&utm_content=email_read_faqs> On Mon, Oct 9, 2017 at 1:54 PM, Chris Richardson <[email protected]> wrote: > It looks like the build system is diverging in this project ( > https://github.com/milagro-crypto/milagro-crypto-c) - initially (and > according to the documentation) it is a CMake project, but it looks like an > autotools/Makefile based build system is also present and being maintained. > > This situation generally results in poor quality in the build system, > particularly when it comes to portability. Already it can be seen from the > commit log that some features have been implemented in CMake and not in the > Makefile, and visa versa. > > I'd like to suggest that the Makefile and config.mk be removed from the > source and that the functionality should exist in the CMake script only. > > Regards > > -- > > *Chris Richardson*, System Architect > [email protected] > > > *FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller, Norwaywww.fourc.eu > <http://www.fourc.eu/>* > > *Follow us on LinkedIn <http://bit.ly/fourcli>, Facebook > <http://bit.ly/fourcfb>, Google+ <http://bit.ly/fourcgp> and Twitter > <http://bit.ly/fourctw>!* >
