Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • L libgdata
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • 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
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • libgdata
  • Issues
  • #30
Closed
Open
Issue created Jul 16, 2019 by Mayank Sharma@mayanksha

meson: debug messages of libgdata don't come from correct log domain - "libgdata"

When we link GVfs against the libgdata (after the meson port) and try to print the debug output, all of libgdata's debug output gets prefixed with domain - google-drive:. Moreover, with autotools, we had a separate log domain for each of the demo we had. The G_LOG_DOMAIN needs to be fixed for the shared_library as well as executable.

(https://gitlab.gnome.org/GNOME/libgdata/blob/master/demos/meson.build#L2)

Edited Jul 16, 2019 by Mayank Sharma
Assignee
Assign to
Time tracking