Go to the Microsoft Visual C++ downloads,.The redistributable comes with Visual Studio 2019 but can be installed separately: Starting with the TensorFlow 2.1.0 version, the msvcp140_1.dllįile is required from this package (which may not be provided from older redistributable packages).
Install the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017,Īnd 2019.
Install using the Homebrew package manager: /usr/bin/ruby -e "$(curl -fsSL )" export PATH="/usr/local/opt/python/libexec/bin:$PATH" # if you are on macOS 10.12 (Sierra) use `export PATH="/usr/local/bin:/usr/local/sbin:$PATH"` brew update brew install python # Python 3 Windows
Ubuntu sudo apt update sudo apt install python3-dev python3-pip python3-venv macOS If these packages are already installed, skip to the next step. Requires Python 3.7-3.9, and pip >= 19.0 python3 -version pip3 -version Install the Python development environment on your systemĬheck if your Python environment is already configured: Read the GPU support guide to set up a CUDA®-enabled GPU card on Ubuntu or Windows.ġ.Starting with TensorFlow 1.6, binaries use AVX instructions which may not run on older CPUs.Note: Installing TensorFlow 2 requires a newer version of pip. GPU support requires a CUDA®-enabled card (Ubuntu and Windows).Redistributable for Visual Studio 2015, 20 macOS 10.12.6 (Sierra) or later (64-bit) (no GPU support).pip 19.0 or later (requires manylinux2010 support).Python 3.8 support requires TensorFlow 2.2 or later.Python 3.9 support requires TensorFlow 2.5 or later.tensorflow-gpu=1.15 -Release with GPU support (Ubuntu and Windows).Ubuntu and Windows include GPU support.įor TensorFlow 1.x, CPU and GPU packages are separate: tensorflow -Latest stable release with CPU and GPU support (Ubuntu and Windows).To configure the web server you must verify the MIME types used for the file types in use. Typically, File Transfer Protocol (FTP) or SSH File Transfer Protocol (SFTP) are used to upload the files, but there are other publishing methods like MSDeploy, SSH, or Blob storage, depending on your web provider. Publishing to a web location requires access to publish content to the web server, making sure the final URL matches the Installation URL defined in the wizard (see Step 6 for details). The wizard will generate the files in the correct location, and users will get both the app and future updates from the same path. If you want to publish your packages over Universal Naming Convention (UNC) shared folders, configure the app package output folder and the Installation URL (see Step 6 for details) to the same path. To make the application available the generated files must be published to the location specified: Publish to shared folders (UNC) The output folder includes all the files needed to sideload the app, including an HTML page that can be used to promote your app. When your app has been successfully packaged, a dialog will display the location of the output folder containing your app package. Here, you can specify the Installation URL and the frequency of update checks. If you checked Enable automatic updates in Step 2, the Configure Update Settings dialog will appear. If you're unsure which architecture(s) to choose, or want to learn more about which architectures are used by various devices, see App package architectures.Ĭonfigure any additional details, such as version numbering or the package output location. If you select a bundle it will generate a single installer, however if you don't want a bundle and prefer one package per architecture you will also get one installer file per architecture. The Select and Configure Packages dialog allows you to select the supported architecture configurations. and Enable automatic updatesĮnable automatic updates is enabled only if the project's TargetPlatformMinVersion is set to the correct version of Windows 10. Select I want to create packages for sideloading. Right-click the project and choose Store -> Create App Packages. To do that, use the Create App Packages wizard in Visual Studio with the following steps. To distribute an app via sideloading, you must create an app package (.appx/.msix) or app bundle (.appxbundle/.msixbundle) and publish it in a shared location.
The app installer file is only generated when the TargetPlatformMinVersion is Windows 10, Version 1803 or greater.