[MonoDevelop] [Problem] Project reference with vala

[Jan Hudec]

Levi Bard <taktaktaktaktaktaktaktaktaktak <at> gmail.com> writes:
> > I am playing with some Vala code in monodevelop. I currently have two 
projects
> > in the solution -- one library and one unit test for it -- and plan to add 
a
> > few more. And I have a problem with the reference from the test project to 
the
> > library one works only partly.
> >
> > I mean, the valac is given correct .vapi file to generate the code, but it 
is
> > *not* given either include path nor the library file for the C compiler, so
> > vala generates the C sources, but compiling them fails.
> 
> Hi, it's great to see someone using MD for Vala!

I am contemplating doing some core stuff in Vala and combining it with gui in
C# (or even more preferably Boo if the gui builder starts working with it
in the meantime), so MD is kind of logical choice. Plus I am used to VS from
work.

> I think valac's behavior in this respect has changed semi-recently; if
> I recall correctly, it used to be that, if one were compiling directly
> to binaries, neither the include path nor the linker path were
> required. (What version of Vala are you using?)

I was using 0.5.7. I updated MD to 2.0.0 from Debian, but forgot to check valac 
updates (I disabled automatic updates because I don't want to do the KDE 
transition just yet). But I just retried with 0.7.0 and it seems to behave 
exactly the same.

> > I have currently worked around the problem by manually adding
> > appropriate --Xcc= options in the Build/Code Generation properties. But as 
I
> > said, I plan to add a few more projects and it will quickly grow ugly.
> >
> > Do you have any better proposal? Or should this be reported as a (possibly
> > wish-list) bug?
> 
> This is definitely a bug. I'll address it as soon as possible.

Thanks.

Best regards,
Jan