Quantcast
Channel: Gradle Forums - Latest posts
Viewing all articles
Browse latest Browse all 19888

My plugins for C++ (integration with Eclipse/QtCreator/NetBeans/KDevelop)

$
0
0

The new version 1.0 of the plugin cpp-build-tuner was released.

  1. The plugin configuration block was implemented:

    buildTuner {
    
     lto = false
    
     gtest = '1.8.1'
    
     libraries {
         common = ['cutils.lib']
         windows = ['ole32', 'user32']
         linux = ['pthread', 'z']
     }
    
     libDirs.common = ['../build/debug', '../release']
    

    }

lto (boolean) - disable or enable LTO (link time optimizations) on Release. By default LTO is enabled.

gtest (string) - the version of Google Test for test binary. At the moment only version 1.8.1 for GCC, MinGW-W64, and MSVC is supported.

libraries (container) - the list of libraries for the linker. The field has three parameters (list of strings) inside: common - libraries which will be used on any platform, windows - only on Windows and linux - only on Linux.

libDirs (container) - the list of directories on the local file system to search the linker libraries. Inside has the same platform-specific structure as the libraries container (see above).

  1. Run application ability for cpp-application was implemented. For application projects a plugin adds tasks: run, runDebug (same as run) and runRelease. Those tasks depends on assemble, assembleDebug and assembleRelease correspondently.
    Also, you can pass command-line arguments as in “Java Application plugin”:
    gradle run --args="arg1 arg2 ...".

Viewing all articles
Browse latest Browse all 19888

Trending Articles