Skip to content

Windows Installer of OpenMS based on NSIS (Nullsoft Scriptable Install System)

Notifications You must be signed in to change notification settings

jpfeuffer/windows-installer

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

90 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

NSIS based Windows Installer for OpenMS

This repository contains all files necessary to create a windows installer from a source build of OpenMS (System A).

Additional required software:

  • NSIS (NullSoft Installer System)

TODO before running OpenMS_installer.nsi

  1. Copy UAC.dll to your <PATH-to-NSIS>/Plugins directory before running the installer script! Otherwise you'll get an error during script compilation: "Invalid command: UAC::RunElevated"
  2. Extract the content of Inettc.zip to your <PATH-to-NSIS> directory before running the installer script! Otherwise you'll get an error during script compilation: "Invalid command: inetc::get"

Quick guide

  1. Fully compile and test OpenMS using a Visual Studio Generator (create the targets [OpenMS TOPP UTILS GUI] - NOT MORE!!)
  2. create the documentation (target "doc" (NOT doc_internal) in OpenMS_build/doc) OR copy the doc folder from Linux if setting up documentation on Windows is too hard or not possible.
  3. Read additional install information in the header of OpenMS_installer.nsi (!)
  4. Adapt relevant settings in the header of OpenMS_installer.nsi to your needs OR see ./auto_package/*.nsi for example files, which you can just copy and modify.
  5. Compile OpenMS_installer.nsi using NSIS (this should create a file named something like OpenMS_setup.exe)
  6. Distribute

Verifying the installer

  • Use a Virtual Machine (System B)
  • Do NOT assume that successfully installing OpenMS_setup.exe on the System A means that the installer will work on a new System B! But you can at least check for major quirks.
  • Check if all files were created and Start Menu entries are present and working.
  • To test the TOPP tools, run TOPPTest_Assembler.pl on System A. e.g.,
    • Adapt paths within TOPPTest_Assembler.pl
    • Open a VS command line
    • > cd c:\<path to win_installer_dir>
    • > TOPPTest_Assembler.pl
    • Now, copy the folder /OpenMS/source/TEST/TOPP/ to System B and run TOPP_test.bat (which should have been created by the perl script).
    • Check if the script runs through without pausing (which means that something needs your attention). If you're picky, then check the whole output of the script. Sometimes a TOPP-tool might give a warning and still produce the correct result, thus the script will not remind you of that.

About

Windows Installer of OpenMS based on NSIS (Nullsoft Scriptable Install System)

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Shell 59.2%
  • Perl 40.8%