Closed GoogleCodeExporter closed 9 years ago
Sounds fine as long as we're explicit about what's GPL. I'd get the LGPL
version
down pat before we add the GPL libs, though.
We'll also want to create several installer (MSI), tarballs, etc. that
represent
binary-only (dlls), dev-only (libs, dlls, and headers), full dev (includes all
plugin libs), and equivalents for linux, mac, etc. Then do it again for GPL.
Original comment by david.g.hoyt
on 5 May 2009 at 3:33
The LGPL version should be ready once I finish to integrate the farsight2's nice
transmitter and the Python Bindings.
I'll start with the Windows installers as soon as I finish with the python
bindings.
Do you think it's useful to work on the Linux packages? The problem with
GStreamer is
not on the Linux side, as all the GNU/Linux distributions provide packages for
GStreamer and it's quite easy to compile GStreamer from the sources on Linux.
I think we should focus on Windows and Mac, where GStreamer is really lacking a
build
system.
Original comment by ylatuya
on 5 May 2009 at 9:57
I prefer to keep the linux stuff because it's useful for me. I have systems
where I
have to install gstreamer and know (for security purposes) which versions of
which
libraries I'm using. These systems are also not connected to the Internet and
don't
have local mirrors to receive updated libs.
Original comment by david.g.hoyt
on 5 May 2009 at 5:15
Ok, I didn't know you where using it.
Original comment by ylatuya
on 6 May 2009 at 1:02
I think this has been resolved satisfactorily.
Original comment by david.g.hoyt
on 8 Jul 2009 at 8:03
Original issue reported on code.google.com by
ylatuya
on 2 May 2009 at 6:54