* Yu Feng wrote on Sun, Apr 26, 2009 at 03:51:50AM CEST:
Is it possible to also add valadoc support in automake together with
vala support?
What does valadoc do, where is it documented, what kind of rules do you
use instead of automake support, what pitfalls are there?
Thanks,
Ralf
On Sun, 2009-04-26 at 09:50 +0200, Ralf Wildenhues wrote:
* Yu Feng wrote on Sun, Apr 26, 2009 at 03:51:50AM CEST:
Is it possible to also add valadoc support in automake together with
vala support?
What does valadoc do, where is it documented, what kind of rules do you
use instead
Is it possible to also add valadoc support in automake together with
vala support?
Yu
On Thu, 2009-04-16 at 21:19 +0200, Jürg Billeter wrote:
On Thu, 2009-04-16 at 21:09 +0200, Ralf Wildenhues wrote:
* Jürg Billeter wrote on Thu, Apr 16, 2009 at 09:02:30PM CEST:
On Thu, 2009-04-16 at 20:49
output for all the vala tests?
[...]
That will allow me to finish review before finishing my system.
I've attached the verbose test log.
Thanks again for this.
There are still a few things that don't work in the Automake support for
vala, as uncovered by the rest of this discussion. However
Hi Ralf,
On Thu, 2009-04-16 at 20:49 +0200, Ralf Wildenhues wrote:
* Jürg Billeter wrote on Wed, Apr 15, 2009 at 08:56:44PM CEST:
On Wed, 2009-04-15 at 20:42 +0200, Ralf Wildenhues wrote:
or even
valac -C b.vala
valac -C e.vala
This would not work, valac requires all Vala
Hi Jürg,
* Jürg Billeter wrote on Wed, Apr 15, 2009 at 08:56:44PM CEST:
On Wed, 2009-04-15 at 20:42 +0200, Ralf Wildenhues wrote:
I'm looking at adding per-target flag support for vala sources.
Say I have baz.vala and want to create from that
foo-baz.c foo-baz.h
in one valac
* Jürg Billeter wrote on Thu, Apr 16, 2009 at 09:02:30PM CEST:
On Thu, 2009-04-16 at 20:49 +0200, Ralf Wildenhues wrote:
bin_PROGRAMS = foo
foo_SOURCES = foo1.vala foo2.vala
foo_LDADD = libbar.a
noinst_LIBRARIES = libbar.a
libbar_a_SOURCES = bar1.vala bar2.vala
How would valac cope
On Thu, 2009-04-16 at 21:09 +0200, Ralf Wildenhues wrote:
* Jürg Billeter wrote on Thu, Apr 16, 2009 at 09:02:30PM CEST:
On Thu, 2009-04-16 at 20:49 +0200, Ralf Wildenhues wrote:
bin_PROGRAMS = foo
foo_SOURCES = foo1.vala foo2.vala
foo_LDADD = libbar.a
noinst_LIBRARIES = libbar.a
Hi Ralf,
On Wed, 2009-04-15 at 20:42 +0200, Ralf Wildenhues wrote:
I'm looking at adding per-target flag support for vala sources.
Say I have baz.vala and want to create from that
foo-baz.c foo-baz.h
in one valac invocation, as well as
bar-baz.c bar-baz.h
in another 'valac -D BAR'
Hi Jürg,
* Jürg Billeter wrote on Tue, Apr 07, 2009 at 11:20:36PM CEST:
I've attached the verbose test log.
Thanks.
I'm looking at adding per-target flag support for vala sources.
Say I have baz.vala and want to create from that
foo-baz.c foo-baz.h
in one valac invocation, as well as
Hi Ralf,
On Tue, 2009-04-07 at 23:08 +0200, Ralf Wildenhues wrote:
Other than that, I haven't yet gotten around to get my system up to date
in order to support Vala 0.7 yet. Would you be so nice as to post
verbose log output for all the vala tests? That is, just
cd tests
for t in
Hello Jürg,
very nice. Thanks again for working on this. At a first glance, all I
could find while reading the patch was a trivial s/_SOURCE/_SOURCES/ in
the manual.
Other than that, I haven't yet gotten around to get my system up to date
in order to support Vala 0.7 yet. Would you be so nice
+
+Automake provides support for Vala compilation
+(@uref{http://www.vala-project.org/}).
+
+...@example
+foo_SOURCES = foo.vala bar.vala zardoc.c
+...@end example
+
+Any @file{.vala} file listed in a @code{_SOURCE} variable will be
+compiled into C code by the Vala compiler.
+
+Automake ships
Dear Jurg,
I have two questions:
If a VALA package depends on the features provided in the patch, will
the distributed tarball(make dist) be compilable on a system with a
unpatched automake?
Is VALA itself going to make use of the features once the they are
accepted in the automake upstream? If
14 matches
Mail list logo
