build from source

[Angelica Perduta]

On Wed, Jan 16, 2013 at 12:46 PM, David Hoyt <dhoyt at guidewire.com> wrote:
> I take it you've already read through tutorials on autotools (e.g. http://bit.ly/13ALhwq).

Yes I did google autotools and there is a phenomenal amount to learn
there including extensive tutorials for those who want to create their
own projects with said system.

However I just want a reasonably up to date version of the gstreamer
library so I can use it in a multi-media application I am trying to
develop myself. However since there is no binary distribution
available beyond the 0.10 edition, I have little choice but to try and
build it from source.

> You can try specifying a prefix on configure if libraries are not being installed to the correct location. e.g.: configure --prefix=<path to desired location>.
>

I wouldn't know what prefix to use since it installs them exactly
where I want them: In the default location. It's the *.la file that it
puts there which specifies incorrect dependencies that do not exists
and I don't know where they are getting it from.

The whole point of autotools and MinGW is that I should be able to do

./configure
make
make install

That works for gstreamer but failes for gst-plugins-base due to the
gstreamer library dependencies.
Now I did manage to find some files named *.lai where the 'erlkoenig'
name appears and edited those to point to my more standard
installation directory /usr/lib but they turn out to just be some kind
of intermediate file that gets overwritten when I run the make command
again.

I was unable to find said name anywhere else on my system also not in
the environment so like I said it's a bit of a mystery where those
file paths are coming from.

> You could reference OSSBuild's build script for GStreamer dependencies: http://code.google.com/p/ossbuild/source/browse/trunk/Libraries/Build-All-Windows-x86.sh which might help direct you. It's rather old at this point, but fine for getting an idea of how you could approach things.

Yes I did look there but then I think I have to go back to using
Microsoft visual studio and when I use that to compile and link with
the latest Gtk+ libraries (without ANY gstreamer at all even) it
crashes at run time... so that would put me back to building Gtk+ from
source using the Microsoft tools so that I can debug it.

> Also, if you take a look at that script, you'll see that to do a native build on Windows from the ground up is no easy thing. There are many, many dependencies (and many transitive dependencies at that). You could consider, instead, cross-compiling from Linux. The environment is definitely more sane. Just a thought...

I don't think it's a MinGW issue. The mysterious dependency paths
suggest that said 'erlkoenig' uses MinGW too. Oh well thanks for the
suggestions anyway :o)