Differences

This shows you the differences between two versions of the page.

--- kb:labview:build_specs [2021/05/31 17:35] – [Destination Directory] alexander.elbert
+++ kb:labview:build_specs [2023/03/08 10:35] (current) – joerg.hampel
@@ Line 3: / Line 3: @@
 //For more details, see https://zone.ni.com/reference/en-XX/help/371361R-01/lvconcepts/building_standaloneapps/ //
-A build specification contains all the settings for a LabVIEW build, such as files to include, directories to create, and settings for VIs. The following items can be built using the Application Builder:
+The [[kb:labview:tools:appbuilder|LabVIEW Application Builder Module]] provides tools for exporting LabVIEW code in various forms. The most common ones are stand-alone, end-use applications and source code exports.
+Builds are configured via build specifications. A build specification contains all the settings for a LabVIEW build, such as files to include, directories to create, and settings for VIs. The following items can be built:
   * Stand-alone application
@@ Line 20: / Line 22: @@
 ==== Preserve Disc Hierarchy ====
-The builder will not create an empty directory, it only counts files as contents and ignores folders.
+The builder will not create an empty directory, it only counts files as contents and ignores folders. You can add a dummy file as 'always included' in a hierarchy level you want to be existent in the build.
 Source:
+  source/someFilesNotIncludedInBuildSpec.txt
   source/ParentFolder/ChildFolder/file1.ext
   source/ParentFolder/ChildFolder/file2.ext
+  source/neededDir/dummyFile.txt
+  source/neededDir/nextLevel/someIncluded.vi
 Build Result:
@@ Line 31: / Line 36: @@
   builds/ParentFolder/file1.ext
   builds/ParentFolder/file2.ext
+  builds/neededDir/dummyFile.txt
+  builds/neededDir/someIncluded.vi
 ==== Destination Directory ====