Adding and external dependency that cannot be built using MinGW

[GoogleCodeExporter]

I need to add libnice for the Farsight2's Nice transmitter. 
This library cannot be built using mingw (I already asked in the nice
mailing list). I have the VS project, but I don't really know where to
place it, and how to proceed integrate it in the build system...

Original issue reported on code.google.com by ylatuya on 5 May 2009 at 9:45

[GoogleCodeExporter]

With enough coaxing I was able to get it to compile under msys/mingw. I'm not 
sure 
how correct the resulting binary is and I certainly haven't tested it, but I 
was 
able to do it. It required several tweaks.

I'll commit it to the repo as soon as I have it a little cleaned up.

Original comment by david.g.hoyt on 6 May 2009 at 12:44

• Changed state: Started

[GoogleCodeExporter]

Great!

Original comment by ylatuya on 6 May 2009 at 12:57

[GoogleCodeExporter]

I added the source and some quick patches, but I'd like to do a better job of 
it so I 
can submit the fixes to the libnice folks. I also need to see why it won't 
produce a 
shared library - it's only creating a static one. Probably a libtool issue 
(uggggh...).

Original comment by david.g.hoyt on 14 May 2009 at 3:57

[GoogleCodeExporter]

I created a branch to add libnice support using MSVC because the amsn team 
needs it.
I updated libnice and tryed to compile it with mingw using your patches with no
results... so I used MSVC. If we cannot compile it using Mingw, we should use 
MSVC
BTW, to get the shared libs you need to set 'LDFLAGS="$LDFLAGS -no-undefined' 
when
calling ./configure (refer to faac compilation in Build-All-Windows)

Original comment by ylatuya on 11 Jul 2009 at 5:12

[GoogleCodeExporter]

Fixed, isn'it?

Original comment by ylatuya on 28 Oct 2009 at 3:49

• Changed state: Fixed