error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools

[Bernardo-Rufino]

Hi there,

I'm trying to install pytimbr, but having issues like below.

error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/

I've already installed Microsoft Visual C++ 14.0 or greater:

The complete log after pip install git+https://github.com/WPSemantix/timbr_python_connector (using pip install pytimbrresults in the same error):

  Cloning https://github.com/WPSemantix/timbr_python_connector to c:\users\c352308\appdata\local\temp\pip-req-build-iycfdx_5
  Running command git clone --filter=blob:none --quiet https://github.com/WPSemantix/timbr_python_connector 'C:\Users\C352308\AppData\Local\Temp\pip-req-build-iycfdx_5'
  Resolved https://github.com/WPSemantix/timbr_python_connector to commit cc823a8035804b1fb1d0cc4ca5ae58625ea8c1d0
  Preparing metadata (setup.py) ... done
Collecting JayDeBeApi==1.2.3 (from pytimbr==1.0.2)
  Using cached JayDeBeApi-1.2.3-py3-none-any.whl.metadata (10 kB)
Collecting JPype1==1.4.1 (from pytimbr==1.0.2)
  Using cached JPype1-1.4.1.tar.gz (797 kB)
  Preparing metadata (setup.py) ... done
Requirement already satisfied: packaging in c:\users\c352308\appdata\local\miniconda3\envs\timbr\lib\site-packages (from JPype1==1.4.1->pytimbr==1.0.2) (23.2)
Using cached JayDeBeApi-1.2.3-py3-none-any.whl (26 kB)
Building wheels for collected packages: pytimbr, JPype1
  Building wheel for pytimbr (setup.py) ... done
  Created wheel for pytimbr: filename=pytimbr-1.0.2-py3-none-any.whl size=96788467 sha256=9759bfbab8c6f1db7d05bd74b2fe2bc02c678421373774afc7c8a93cb850b28e
  Stored in directory: C:\Users\C352308\AppData\Local\Temp\pip-ephem-wheel-cache-ivouxsid\wheels\48\24\28\d1b9181f609cfa5cf446435ce078bbfa00572f8f2609df375d
  Building wheel for JPype1 (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [50 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build\lib.win-amd64-cpython-312
      creating build\lib.win-amd64-cpython-312\jpype
      copying jpype\beans.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\config.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\dbapi2.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\imports.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\nio.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\pickle.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\protocol.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\types.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_classpath.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_core.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_gui.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jarray.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jclass.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jcollection.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jcustomizer.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jexception.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jinit.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jio.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jmethod.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jobject.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jpackage.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jproxy.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jstring.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jthread.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jvmfinder.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_pykeywords.py -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\__init__.py -> build\lib.win-amd64-cpython-312\jpype
      creating build\lib.win-amd64-cpython-312\jpype\_pyinstaller
      copying jpype\_pyinstaller\entry_points.py -> build\lib.win-amd64-cpython-312\jpype\_pyinstaller
      copying jpype\_pyinstaller\example.py -> build\lib.win-amd64-cpython-312\jpype\_pyinstaller
      copying jpype\_pyinstaller\hook-jpype.py -> build\lib.win-amd64-cpython-312\jpype\_pyinstaller
      copying jpype\_pyinstaller\test_jpype_pyinstaller.py -> build\lib.win-amd64-cpython-312\jpype\_pyinstaller
      copying jpype\_core.pyi -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jcollection.pyi -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jio.pyi -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jstring.pyi -> build\lib.win-amd64-cpython-312\jpype
      copying jpype\_jthread.pyi -> build\lib.win-amd64-cpython-312\jpype
      running build_ext
      Call build extensions
      Using Jar cache
      copying native\jars\org.jpype.jar -> build\lib.win-amd64-cpython-312
      Call build ext
      building '_jpype' extension
      error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for JPype1
  Running setup.py clean for JPype1
Successfully built pytimbr
Failed to build JPype1
ERROR: Could not build wheels for JPype1, which is required to install pyproject.toml-based projects```

[amitwps]

@Bernardo-Rufino can you share the specific version of your visual-cpp-build-tools, it appears at the end of the package name:

[Bernardo-Rufino]

@amitwps , here it is (you could see on the first screenshot that I've provided, on the last column):

[amitwps]

@Bernardo-Rufino
Can you try modifying your "Visual Studio Build Tools" - enable all packages and try again?

[Bernardo-Rufino]

@amitwps , fixed with a fresh install like your screen shot and with a few connection tweaks as we talked.

Thanks a lot!