Integrating local applications is very simple. The following describes what files each sub-directory should contain:
${UG_VER}/application - Contains all BMP and UBM files. May also contain UI/Styler dialog(.dlg) and Menuscript(.men) files.
${UG_VER}/dfa - Contains site DFA files. May also contain UI/Styler dialog(.dlg) files.
${UG_VER}/startup - Contains Menuscript(.men) and toolbar(.tbr) files.
${UG_VER}/win64/application - Contains UG/Open API and UG/Open GRIP programs built for win64.
${UG_VER}/win64/startup - Contains Menuscript(.men) and toolbar(.tbr) files to be defined just on win64.
${UG_VER}/win64/udo - Contains UG/Open API UDO shared libraries(.sl) for win64.
${UG_VER}/lib/win64 - Contains common UG/Open API shared libraries used by multiple applications for win64.
For more complex applications that need to be grouped together, you will need to create a new custom directory. Let's call this new custom directory my_local_app and place it in ${DSL_DEPT_DIR}/${UG_VER}. To tell NX to search this new directory, add the directory path to the ${DSL_DEPT_DIR}/${UG_VER}/config/custom_dirs.dat file. The added line should look like this:
${DSL_DEPT_DIR}/${UG_VER}/my_local_app
The structure of my_local_app should be:
dfa - Contains DFA files common to all apps. May also contain DLG files.
application - Contains DLL, SL, BMP, and UBM files. May also contain DLG files.
startup - Contains .MEN and .TBR files. May also contain DLL or SL files.
udo - Contains UDO shared libraries.
The above assumes you are supporting one platform of is a Knowledge Fusion application. For a UG/Open API code, you will need to create additional custom directories for each supported platform. Only the platform dependent files need to go into this custom directory. The entry in the custom_dirs.dat file would like this:
${DSL_DEPT_DIR}/${UG_VER}/my_local_app/${OS}
This way only the appropriate platform custom directory will be added to NX's
search path.