How to split NSIS script among developers?

Question

I would like to share the tasks for developing an NSIS installer among several developers. How can I physically organize the code? Do I need to edit and combine a single .nsi script when they check for SVN? Is it possible to split NSIS scripts into modular, separate files? That would be perfect.

Thanks!

Answer 1

I use the "main" nsi file, which makes up the actual installer creation and the MUI code, but includes the "additional" function definitions from the nsi files, as well as separate files for each "Installer" section.

Example:

!include "LibraryFunction1.nsh"
!include "LibraryFunction2.nsh"
!include "LibraryFunction3.nsh"

; Basic Defines and MUI code Go HERE

; Output file information
Name "${PRODUCT_NAME} ${PRODUCT_VERSION}"
OutFile "File-${BUILD_VER_ABRV}-${BUILD_VER_MIN}.exe"
InstallDir "$PROGRAMFILES\Location\"
InstallDirRegKey HKLM "${PRODUCT_DIR_REGKEY}" ""

; now include file sections
!include "FileSectionDefinition1.nsh"
!include "FileSectionDefinition2.nsh"
!include "FileSectionDefinition3.nsh"
!include "Uninstall.nsh"

Answer 2

! "uninstaller.nsh" .. ( , .nsh)

Answer 3

(.nsh) script . , MUI, , , (.NET framework). , include, MUI ! ! Insertmacro MUI_PAGE_x. , .

Answer 4

, , NSI. .