Thread
#multiplatform
    natpryce

    natpryce

    4 years ago
    But I find that for libraries, Gradle will still be parsing the build configuration when the Make build has finished.
    gildor

    gildor

    4 years ago
    Make sense to profile configuration step, maybe there is some problem with one of plugins
    natpryce

    natpryce

    4 years ago
    I don’t need to because Make is already fast.
    gildor

    gildor

    4 years ago
    And also not compatible with Idea and Kotlin
    I just want to say, that maybe there is just some performance problem that can be solved, instead of writing manual integration with CLI tools
    natpryce

    natpryce

    4 years ago
    That sounds like Yak shaving
    Writing Make rules is easy
    Writing Gradle and debugging its performance problems is not
    Especially given the buggy caching
    and patchy IntelliJ support for editing Gradle files
    gildor

    gildor

    4 years ago
    Writing Gradle and debugging its performance problems is not
    is not a big problem if you know what to do, if it’s easy to write everything manually, why not
    natpryce

    natpryce

    4 years ago
    But it’s not something that one should need to do. Profiling my app? Sure. Profiling Gradle’s own parsing of its own configuration files? Yak shaving.
    gildor

    gildor

    4 years ago
    parsing of its own configuration files
    No, of course not parsing. Gradle compiles all build scripts only once and cache them, I don’t think that this is your problem. Configuration should be pretty fast even for multimodule project with modern Gradle, but sometimes bad plugin or wrong configuration can broke it. Sometimes just run Gradle builds scan to find problem