Skip to content
Snippets Groups Projects

Create a Vapi file when building the library as recommended by the Vala documentation.

Open username-removed-127580 requested to merge wip/vala-support into master

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Thanks Corentin, and sorry for the very late reply :-)

    I would like to be able to generate the vapi file automatically, but unfortunately we have some existing code out there, and we must make sure that they continue building with this file. For instance the AgManager class has a list() method which in the old vapi file returns an list of uints. Now, with your change, this becomes a list of Ag.AccountId. Is it possible (maybe via some comments in the source code) alter the way that vapigen works, so that it generates the same file as we have now?

  • Ag.AccountId is registered as a uint subclass, so your old code should still compile. It might be a better idea to just remove the AgAccountId from the C code and use the simple GLib types, we don't need such typedefs… If you really want to force to uint, it's possible to provide a .metadata file that overrides the types, but again it's maybe better to have a sane API than overriding the results

Please register or sign in to reply
Loading