[RETHINK] build specs and build process

See

• https://dokuwiki.hampel-soft.com/code/common/deployment-structure
• open-source/hse-framework#29

---

• Introduce a standard for build spec names

  • why? less error-prone
  • Add documentation to the DokuWiki
  • Define standard names:
    • SRC – Source distribution
    • EXE – Executable
    • INST – Installer
    • NIPKG – NI Package
    • RT – Real-Time target
    • ...? – Extend if needed
  • If more than one buildspec, add _ (eg SRC_something)
  • Ensure all build into /builds/<%build-spec-name%>
    • eg <repoRoot>/builds/EXE/<myApp>.exe

• When running from the IDE, the config folder in the repo should be used

  • why? Easy for development
  • Nothing to do

• When the EXE is built manually & locally, the original config folder in the repo should be used

  • why? easy for testing, nice, but not needed
  • Add documentation to the DokuWiki
  • artefacts are built into /builds/<buildspecname>
    • .exe has to be copied manually to a folder next to the config

• Provide EXE + config without installer

  • We will not provide this as a single combined package: Either it's only an update to an existing installation (ie config folder already there) or it's a new installation (ie use NIPKG or know what you're doing)

• For Installer and NI Package, the company name is required to define the target locations

  • eg for company HSE and project Template:
    • C:/Program Files/HSE/Template/