Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update installation-windows-env.rst #11

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Update installation-windows-env.rst #11

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
bb801b5
Update installation-windows-env.rst
HiteshDhola Apr 28, 2021
ebc409e
Update installation-windows-env.rst
HiteshDhola Apr 28, 2021
2d8f7fa
Update installation-windows-env.rst
HiteshDhola Apr 28, 2021
76159fd
Update installation-windows-env.rst
HiteshDhola Apr 28, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions getting-started/installation-windows-env.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,12 +13,12 @@ Required settings for Path
^^^^^^^^^^^^^^^^^^^^^^^^^^
The way you are building your binaries determines which paths have to be added to the Path variable.

* Static builds
* Static builds (For more Details see `Product Static Build <https://docs.epics-controls.org/en/latest/appdevguide/EPICSBuildFacility.html#product-static-builds>`_.)

1. Add the EPICS Base binary directory for your target to be able to call the EPICS command line tools without specifying their fully qualified path.
1. Add the EPICS Base binary directory ("...\\base-x.x.x\\bin\\<target-arch>") for your target to be able to call the EPICS command line tools without specifying their fully qualified path.

This setting is for convenience only and not mandatory. Your IOCs run without it.

* Dynamic (DLL) builds

1. Add the EPICS Base binary directory for your target so that the EPICS DLLs are found and you can use the CLI tools without specifying the path.
Expand All @@ -44,11 +44,11 @@ If you have Administrator rights and want to do it globally, you can also select

1. Select ``Advance`` tab, navigate to ``Environment Variables`` button. That should open editable tables of settings for Windows Environment.
2. Select ``User Variable for 'user'`` option, press NEW
3. Add EPICS BASE path here. In ``Variable Name``, put "EPICS_BASE". For ``Variable Value``, enter the location of your EPICS Base installation, e.g., "C:\\msys64\\home\\'user'\\base-R7.0.4.1"
3. Add EPICS BASE path here. In ``Variable Name``, put "EPICS_BASE". For ``Variable Value``, enter the location of your EPICS Base installation, e.g., "C:\\msys64\\home\\ 'user'\\base-R7.0.4.1"
4. Set the host architecture. In ``Variable Name``, put "EPICS_HOST_ARCH". For ``Variable Value``, put "windows-x64-mingw" or "windows-x64" (depending on your selection of compilers).
5. Navigate to the variable called ``Path``. Press Edit.
6. If you are using the MinGW compilers and dynamic (DLL) linking, add the path for the MinGW64 DLLs. Press NEW and enter "C:\\msys64\\mingw64\\bin". Press ok.
7. Add the path for the EPICS commands and DLLs. Press NEW and enter ``%EPICS_BASE%\bin\%EPICS_HOST_ARCH%``. Press ok twice and you are done.
8. Restart the Machine and check if EPICS commands like ``caget`` and ``camonitor`` are being recognised as valid commands in any location and work.

Note that by default the MSYS2 shell does not inherit the parent environment. To change that behavior, you need to start the shell with the argument ``-use-full-path``.
Note that by default the MSYS2 shell does not inherit the parent environment. To change that behavior, you need to start the shell with the argument ``-use-full-path``. To make MSYS2 always inherit the parent environment, uncomment the line rem set MSYS2_PATH_TYPE=inherit in "C:\\msys64\\msys2_shell.cmd".