On Thu, 2011-10-27 at 16:58 +0800, PCMan wrote:
> If I did not get it wrong, it seems to generate a single header file "g
> mpc-extras.h".
> For what I want, I prefer generating file_a.[ch] for file_a.vala,
> file_b.[ch] for file_b.vala, and file_c.[ch] for file_c.vala. Each vala file
> can has its
>
>
> For C from Vala calls, feel free to borrow ideas from Spek:
> https://github.com/alexkay/spek
>
> Also check out Sampala: https://github.com/tadeboro/Sampala
and how about the opposite, calling vala from C?
Adding --header or -H to vala flags will only generate a single large header
file fo
If I did not get it wrong, it seems to generate a single header file "g
mpc-extras.h".
For what I want, I prefer generating file_a.[ch] for file_a.vala,
file_b.[ch] for file_b.vala, and file_c.[ch] for file_c.vala. Each vala file
can has its own generated *.c and *.h files.
Is this possible with au
On 27 October 2011 12:53, PCMan wrote:
> Hello,
> I'm the developer of LXDE project and I started using Vala last night.
> Most parts of our existing code are written in pure C with or without
> GObject.
> Now I want to do further development in vala.
> To mix vala code with existing C code, I can
Hello,
I'm the developer of LXDE project and I started using Vala last night.
Most parts of our existing code are written in pure C with or without
GObject.
Now I want to do further development in vala.
To mix vala code with existing C code, I cannot find any good guide on the
internet.
Some existi
