lacasseio
commented
5 years ago At the moment, we don't allow mixing cpp-library and cpp-application into the same project to create multi-components project like in the software model. The reason being it goes against the pattern expressed everywhere else in Gradle. Multiple components in a project will be expressed in a more focused way like JNI project or multiple test suite per project.
For your specific scenario, you could model the structure of the project as a setting plugin that simplifies the project creation. Given the pattern used throughout the Poco organization is pretty clear, you should be able to model it so that you can use a custom DSL that does the right configuration to keep the organization of the Gradle logic concise. For example, you could have the following settings.gradle. Keep in mind the code could be moved to buildSrc and apply the plugin.
import javax.inject.Inject
class PocoLibraryProject {
private final String path
final List<String> samples = []
@Inject
PocoLibraryProject(String path) {
this.path = path
}
void sample(String name) {
samples.add(name)
}
}
class PocoLayoutExtension {
private final Settings settings
private final ObjectFactory objectFactory
@Inject
PocoLayoutExtension(ObjectFactory objectFactory, Settings settings) {
this.objectFactory = objectFactory
this.settings = settings
}
void library(String path, Action<? extends PocoLibraryProject> action = null) {
settings.include(path)
if (action != null) {
def spec = objectFactory.newInstance(PocoLibraryProject, path)
action.execute(spec)
for (String it : spec.samples) {
String projectPath = "${path}:${it}"
settings.include(projectPath)
settings.project(":${projectPath}").projectDir = new File(settings.rootDir, path.replace(":", "/") + "/samples/${it}")
settings.gradle.rootProject { proj ->
proj.project(":${projectPath}") {
// TODO: Configure convention for the sample such as:
// - applying `cpp-application`
// - adding a dependency to the library
}
}
}
// TODO: Handle the test case in a similar way
}
}
}
class PocoProjectLayoutPlugin implements Plugin<Settings> {
private final ObjectFactory objectFactory
@Inject
PocoProjectLayoutPlugin(ObjectFactory objectFactory) {
this.objectFactory = objectFactory
}
void apply(Settings settings) {
def subprojects = objectFactory.newInstance(PocoLayoutExtension, settings)
settings.extensions.add("subprojects", subprojects)
}
}
apply plugin: PocoProjectLayoutPlugin
subprojects {
library("Foundation") {
sample("ActiveMethod")
sample("Activity")
//...
}
library("SQL") {
sample("Binding")
sample("RecordSet")
//...
}
library("SQL:MySQL")
}
zosrothko
When building a multi modules project, that contains both cpp library and cpp-application, one needs to specify global options/parameters/tasks for some or all submodules. Below is the organisation of a the Poco Foundation module
Expected Behavior
A working build as with the Rule based plugins
Current Behavior
Build file 'Z:\git\gradle-bug\build.gradle' line: 2
Context
Cannot use the new cpp-plugins
Steps to Reproduce (for bugs)
build the following build.gradle script
Your Environment
Gradle 5.1.1
Build time: 2019-01-10 23:05:02 UTC Revision: 3c9abb645fb83932c44e8610642393ad62116807
Kotlin DSL: 1.1.1 Kotlin: 1.3.11 Groovy: 2.5.4 Ant: Apache Ant(TM) version 1.9.13 compiled on July 10 2018 JVM: 1.8.0_181 (Oracle Corporation 25.181-b13) OS: Windows 10 10.0 amd64