Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. Paths in conan_paths.cmake changed in conan 2.1.0, results cmake error when cmake project in QtCreator
Forum Updated to NodeBB v4.3 + New Features

Paths in conan_paths.cmake changed in conan 2.1.0, results cmake error when cmake project in QtCreator

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
8 Posts 3 Posters 760 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • CalciferC Offline
    CalciferC Offline
    Calcifer
    wrote on last edited by Calcifer
    #1

    This problem do not exist in conan 2.0.9,
    but in conan 2.1.0, '/' changes to '\'

    345fb72d-879e-496e-a7b8-26e1c53e76e9-image.png

    General Messages in QtCreator 12.0.2:
    [cmake] CMake Error at D:/build-Repos-Desktop_Qt_6_6_2_MSVC2019_64bit-Debug/conan-dependencies/conan_paths.cmake:2 (list):
    [cmake] Syntax error in cmake code at
    [cmake]
    [cmake] D:/build-Repos-Desktop_Qt_6_6_2_MSVC2019_64bit-Debug/conan-dependencies/conan_paths.cmake:2
    [cmake]
    [cmake] when parsing string
    [cmake]
    [cmake] D:\build-Repos-Desktop_Qt_6_6_2_MSVC2019_64bit-Debug\conan-dependencies\build\conan
    [cmake]
    [cmake] Invalid character escape '\S'.
    [cmake] Call Stack (most recent call first):
    [cmake] D:/build-Repos-Desktop_Qt_6_6_2_MSVC2019_64bit-Debug/.qtc/package-manager/auto-setup.cmake:188 (include)
    [cmake] D:/build-Repos-Desktop_Qt_6_6_2_MSVC2019_64bit-Debug/.qtc/package-manager/auto-setup.cmake:192 (qtc_auto_setup_conan)
    [cmake] CMakeLists.txt:31 (project)
    [cmake]
    [cmake]
    [cmake] -- Configuring incomplete, errors occurred!
    [cmake]
    [cmake] CMake process exited with exit code 1.
    [cmake]
    [cmake] Elapsed time: 00:03.

    change '\' to '/', then do cmake can fix this problem.

    This is a problem of conan or cmake-conan?

    Thanks in advance.

    cristian-adamC 1 Reply Last reply
    0
    • CalciferC Calcifer

      This problem do not exist in conan 2.0.9,
      but in conan 2.1.0, '/' changes to '\'

      345fb72d-879e-496e-a7b8-26e1c53e76e9-image.png

      General Messages in QtCreator 12.0.2:
      [cmake] CMake Error at D:/build-Repos-Desktop_Qt_6_6_2_MSVC2019_64bit-Debug/conan-dependencies/conan_paths.cmake:2 (list):
      [cmake] Syntax error in cmake code at
      [cmake]
      [cmake] D:/build-Repos-Desktop_Qt_6_6_2_MSVC2019_64bit-Debug/conan-dependencies/conan_paths.cmake:2
      [cmake]
      [cmake] when parsing string
      [cmake]
      [cmake] D:\build-Repos-Desktop_Qt_6_6_2_MSVC2019_64bit-Debug\conan-dependencies\build\conan
      [cmake]
      [cmake] Invalid character escape '\S'.
      [cmake] Call Stack (most recent call first):
      [cmake] D:/build-Repos-Desktop_Qt_6_6_2_MSVC2019_64bit-Debug/.qtc/package-manager/auto-setup.cmake:188 (include)
      [cmake] D:/build-Repos-Desktop_Qt_6_6_2_MSVC2019_64bit-Debug/.qtc/package-manager/auto-setup.cmake:192 (qtc_auto_setup_conan)
      [cmake] CMakeLists.txt:31 (project)
      [cmake]
      [cmake]
      [cmake] -- Configuring incomplete, errors occurred!
      [cmake]
      [cmake] CMake process exited with exit code 1.
      [cmake]
      [cmake] Elapsed time: 00:03.

      change '\' to '/', then do cmake can fix this problem.

      This is a problem of conan or cmake-conan?

      Thanks in advance.

      cristian-adamC Offline
      cristian-adamC Offline
      cristian-adam
      wrote on last edited by
      #2

      This was fixed in Qt Creator 13 by doing the \ to / conversion on Qt Creator side. See https://bugreports.qt.io/browse/QTCREATORBUG-30326

      It's a one liner, but if you use Qt Creator 12 you'll have to patch your Qt Creator installation like in https://codereview.qt-project.org/c/qt-creator/qt-creator/+/538496

      CalciferC I 2 Replies Last reply
      1
      • cristian-adamC cristian-adam

        This was fixed in Qt Creator 13 by doing the \ to / conversion on Qt Creator side. See https://bugreports.qt.io/browse/QTCREATORBUG-30326

        It's a one liner, but if you use Qt Creator 12 you'll have to patch your Qt Creator installation like in https://codereview.qt-project.org/c/qt-creator/qt-creator/+/538496

        CalciferC Offline
        CalciferC Offline
        Calcifer
        wrote on last edited by
        #3

        @cristian-adam Thanks for help!

        1 Reply Last reply
        1
        • cristian-adamC cristian-adam

          This was fixed in Qt Creator 13 by doing the \ to / conversion on Qt Creator side. See https://bugreports.qt.io/browse/QTCREATORBUG-30326

          It's a one liner, but if you use Qt Creator 12 you'll have to patch your Qt Creator installation like in https://codereview.qt-project.org/c/qt-creator/qt-creator/+/538496

          I Offline
          I Offline
          iexavl
          wrote on last edited by iexavl
          #4

          @cristian-adam I am currently on Qt Creator 13.0.0 and I am getting the same issue

          cristian-adamC 1 Reply Last reply
          0
          • I iexavl

            @cristian-adam I am currently on Qt Creator 13.0.0 and I am getting the same issue

            cristian-adamC Offline
            cristian-adamC Offline
            cristian-adam
            wrote on last edited by
            #5

            @iexavl The update code is there. Qt Creator 13 shouldn't have this issue.

            Make sure that you delete your build directory and try again. If that doesn't work, then debug the <build-dir>/.qtc/package-manager/auto-setup.cmake.

            It's not rocket science 😀

            I 1 Reply Last reply
            0
            • cristian-adamC cristian-adam

              @iexavl The update code is there. Qt Creator 13 shouldn't have this issue.

              Make sure that you delete your build directory and try again. If that doesn't work, then debug the <build-dir>/.qtc/package-manager/auto-setup.cmake.

              It's not rocket science 😀

              I Offline
              I Offline
              iexavl
              wrote on last edited by
              #6

              @cristian-adam Hail the savior. I hit clean under the build tab in Qt Creator and thought that would be enough, and it possibly would be, but I am connected remotely to another computer with remote desktop on windows, and there was apparently some sort of permission issue when attempting to touch anything in that folder. Never had that happen before and I am just beyond delighted it happened at the exact fateful place where I would waste 3 hours trying to figure out what's going on.

              cristian-adamC 1 Reply Last reply
              1
              • I iexavl

                @cristian-adam Hail the savior. I hit clean under the build tab in Qt Creator and thought that would be enough, and it possibly would be, but I am connected remotely to another computer with remote desktop on windows, and there was apparently some sort of permission issue when attempting to touch anything in that folder. Never had that happen before and I am just beyond delighted it happened at the exact fateful place where I would waste 3 hours trying to figure out what's going on.

                cristian-adamC Offline
                cristian-adamC Offline
                cristian-adam
                wrote on last edited by
                #7

                @iexavl right. I guess the <build-dir>/.qtc/package-manager/auto-setup.cmake could be recreated when doing a clean, so that an update could be delivered.

                Would you make a suggestion at https://bugreports.qt.io/secure/CreateIssue.jspa?pid=10512 ?

                I 1 Reply Last reply
                0
                • cristian-adamC cristian-adam

                  @iexavl right. I guess the <build-dir>/.qtc/package-manager/auto-setup.cmake could be recreated when doing a clean, so that an update could be delivered.

                  Would you make a suggestion at https://bugreports.qt.io/secure/CreateIssue.jspa?pid=10512 ?

                  I Offline
                  I Offline
                  iexavl
                  wrote on last edited by
                  #8

                  @cristian-adam Ah. So that was the problem than. I suppose I really should have just taken a look there. I made the suggestion, thanks for the help.

                  1 Reply Last reply
                  1

                  • Login

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Users
                  • Groups
                  • Search
                  • Get Qt Extensions
                  • Unsolved