From 039ac92480a09266146fc5b0c9ec67a32a2565ad Mon Sep 17 00:00:00 2001
From: saurabhb17
Date: Wed, 26 Feb 2020 16:04:40 +0530
Subject: Added secondary files

---
 Documentation/KIWAY_Build_Symbols_Defined.txt | 29 +++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 Documentation/KIWAY_Build_Symbols_Defined.txt

(limited to 'Documentation/KIWAY_Build_Symbols_Defined.txt')

diff --git a/Documentation/KIWAY_Build_Symbols_Defined.txt b/Documentation/KIWAY_Build_Symbols_Defined.txt
new file mode 100644
index 0000000..f10dea9
--- /dev/null
+++ b/Documentation/KIWAY_Build_Symbols_Defined.txt
@@ -0,0 +1,29 @@
+
+KIWAY Build Symbols, Definitions and Intentions
+
+
+COMPILING_DLL:
+
+    This is a signal to import_export.h, and when present, toggles the
+    interpretation of the #defines in that file. Its purpose should not be
+    extended beyond this.
+
+
+USE_KIWAY_DLLS:
+
+    Comes from CMake as a user configuration variable, settable in the Cmake
+    user interface. It decides if KiCad will be built with the *.kiface program
+    modules.
+
+
+BUILD_KIWAY_DLL:
+
+    Comes from CMake, but at the 2nd tier, not the top tier. By 2nd tier,
+    something like pcbnew/CMakeLists.txt, not /CMakeLists.txt is meant. It is
+    not a user configuration variable. Instead, the 2nd tier CMakeLists.txt file
+    looks at the top level USE_KIWAY_DLLS and decides how the object files under
+    the 2nd tier's control will be built. If it decides it wants to march in
+    lockstep with USE_KIWAY_DLLS, then this local CMakeLists.txt file may pass a
+    defined BUILD_KIWAY_DLL (singular) on the compiler command line to the
+    pertinent set of compilation steps under its control.
+
-- 
cgit