Perhaps I'm missing something, but I think there is a pretty big problem with this... When you roll a dist tarball, the Vala code will be compiled to C with *your* valac, and the resulting C code will not contain both versions.
AFAIK there isn't currently a way to convince the Vala support built into autotools to require users of dist tarballs to compile the Vala code to C. You will probably have to ditch the built in support for Vala. -E On Wed, 2010-10-27 at 09:15 +0200, pancake wrote: > Thanks > > http://hg.youterm.com/valaswig/rev/480d91d604c8 > > On Wed, 27 Oct 2010 08:30:27 +0200 > Jürg Billeter <j...@bitron.ch> wrote: > > > On Wed, 2010-10-27 at 08:10 +0200, pancake wrote: > > > Is there any way to check at preprocessor stage for the version of > > > vala? Or I have to do this check outside (configure?) and then pass > > > the -D to valac? > > > > > > #ifdef VALA10 > > > ... Old/stable stuff here > > > #else > > > .. New stuff here > > > #endif > > > > #if VALA_0_12 > > ... Code for Vala >= 0.11 > > #else > > ... Code for older Vala > > #endif > > > > This is implicitly defined and doesn't need -D. > > > > Jürg > > > _______________________________________________ > vala-list mailing list > vala-list@gnome.org > http://mail.gnome.org/mailman/listinfo/vala-list _______________________________________________ vala-list mailing list vala-list@gnome.org http://mail.gnome.org/mailman/listinfo/vala-list
