Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • libvlcpp libvlcpp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VideoLAN
  • libvlcpplibvlcpp
  • Issues
  • #7

Closed
Open
Created Oct 08, 2020 by hacker1024@hacker1024

MinGW?

There are numerous changes for MSVC when the _MSC_VER macro is set, including a change to stop using asprintf in Instance.hpp. When using MinGW instead, these macros don't get activated. Is it possible to check for the __MINGW32__ when required? It wouldn't be everywhere _MSC_VER is used, as MinGW does provide some GCC-only features, like the ssize_t type.

Assignee
Assign to
Time tracking

VideoLAN code repository instance