Project dependencies

[GoogleCodeExporter]

We should set-up the projects dependencies...

If a new user fetches the build system and tries to build the solution he
will get a bunch of errors, because projects must be built in order.

The "gstreamer" project should depend on "common",to generate all the
enums, marshallers and headers.

All the gst-libs should depend on the "gstreamer pproject"

All the enum's generation should be done by the "common" project. If not,
the first build always fails because the enum types files are not generated.

All the plugins that depends on a gstreamer library (e.g. gstrtp )should 
depend on the library's project, because it copies headers used by the
plugins to the output dir.

The idea is to build the entire Solution with one click.

Original issue reported on code.google.com by ylatuya on 2 May 2009 at 6:41

[GoogleCodeExporter]

The dependencies should already be working if you use the solution. I've been 
getting one-click compiles just fine.

Original comment by david.g.hoyt on 5 May 2009 at 3:30

[GoogleCodeExporter]

For some reason it wasn't working right on my vista box. The project build 
order 
seemed correct, but when you went to build it, it was not following the same 
order. 
So I added the project-level dependencies (it was solution-level before) and 
that 
seemed to fix it.

I unloaded all farsight-related projects, so those have not been tested. But 
everything else should work.

With the inclusion of the pre-generated files, you should be able to take out 
the 
common and common-farsight2 projects and merge those items into their 
respective 
project. You'll notice I already did that for most of the items in the common 
project.

Original comment by david.g.hoyt on 5 May 2009 at 9:38

• Changed state: Fixed