Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2022-07

gtk3, glib2 headers, gir2pascal

5 messages · 2 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Marco van de Voort

Who maintains the gtk3 headers and gir2pascal?

Last week I tried to port a glib based library (Aravis), and I noticed that the interface/gtk3/gtk3defs headers were out of date, and didn't support Windows.

So I sought to regenerate them, with a modified gir2pascal and also saw that some more recent patches (https://github.com/n1tehawk/gir2pascal) were not incorporated in lazarus-ccr yet. (I base myself on that version).

Since local changes and githubgitlab is complicated, it is probably the best to work with patches. Anybody interestd?

Reply by email

Maxim Ganetsky
to Marco van de Voort

16.07.2022 16:42, Marco van de Voort via lazarus ?????:

Show quoted text 13 lines
Who maintains the gtk3 headers and gir2pascal? Last week I tried to port a glib based library (Aravis), and I noticed that the interface/gtk3/gtk3defs headers were out of date, and didn't support Windows. So I sought to regenerate them, with a modified gir2pascal and also saw that some more recent patches (https://github.com/n1tehawk/gir2pascal) were not incorporated in lazarus-ccr yet. (I base myself on that version). Since local changes and githubgitlab is complicated, it is probably the best to work with patches. Anybody interestd?

It is actually worse, it's Git->SVN. Although the patch set is not very big (and looks fine BTW), so it's doable.

But IMO, this tool should just be incorporated into Lazarus sources. What do you (and others) think about this?

Best regards, Maxim Ganetsky mailto:

Reply by email

Marco van de Voort
to Maxim Ganetsky
Maxim Ganetsky wrote 7 lines
It is actually worse, it's Git->SVN. Although the patch set is not very big (and looks fine BTW), so it's doable. But IMO, this tool should just be incorporated into Lazarus sources. What do you (and others) think about this?

Agree. Due to the usage for the interface headers it is kind of like a dependency of lazarus, so it shouldn't be in a repo for 3rd party components.

Reply by email

Maxim Ganetsky
to Marco van de Voort

17.07.2022 15:09, Marco van de Voort via lazarus ?????:

Show quoted text 12 lines
On 16-7-2022 21:27, Maxim Ganetsky via lazarus wrote: > > It is actually worse, it's Git->SVN. Although the patch set is not > very big (and looks fine BTW), so it's doable. > > But IMO, this tool should just be incorporated into Lazarus sources. > What do you (and others) think about this? > Agree. Due to the usage for the interface headers it is kind of like a dependency of lazarus, so it shouldn't be in a repo for 3rd party components.

This tool is now part of Lazarus source code tree in main branch and located in <lazarusdir>/tools/gir2pascal.

Best regards, Maxim Ganetsky mailto:

Reply by email

Marco van de Voort
to Maxim Ganetsky
Maxim Ganetsky wrote
This tool is now part of Lazarus source code tree in main branch and located in <lazarusdir>/tools/gir2pascal.

Great, thanks. I'll try to add my mods (windows-only) in the coming days.

Reply by email