search

gradle / gradle-native

The home of Gradle's support for natively compiled languages
https://blog.gradle.org/introducing-the-new-cpp-plugins
Apache License 2.0
92 stars 8 forks source link

Allow source files with any extension to be added to a C++ or Swift component #450

Open adammurdoch opened 6 years ago

adammurdoch commented 6 years ago

Currently, the C++ and Swift plugins filter source files using a hard-coded set of extensions. When a source files does not have one of these extensions, it is ignored even when added explicitly.

The solution should allow a plugin to add a directory containing source files with any explicitly defined extensions as a convention.

big-guy commented 6 years ago

Is this just a shorter-term solution for https://github.com/gradle/gradle-native/issues/105?

adammurdoch commented 6 years ago

I think it's independent of #105. We could do #105 and still have hard-coded extensions, or we could have an open set of extensions and not do #105. If we had done #105, then that structure would be a natural home for the solution to this issue, to allow it to be reused for all languages and header directory sets.