On 16/04/2013, at 9:38 PM, Peter Walker <peter.wal...@gradleware.com> wrote:
> Lets consider this in more detail: > "- The source files and the header files of a C++ compile task. I might > implement this task so that it can deal with changes to source files but not > header files. If a source file changes, I can recompile the output file for > this source file. If a header file changes, I will recompile everything." > I'm assuming that me are compiling multiple C++ source files into multiple > object files with one task. > We need to map many headers files and one C++ source file to one object > file. Have we thought about a mechanism to persist the relationship between > many header files, a source files and an object file? Yes, we're going to need something like this. To start with, it will be the task's problem to solve, but at some point it would be useful to expose something to help with this. > Is it possible to start exploring native C++ compilation to learn more about > the best API and supporting infra? Yes. I think we're spinning a bit without some real use cases to solve. Some candidates I'm thinking of: make the c++ compilation task incremental wrt source files (but not header files, that's for later), make our DSL meta-data task incremental, and probably make the java compilation task incremental wrt compile classpath (but not source files). -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com Join us at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: http://www.gradlesummit.com
