From 6e0cb229b5dbb31164c6f8d8a4b98b3e39b1e174 Mon Sep 17 00:00:00 2001
From: Fanny Rodolakis <rodolakis@anl.gov>
Date: Thu, 25 May 2023 13:14:25 -0500
Subject: [PATCH] 4.7 explanation

---
 4-Deploy-motorVMC.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/4-Deploy-motorVMC.md b/4-Deploy-motorVMC.md
index 40850e7..f9cc91a 100644
--- a/4-Deploy-motorVMC.md
+++ b/4-Deploy-motorVMC.md
@@ -380,6 +380,8 @@ make[1]: Leaving directory '/home/beams/USERNAME/PET-S2/epics/synApps_6_2_1/supp
 ```
 </details>
 
+Note: issuing a `make` in the **epics/synApps_6_2_1/support/motorVMC** directory builds the motorVMC support module, whereas running make in the **epics/synApps_6_2_1/ioc/xxx** directory builds the specific IOC application (binary), which relies on various support modules, including motorVMC. The former focuses on building the support module itself (dbd and lib), while the latter focuses on building the IOC application that utilizes the support modules (binary).
+
 ### 4.8 Confirm build products exist
 
 When the build is successful there should be a database definitions file (.dbd) in the top level dbd dir, as well as a static library (.a) and a dynamic library (.so) in the arch-specific lib dir.
@@ -402,4 +404,6 @@ total 92
 ```
 </details>
 
+
+
 ## [5 Add virtual motors to the IOC](5-Add-virtual-motors.md)
-- 
GitLab