Hi,
I wanted to move my geany-multiterm[1] plugin into the Geany-Plugins repository and continue development there, but I need help with some things. It's written in Vala[2] using the Geany binding[3] Colomban wrote.
My questions are:
Is there a maintainer mode or something that can be use to only activate Vala support in Autotools if this plugin is selected to build? Should this go into `build/multiterm.m4`?
Should the .c/.h files that valac compiles be checked into the VCS so that people without valac compiler can still compile the plugin?
How to make it work with Waf?
(Mostly for Colomban) How should the geany.vapi/.deps be distributed? If I make it install into the normal location I guess it will conflict with the "official" binding, but then again AFAIK the "official" one isn't really distributed, it just lives in a Gitorious repo[3], so I can't really depend on it (or can I?). Could we move the "official" Vala binding to Geany-Plugins project as well so that it is released with GP and other plugins can depend on it being there?
Cheers, Matthew Brush
[1] https://github.com/codebrainz/geany-multiterm [2] https://live.gnome.org/Vala [3] http://gitorious.org/geany-vala-binding
On 12/15/2011 08:35 PM, Matthew Brush wrote:
(Mostly for Colomban) How should the geany.vapi/.deps be distributed? If I make it install into the normal location I guess it will conflict with the "official" binding, but then again AFAIK the "official" one isn't really distributed, it just lives in a Gitorious repo[3], so I can't really depend on it (or can I?). Could we move the "official" Vala binding to Geany-Plugins project as well so that it is released with GP and other plugins can depend on it being there?
I don't know why I thought I had to install the binding into the system since it's only used during compilation, stupid me!
The only real question is whether to keep copies of the binding in the source of the multiterm plugin in Geany-Plugins or to depend on the `geany` Vala package being installed on the system.
Cheers, Matthew Brush
Hi,
I just added the MultiTerm plugin to Geany-Plugins master branch. Please let me know ASAP if it causes you any issues.
It still needs to be added to the Waf build system and there's lots of work to do on everything else.
Note: there's some build warnings even without make check that are caused by the C code that is generated by valac. There's not much I can do about it, the fixes will come with newer valac versions, I'm sure.
Cheers, Matthew Brush
On 12/15/2011 08:35 PM, Matthew Brush wrote:
Hi,
I wanted to move my geany-multiterm[1] plugin into the Geany-Plugins repository and continue development there, but I need help with some things. It's written in Vala[2] using the Geany binding[3] Colomban wrote.
My questions are:
Is there a maintainer mode or something that can be use to only activate Vala support in Autotools if this plugin is selected to build? Should this go into `build/multiterm.m4`?
Should the .c/.h files that valac compiles be checked into the VCS so that people without valac compiler can still compile the plugin?
How to make it work with Waf?
(Mostly for Colomban) How should the geany.vapi/.deps be distributed? If I make it install into the normal location I guess it will conflict with the "official" binding, but then again AFAIK the "official" one isn't really distributed, it just lives in a Gitorious repo[3], so I can't really depend on it (or can I?). Could we move the "official" Vala binding to Geany-Plugins project as well so that it is released with GP and other plugins can depend on it being there?
Cheers, Matthew Brush
[1] https://github.com/codebrainz/geany-multiterm [2] https://live.gnome.org/Vala [3] http://gitorious.org/geany-vala-binding _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Le 18/12/2011 06:07, Matthew Brush a écrit :
Hi,
I just added the MultiTerm plugin to Geany-Plugins master branch. Please let me know ASAP if it causes you any issues.
It breaks the build from Git when the user ain't got valac.
I committed a perfectable fix that simply checks whether AM_PROG_VALAC actually found a Vala compiler. At least people with no valac can now build geany-plugins again.
Regards, Colomban
It still needs to be added to the Waf build system and there's lots of work to do on everything else.
Note: there's some build warnings even without make check that are caused by the C code that is generated by valac. There's not much I can do about it, the fixes will come with newer valac versions, I'm sure.
Cheers, Matthew Brush
On 12/15/2011 08:35 PM, Matthew Brush wrote:
Hi,
I wanted to move my geany-multiterm[1] plugin into the Geany-Plugins repository and continue development there, but I need help with some things. It's written in Vala[2] using the Geany binding[3] Colomban wrote.
My questions are:
Is there a maintainer mode or something that can be use to only activate Vala support in Autotools if this plugin is selected to build? Should this go into `build/multiterm.m4`?
Should the .c/.h files that valac compiles be checked into the VCS so that people without valac compiler can still compile the plugin?
How to make it work with Waf?
(Mostly for Colomban) How should the geany.vapi/.deps be distributed? If I make it install into the normal location I guess it will conflict with the "official" binding, but then again AFAIK the "official" one isn't really distributed, it just lives in a Gitorious repo[3], so I can't really depend on it (or can I?). Could we move the "official" Vala binding to Geany-Plugins project as well so that it is released with GP and other plugins can depend on it being there?
Cheers, Matthew Brush
[1] https://github.com/codebrainz/geany-multiterm [2] https://live.gnome.org/Vala [3] http://gitorious.org/geany-vala-binding _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Le 18/12/2011 16:52, Colomban Wendling a écrit :
Le 18/12/2011 06:07, Matthew Brush a écrit :
Hi,
I just added the MultiTerm plugin to Geany-Plugins master branch. Please let me know ASAP if it causes you any issues.
It breaks the build from Git when the user ain't got valac.
I committed a perfectable fix that simply checks whether AM_PROG_VALAC actually found a Vala compiler. At least people with no valac can now build geany-plugins again.
...but it still breaks make dist that tries to distribute the compiled .c, and that's probably way harder to "fix". Or we accept that creating a dist tarball now requires valac.
Regards, Colomban
It still needs to be added to the Waf build system and there's lots of work to do on everything else.
Note: there's some build warnings even without make check that are caused by the C code that is generated by valac. There's not much I can do about it, the fixes will come with newer valac versions, I'm sure.
Cheers, Matthew Brush
On 12/15/2011 08:35 PM, Matthew Brush wrote:
Hi,
I wanted to move my geany-multiterm[1] plugin into the Geany-Plugins repository and continue development there, but I need help with some things. It's written in Vala[2] using the Geany binding[3] Colomban wrote.
My questions are:
Is there a maintainer mode or something that can be use to only activate Vala support in Autotools if this plugin is selected to build? Should this go into `build/multiterm.m4`?
Should the .c/.h files that valac compiles be checked into the VCS so that people without valac compiler can still compile the plugin?
How to make it work with Waf?
(Mostly for Colomban) How should the geany.vapi/.deps be distributed? If I make it install into the normal location I guess it will conflict with the "official" binding, but then again AFAIK the "official" one isn't really distributed, it just lives in a Gitorious repo[3], so I can't really depend on it (or can I?). Could we move the "official" Vala binding to Geany-Plugins project as well so that it is released with GP and other plugins can depend on it being there?
Cheers, Matthew Brush
[1] https://github.com/codebrainz/geany-multiterm [2] https://live.gnome.org/Vala [3] http://gitorious.org/geany-vala-binding
On 12/18/2011 07:57 AM, Colomban Wendling wrote:
Le 18/12/2011 16:52, Colomban Wendling a écrit :
Le 18/12/2011 06:07, Matthew Brush a écrit :
Hi,
I just added the MultiTerm plugin to Geany-Plugins master branch. Please let me know ASAP if it causes you any issues.
It breaks the build from Git when the user ain't got valac.
I committed a perfectable fix that simply checks whether AM_PROG_VALAC actually found a Vala compiler. At least people with no valac can now build geany-plugins again.
Thanks for fixing that, I was still trying to figure out how.
...but it still breaks make dist that tries to distribute the compiled .c, and that's probably way harder to "fix". Or we accept that creating a dist tarball now requires valac.
I don't think it's too big a deal to require valac, it's been around for 4 or 5 years and is available in most (all?) popular distro repositories. What do we do for things like `glib-mkenums`?
Cheers, Matthew Brush