Linux build - cmake generated Makefile vs checked-in Makefile?

[steve.ni...@gmail.com]

I'd like to understand the difference between the checked in Makefile and the cmake generated Makefile on Linux.

On Windows, we must use cmake and then do a build with visualstudio. I understand the reasons for using cmake.

On Linux, it seems there are two options. 1) we could use the Makefile checked into the project. 2) we could also use cmake and then build with the generated Makefile. Both seem to work ok although binaries are put into different directories.

What are the build differences when using the checked in Makefile vs the cmake generated Makefile for the linux build?

Why provide both?

Which approach is recommended?

Thanks,

Steve Nikopoulos

[Nicolas Noble]

The short answer to "why provide both" could be resumed to "so that people have options". There are pros and cons to each build mechanism that is, and cmake doesn't necessarily fit everyone's needs. There's consumers of the Makefile that is, such as the Ruby or the Python build, which can't call cmake beforehand. That's a byproduct of having to deal with many platforms and languages.

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+u...@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/78a74796-d045-4a57-813a-ea4f6780e2a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.