On 16.03.2014, at 16:10, Darin Adler <[email protected]> wrote: > On Mar 16, 2014, at 3:01 AM, Patrick Gansterer <[email protected]> wrote: > >> a) Invoke make on DerivedSources.make and add a lot of custom target for >> that to CMake > > I’d like to see what this would look like before deciding it’s a bad idea.
In the easiest case it's a simple add_custom_command() in CMake for every "make <target>" call. > I don’t know what “a lot of custom targets” means and I’d like to see what > that would be like; we should simply invoke make unconditionally on > DerivedSources.make before doing the rest of CMake. This will remove all benefits CMake provides over simple make (platform abstraction, better dependency tracking, ...). For sure it's doable, but I'm not a big fan of kicking out CMake in favor of simple make. So once again the question: What are the blockers (beside that someone has to do the work) for migrating the remaining build systems to CMake? -- Patrick _______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
