Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • cerbero cerbero
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 101
    • Issues 101
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 35
    • Merge requests 35
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamerGStreamer
  • cerberocerbero
  • Issues
  • #109
Closed
Open
Issue created Jan 05, 2019 by Stuart Whelan@stuart1

msys python vs mingw python issues on windows.

I have been trying to get a gstreamer build environment up and running on windows. One of the issues I ran into was that when running the cerbero bootstrapper it would fail to detect my windows version.

Investigation showed that the call to platform.win32_ver() in cerbero/utils/init.py returns blank values when using the default msys python.

Running the bootstrapper with /mingw64/bin/python3 ./cerbero-uninstalled bootstrap resolved this issue.

Part of the issue is that I had already installed msys and mingw64, but not using the recommend http://sourceforge.net/projects/mingw/files/Installer/mingw-get-setup.exe/download link.

It would have saved me a lot of time if the bootstrapper had detected me running the incorrect instance of python. :)

Edited Jan 05, 2019 by Stuart Whelan
Assignee
Assign to
Time tracking