1.. _Windows_OS_ug:
2
3Windows\*
4=========
5
6This section uses <*tbb_install_dir*> to indicate the top-level
7installation directory. The following table describes the subdirectory
8structure for Windows\*, relative to <*tbb_install_dir*>.
9
10.. container:: tablenoborder
11
12
13   .. list-table::
14      :header-rows: 1
15
16      * - Item
17        - Location
18        - Environment Variable
19      * - Header files
20        - | ``include\oneapi\tbb.h``
21	  | ``include\oneapi\tbb\*.h``
22        - ``INCLUDE``
23      * - .lib files
24        - ``lib\<arch>\vc<vcversion>\<lib><variant><version>.lib``\
25        - ``LIB``
26      * - .dll files
27        - ``redist\<arch>\vc<vcversion>\<lib><variant><version>.dll``
28        - ``PATH``
29      * - .pdb files
30        - Same as corresponding ``.dll`` file.
31        - \
32
33where
34
35* ``<arch>`` - ``ia32`` or ``intel64``
36
37* ``<lib>`` - ``tbb``, ``tbbmalloc``, ``tbbmalloc_proxy`` or ``tbbbind``
38
39* ``<vcversion>``
40
41  - ``14`` - use for dynamic linkage  with the CRT
42
43  - ``14_uwp`` - use for Windows 10 Universal Windows applications
44
45  - ``14_uwd`` - use for Universal Windows Drivers
46
47  - ``_mt`` - use for static linkage with the CRT
48
49* ``<variant>`` - ``_debug`` or empty
50
51* ``<version>`` - binary version
52
53The last column shows which environment variables are used by the
54Microsoft\* Visual C++\* or Intel® C++ Compiler Classic or Intel® oneAPI DPC++/C++ Compiler to find these
55subdirectories.
56
57.. CAUTION::
58   Ensure that the relevant product directories are mentioned by the
59   environment variables; otherwise the compiler might not find the
60   required files.
61
62
63.. note::
64   Microsoft\* C/C++ run-time libraries come in static and dynamic
65   forms. Either can be used with oneTBB. Linking to the oneTBB library
66   is always dynamic.
67