Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • OpenFlipper-Free OpenFlipper-Free
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenFlipper-FreeOpenFlipper-Free
  • OpenFlipper-FreeOpenFlipper-Free
  • Issues
  • #77

Wrong cmake subsystem configuration in console mode on Windows (WIN_GET_DEBUG_CONSOLE)

With the cmake flag WIN_GET_DEBUG_CONSOLE enabled on windows, OpenFlipper starts with a console but no output is ever written to it. This is caused by the misconfigured subsystem flag in the OpenFlipper project properties after running cmake. So there is actually no debug output in the console.

The subsystem is always set to /SUBYSTEM:WINDOWS, which prevents output streams to the console. The subsystem should be dependent of the WIN_GET_DEBUG_CONSOLE flag to fix this issue. If it is enabled, then /SUBSYSTEM:CONSOLE should be used, otherwise /SUBSYSTEM:WINDOWS.

Apparently it can be controlled by the "WIN32" flag in add_executable() https://stackoverflow.com/questions/8497948/vs10-always-links-to-subsystemwindows-cmakesdlglew

Assignee
Assign to
Time tracking