Install Git On Mac
Monserrate Lares
Developers can access the power of both Windows and Linux at the same time on a Windows machine. The Windows Subsystem for Linux (WSL) lets developers install a Linux distribution (such as Ubuntu, OpenSUSE, Kali, Debian, Arch Linux, etc) and use Linux applications, utilities, and Bash command-line tools directly on Windows, unmodified, without the overhead of a traditional virtual machine or dualboot setup.
You can now install everything you need to run WSL with a single command. Open PowerShell or Windows Command Prompt in administrator mode by right-clicking and selecting "Run as administrator", enter the wsl --install command, then restart your machine.
The first time you launch a newly installed Linux distribution, a console window will open and you'll be asked to wait for files to de-compress and be stored on your machine. All future launches should take less than a second.
The above command only works if WSL is not installed at all, if you run wsl --install and see the WSL help text, please try running wsl --list --online to see a list of available distros and run wsl --install -d to install a distro.To uninstall WSL, see Uninstall legacy version of WSL or unregister or uninstall a Linux distribution.
If you want to install additional distributions from inside a Linux/Bash command line (rather than from PowerShell or Command Prompt), you must use .exe in the command: wsl.exe --install -d or to list available distributions: wsl.exe -l -o.
To install a Linux distribution that is not listed as available, you can import any Linux distribution using a TAR file. Or in some cases, as with Arch Linux, you can install using an .appx file. You can also create your own custom Linux distribution to use with WSL.
Once you have installed WSL, you will need to create a user account and password for your newly installed Linux distribution. See the Best practices for setting up a WSL development environment guide to learn more.
We recommend following our Best practices for setting up a WSL development environment guide for a step-by-step walk-through of how to set up a user name and password for your installed Linux distribution(s), using basic WSL commands, installing and customizing Windows Terminal, set up for Git version control, code editing and debugging using the VS Code remote server, good practices for file storage, setting up a database, mounting an external drive, setting up GPU acceleration, and more.
If you manually installed WSL prior to the wsl --install command being available, you may also need to enable the virtual machine optional component used by WSL 2 and install the kernel package if you haven't already done so.
WSL supports running as many different Linux distributions as you would like to install. This can include choosing distributions from the Microsoft Store, importing a custom distribution, or building your own custom distribution.
If a relative path is given it is interpreted relative to the valueof the CMAKE_INSTALL_PREFIX variable.The prefix can be relocated at install time using the DESTDIRmechanism explained in the CMAKE_INSTALL_PREFIX variabledocumentation.
As absolute paths are not supported by cpack installergenerators, it is preferable to use relative paths throughout.In particular, there is no need to make paths absolute by prependingCMAKE_INSTALL_PREFIX; this prefix is used by default ifthe DESTINATION is a relative path.
If this option is used multiple times in a single call, its listof permissions accumulates. If an install(TARGETS) calluses arguments, a separate list of permissionsis accumulated for each kind of artifact.
If this option is used multiple times in a single call, its listof configurations accumulates. If an install(TARGETS)call uses arguments, a separate list ofconfigurations is accumulated for each kind of artifact.
Specify an installation component name with which the install ruleis associated, such as Runtime or Development. Duringcomponent-specific installation only install rules associated withthe given component name will be executed. During a full installationall components are installed unless marked with EXCLUDE_FROM_ALL.If COMPONENT is not provided a default component "Unspecified" iscreated. The default component name may be controlled with theCMAKE_INSTALL_DEFAULT_COMPONENT_NAME variable.
New in version 3.11: Many of the install() variants implicitly create the directoriescontaining the installed files. IfCMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS is set, thesedirectories will be created with the permissions specified. Otherwise,they will be created according to the uname rules on Unix-like platforms.Windows platforms are unaffected.
Any PUBLIC_HEADER files associated with a library are installed inthe destination specified by the PUBLIC_HEADER argument on non-Appleplatforms. Rules defined by this argument are ignored for FRAMEWORKlibraries on Apple platforms because the associated files are installedinto the appropriate locations inside the framework folder. SeePUBLIC_HEADER for details.
File sets are defined by the target_sources(FILE_SET) command.If the file set exists and is PUBLIC or INTERFACE,any files in the set are installed under the destination (see below).The directory structure relative to the file set's base directories ispreserved. For example, a file added to the file set as/blah/include/myproj/here.h with a base directory /blah/includewould be installed to myproj/here.h below the destination.
Any module files from C++ modules from PUBLIC sources in a file set oftype CXX_MODULES will be installed to the given DESTINATION. Allmodules are placed directly in the destination as no directory structure isderived from the names of the modules. An empty DESTINATION may be usedto suppress installing these files (for use in generic code).
For regular executables, static libraries and shared libraries, theDESTINATION argument is not required. For these target types, whenDESTINATION is omitted, a default destination will be taken from theappropriate variable from GNUInstallDirs, or set to a built-indefault value if that variable is not defined. The same is true for filesets, and the public and private headers associated with the installedtargets through the PUBLIC_HEADER and PRIVATE_HEADERtarget properties. A destination must always be provided for module libraries,Apple bundles and frameworks. A destination can be omitted for interface andobject libraries, but they are handled differently (see the discussion of thistopic toward the end of this section).
For shared libraries on DLL platforms, if neither RUNTIME nor ARCHIVEdestinations are specified, both the RUNTIME and ARCHIVE components areinstalled to their default destinations. If either a RUNTIME or ARCHIVEdestination is specified, the component is installed to that destination, andthe other component is not installed. If both RUNTIME and ARCHIVEdestinations are specified, then both components are installed to theirrespective destinations.
Projects wishing to follow the common practice of installing headers into aproject-specific subdirectory may prefer using file sets with appropriatepaths and base directories. Otherwise, they must provide a DESTINATIONinstead of being able to rely on the above (see next example below).
To make packages compliant with distribution filesystem layout policies, ifprojects must specify a DESTINATION, it is recommended that they use apath that begins with the appropriate GNUInstallDirs variable.This allows package maintainers to control the install destination by settingthe appropriate cache variables. The following example shows a static librarybeing installed to the default destination provided byGNUInstallDirs, but with its headers installed to a project-specificsubdirectory without using file sets:
where lib.so.1 is the soname of the library and lib.sois a "namelink" allowing linkers to find the library when given-l. The NAMELINK_COMPONENT option is similar to theCOMPONENT option, but it changes the installation component of a sharedlibrary namelink if one is generated. If not specified, this defaults to thevalue of COMPONENT. It is an error to use this parameter outside of aLIBRARY block.
This option causes the installation of only the namelink when a librarytarget is installed. On platforms where versioned shared libraries do nothave namelinks or when a library is not versioned, the NAMELINK_ONLYoption installs nothing. It is an error to use this parameter outside of aLIBRARY block.
Similar to NAMELINK_ONLY, but it has the opposite effect: it causes theinstallation of library files other than the namelink when a library targetis installed. When neither NAMELINK_ONLY or NAMELINK_SKIP are given,both portions are installed. On platforms where versioned shared librariesdo not have symlinks or when a library is not versioned, NAMELINK_SKIPinstalls the library. It is an error to use this parameter outside of aLIBRARY block.
This option associates the installed target files with an export called. It must appear before any target options.To actually install the export file itself, callinstall(EXPORT), documented below.See documentation of the EXPORT_NAME target property to changethe name of the exported target.
This option specifies a list of directories which will be added to theINTERFACE_INCLUDE_DIRECTORIES target property of the when exported by the install(EXPORT) command.If a relative path is specified, it is treated as relative to the$.
This option causes all runtime dependencies of installed executable, sharedlibrary, and module targets to be added to the specified runtime dependencyset. This set can then be installed with aninstall(RUNTIME_DEPENDENCY_SET) command.
This option causes all runtime dependencies of installed executable, sharedlibrary, and module targets to be installed along with the targetsthemselves. The RUNTIME, LIBRARY, FRAMEWORK, and genericarguments are used to determine the properties (DESTINATION,COMPONENT, etc.) of the installation of these dependencies.
760c119bf3