Intellij: Support CLion 2018.3

Created on 27 Nov 2018  路  9Comments  路  Source: bazelbuild/intellij

I tried to bazel clean --expunge but I still get the same error

bazel build //clwb:clwb_bazel_zip --define=ij_product=clion-2018.3 | tee /tmp/clion23.txt
Loading: 
Loading: 0 packages loaded
INFO: Analysed target //clwb:clwb_bazel_zip (0 packages loaded).
INFO: Found 1 target...
[0 / 4] [-----] BazelWorkspaceStatusAction stable-status.txt
[1 / 5] Building clwb/libclwb_lib.jar (25 source files); 1s worker
ERROR: /Users/cmluciano/go/src/github.com/bazelbuild/intellij/clwb/BUILD:56:1: Building clwb/libclwb_lib.jar (25 source files) failed (Exit 1): java failed: error executing command 
  (cd /private/var/tmp/_bazel_cmluciano/9eff791ae49da2f4e88190b89a34526c/execroot/intellij_with_bazel && \
  exec env - \
    LC_CTYPE=en_US.UTF-8 \
  external/embedded_jdk/bin/java -Xbootclasspath/p:external/bazel_tools/third_party/java/jdk/langtools/javac-9+181-r4173-1.jar -jar external/bazel_tools/tools/jdk/JavaBuilder_deploy.jar @bazel-out/darwin-fastbuild/bin/clwb/libclwb_lib.jar-0.params)
clwb/src/com/google/idea/blaze/clwb/run/BlazeCidrLauncher.java:322: error: constructor CPPToolSet in class CPPToolSet cannot be applied to given types;
      super(Kind.MINGW, workingDirectory);
      ^
  required: Kind
  found: Kind,File
  reason: actual and formal argument lists differ in length
clwb/src/com/google/idea/blaze/clwb/run/BlazeCidrLauncher.java:357: error: cannot find symbol
        cl.setWorkDirectory(super.getHome());
                                 ^
  symbol: method getHome()
clwb/src/com/google/idea/blaze/clwb/run/BlazeCidrLauncher.java:381: error: cannot find symbol
        && !CidrGoogleTestUtil.findGoogleTestSymbolsForSuiteRandomly(getProject(), null, true)
                              ^
  symbol:   method findGoogleTestSymbolsForSuiteRandomly(Project,<null>,boolean)
  location: class CidrGoogleTestUtil
clwb/src/com/google/idea/blaze/clwb/run/test/BlazeCppTestLocator.java:102: error: cannot find symbol
      symbol = CidrGoogleTestUtil.findGoogleTestSymbol(project, suite, method);
                                 ^
  symbol:   method findGoogleTestSymbol(Project,String,String)
  location: class CidrGoogleTestUtil
clwb/src/com/google/idea/blaze/clwb/run/test/BlazeCppTestLocator.java:104: error: cannot find symbol
      symbol = CidrGoogleTestUtil.findGoogleTestInstantiationSymbol(project, suite, instantiation);
                                 ^
  symbol:   method findGoogleTestInstantiationSymbol(Project,String,String)
  location: class CidrGoogleTestUtil
clwb/src/com/google/idea/blaze/clwb/run/test/BlazeCppTestLocator.java:126: error: cannot find symbol
                && CidrGoogleTestUtil.isGoogleTestClass((OCStructSymbol) symbol, project);
                                     ^
  symbol:   method isGoogleTestClass(OCStructSymbol,Project)
  location: class CidrGoogleTestUtil
clwb/src/com/google/idea/blaze/clwb/run/test/BlazeCppTestLocator.java:134: error: cannot find symbol
        CidrGoogleTestUtil.findGoogleTestSymbolsForSuiteSorted(project, suite);
                          ^
  symbol:   method findGoogleTestSymbolsForSuiteSorted(Project,String)
  location: class CidrGoogleTestUtil
clwb/src/com/google/idea/blaze/clwb/run/test/GoogleTestLocation.java:87: error: cannot find symbol
        && CidrGoogleTestUtil.isGoogleTestClass(parentSymbol, project)) {
                             ^
  symbol:   method isGoogleTestClass(OCStructSymbol,Project)
  location: class CidrGoogleTestUtil
clwb/src/com/google/idea/blaze/clwb/run/test/GoogleTestLocation.java:105: error: cannot find symbol
              && CidrGoogleTestUtil.isGoogleTestClass((OCStructSymbol) owner, project)) {
                                   ^
  symbol:   method isGoogleTestClass(OCStructSymbol,Project)
  location: class CidrGoogleTestUtil
clwb/src/com/google/idea/blaze/clwb/run/test/GoogleTestLocation.java:121: error: cannot find symbol
      OCMacroCall gtestMacro = CidrGoogleTestUtil.findGoogleTestMacros(parent);
                                                 ^
  symbol:   method findGoogleTestMacros(PsiElement)
  location: class CidrGoogleTestUtil
clwb/src/com/google/idea/blaze/clwb/run/test/GoogleTestLocation.java:136: error: cannot find symbol
              CidrGoogleTestUtil.findGoogleTestSymbol(element.getProject(), suiteName, testName);
                                ^
  symbol:   method findGoogleTestSymbol(Project,String,String)
  location: class CidrGoogleTestUtil
clwb/src/com/google/idea/blaze/clwb/run/test/GoogleTestLocation.java:143: error: cannot find symbol
      Couple<String> suite = CidrGoogleTestUtil.extractFullSuiteNameFromMacro(parent);
                                               ^
  symbol:   method extractFullSuiteNameFromMacro(PsiElement)
  location: class CidrGoogleTestUtil
clwb/src/com/google/idea/blaze/clwb/run/test/GoogleTestLocation.java:146: error: cannot find symbol
            CidrGoogleTestUtil.findGoogleTestSymbolsForSuiteRandomly(
                              ^
  symbol:   method findGoogleTestSymbolsForSuiteRandomly(Project,String,boolean)
  location: class CidrGoogleTestUtil
clwb/src/com/google/idea/blaze/clwb/run/test/GoogleTestLocation.java:194: error: cannot find symbol
                      () -> CidrGoogleTestUtil.fileIncludesGoogleTest(file));
                                              ^
  symbol:   method fileIncludesGoogleTest(OCFile)
  location: class CidrGoogleTestUtil
clwb/src/com/google/idea/blaze/clwb/run/test/GoogleTestLocation.java:273: error: cannot find symbol
      if (CidrGoogleTestUtil.findGoogleTestMacros(macroCall) != null) {
                            ^
  symbol:   method findGoogleTestMacros(OCMacroCall)
  location: class CidrGoogleTestUtil
Target //clwb:clwb_bazel_zip failed to build
INFO: Elapsed time: 2.668s, Critical Path: 2.35s
INFO: 0 processes.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully

Most helpful comment

We're planning to support CLion 2018.3 in the next release, which should be uploaded in early January.

All 9 comments

Is there an ETA for releasing a CLion 2018.3 version, or any particular blocking issues?

Any updates?

We're planning to support CLion 2018.3 in the next release, which should be uploaded in early January.

@brendandouglas Should master be buildable for 2018.3 or has that update not been pushed to master yet?

I'd assume that master is not compatible yet, since its last update was 27 days ago.

You could try branch D8D8DDF3E27ABF305BC485BAEAFE48C9 though, it seems to be the current development version.

Is there an updated release date for this?

We're planning to upload the previous release, which supports 2018.3, early this week.

This is in the plugin repository now: https://plugins.jetbrains.com/plugin/9554-bazel

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ghost picture ghost  路  5Comments

mbravi picture mbravi  路  7Comments

lifeiteng picture lifeiteng  路  4Comments

Maririri picture Maririri  路  7Comments

shane13hsi picture shane13hsi  路  7Comments