Files
qt-migration-legatus/qt5-before/dlbo/specs/external/guez_buildings/postProcessingExcon
torstenandCopilot 7173785915 Qt6 Migration: Complete migration with DDS/RTI support and build validation
Major Changes:
- Merged latest Qt5 devel content from dlbo (292 files changed, 7 new dirs)
- Consolidated forward-declarations and include folders
- Removed unneeded modules per Niklas' repo check list

Build System Fixes:
- Fixed CMake VERSION_GREATER syntax in ParticipantManagement/CMakeLists.txt
- Added VLC packages (libvlc-dev, vlc-plugin-base) to docker_build.sh
- Added PostgreSQL dev packages (libpq-dev, postgresql-server-dev-all) to Dockerfile
- Fixed locale warnings (ANSI_X3.4-1968 → C.UTF-8)
- Fixed ArcGIS SDK path warnings when BUILD_ARCGIS=OFF

Code Generation Fixes:
- Fixed IDL enum collisions (PortType→CorePortType/DdsutPortType, PdmEventType)
- Fixed Grantlee template svc_translation.cpp.grantlee:
  - Changed {{ idl_enum.name }}_def:: to {{ idl_enum.name }}::
  - Fixed .underlying() calls for C++11 scoped enums (enum class)
- Removed generated files from repo (moc_*, *_dtc.h, *_ftc.h)

Validation:
- BUILD_RTI=ON: SUCCESS
- BUILD_RTI=OFF: SUCCESS
- C++17 standard maintained for RTI 7.7 compatibility
- Ubuntu 26.04 Docker environment verified

Remaining Warnings (expected):
- BgViewer, KDChart, KDReports, Poppler-Qt6 not found (optional features)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-09-15 18:20:26 +00:00
..

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# $Id$
# $HeadURL$
# $Author$
# Created by Norbert Thoden, SLSE, 2021-03-16

Um die postProcessingExcon Scripte laufen zu lassen sind erforderlich
- xls2csv   zypper in xls2csv
- cs2cs     zypper install proj

In dem Unterverzeichnis vwm_adjustment befinden sich die Scripte von Manfred Gronak.
Sie dienen dazu, die Positionen der Anbringungspunkte der BSM (aussen) so zu verschieben,
dass bei Beschuss der korrekte Raum beschädigt wird.

Um die js-Files auszuführen sind ein paar Vorbereitungsschritte notwendig:

- Repository für NodeJS hinzufügen (Es sollte aktuell sein, damit die Nachinstalltionen per npm funktionieren)
  (192.168.133.111 -> Repo-Server bei Mike Wille)

  --------------------
  ctc@CTCAP15:/etc/zypp/repos.d> cat nodejs.repo
  [nodejs]
  name=nodejs
  enabled=1
  autorefresh=1
  baseurl=http://192.168.133.111/pub/repositories/devel:/languages:/nodejs/openSUSE_Leap_15.1/
  path=/
  type=rpm-md
  keeppackages=0
  --------------------


  Unklar ist, welche Version nun tatsächlich notwendig ist...
  sudo zypper install nodejs
  sudo zypper install nodejs12




- ein paar js-Pakete nachinstallieren:

  - Proxy-Settings:
    (Aucvh wenn im Netz oft die Notation die Notation mit "@" zu lesen ist,

    USER@PWD|PROXY:PORT  --> bei OpenSuse 15.1 hat funktioniert: NEIN
    USER:PWD|PROXY:PORT  --> bei OpenSuse 15.1 hat funktioniert: JA

    npm config set proxy http://<MAIL_ADR>:<PWD>@213.61.254.67:8080
    npm config set https-proxy http://<MAIL_ADR>:<PWD>@213.61.254.67:8080

    ->
    cat ~/.npmrc
    proxy=http://norbert.thoden%40rheinmetall.com:<PWD>@213.61.254.67:8080/
    https-proxy=http://norbert.thoden@rheinmetall.com:<PWD>@213.61.254.67:8080

  - npm install
    npm install xml2json
    npm install fs
    npm install xml-formatter
    npm install js2xmlparser

Thore:
>>>Hallo,
auf dem guez-15-1-qt-5-15-rpmbuild - 10.198.80.103 ist das bereits entsprechend umgesetzt:
Zur nachlese:

zypper ar http://10.198.80.75/opensuse/15.1/repositories/devel:/languages:/nodejs/openSUSE_Leap_15.1/ nodejs;
zypper rm nodejs10 nodejs10-devel –y && zypper in nodejs12 nodejs12-devel –ly;
npm config set proxy http://10.198.80.60:3128;
npm config set https-proxy http://10.198.80.60:3128;
npm install npm@latest;
npm install xml2json fs xml-formatter js2xmlparser;
npm config delete proxy;
npm config delete https-proxy;  <<<

Mit su (ohen -) habe ich dann noch machen müssen:
npm install -g xml2json fs xml-formatter js2xmlparser

mit npm -list -g sieht man dann, WO diese sind -> NODE_PATH