search

geysee / ossbuild

Automatically exported from code.google.com/p/ossbuild
Other
0 stars 0 forks source link

WinBuilds 0.10.7 release #49

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
New upstream releases are comming!
I'll take care of updating all the gstreamer modules in the next week.
We should start thinking on the next release :)

Original issue reported on code.google.com by ylatuya on 27 Jun 2010 at 8:30

GoogleCodeExporter commented 9 years ago 
We want to get this release out the door and then we'll be doing a sync soon 
after that.

Original comment by david.g.hoyt on 23 Mar 2011 at 8:30

GoogleCodeExporter commented 9 years ago 
any schedule? we've got a lots of problems with rtsp on windows and we'd like 
to test the last upstream with ossbuild, but your current svn is not 
up-to-date...

Original comment by lfar...@gmail.com on 23 Mar 2011 at 8:37

GoogleCodeExporter commented 9 years ago 
For those interested, you can see what we're working on over at github: 
https://github.com/ossbuild/

Until we're done w/ our major reworking, we'll continue to do releases using 
our current system. In the future, however, we'll be doing builds using msys, 
mingw, and gcc. Trying to maintain the MSVC projects is painful. We're using 
jhbuild for most everything to keep the build experience as painless as 
possible. I created a *very* preliminary installer that sets up your 
environment so you can see where we're headed with things. The windows build 
env (ossbuild-build-env-v1.0.0-beta00-preview-00.exe) is available at: 
http://www.yourfilelink.com/get.php?fid=622586

The idea, eventually, is to create a package management system. We'll start w/ 
a command line app and move to a GUI down the line (hopefully). But for now, 
we're just getting the basic system setup and builds started. x86 and x64 
builds are expected.

Original comment by david.g.hoyt on 23 Mar 2011 at 8:41

GoogleCodeExporter commented 9 years ago 
wouldn't be better to create a mailing list on google for easier communication 
than talking through issues?

Original comment by vitorl...@gmail.com on 28 Mar 2011 at 10:30

GoogleCodeExporter commented 9 years ago 
any progress with a new build?
anyway as it'll be a new upstream release about this week do you plane to 
update the current ossbuild source?
do you push all source and patch to upstream?
ie. if we update ourself the ossbuild source tree with upstream will it work?
how can we help to merge the upstream and ossbuild tree?
regards.

Original comment by lfar...@gmail.com on 26 Apr 2011 at 9:26

GoogleCodeExporter commented 9 years ago 
The major blocker here has been time -- things at work have been keeping me 
extremely busy these past few months. There's only 2 of us really actively 
working on the project right now. We'd love some help. If you want to join, let 
me know so I can add you to the project.

We'll be updating as soon as our release goes out (v0.10.7). I may just call 
our latest beta complete and move on.

Original comment by david.g.hoyt on 26 Apr 2011 at 2:57

GoogleCodeExporter commented 9 years ago 
may be this move on can help a lot...

Original comment by lfar...@gmail.com on 26 Apr 2011 at 3:01

GoogleCodeExporter commented 9 years ago 
any move on this?

Original comment by lfar...@gmail.com on 6 May 2011 at 8:15

GoogleCodeExporter commented 9 years ago 
as there is a new upstreamer release it'd be useful to make the latest beta as 
release and update the ossbuild svn to the latest upstream git...
anyway from the next week we try to find some time for one of our programmer to 
fix the network issues...

Original comment by lfar...@gmail.com on 14 May 2011 at 2:52

GoogleCodeExporter commented 9 years ago 
I'd be interested in getting the ossbuild project moving forward. Can you 
summarize the current state and what needs to be worked on? It's not easy to 
tell just looking at the code in GitHub.

Original comment by joshthep...@gmail.com on 5 Dec 2011 at 8:25

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[Windows 7] I just installed this release and I can't get udp elements to work 
(udpsrc/sink). I'm guessing it's a firewall issue, but I already enabled all 
UDP ports on this application and even disabled the whole firewall to test. 
Anyone has had some related problem?

My test is:

Sending: GST_DEBUG=3 gst-launch -v autoaudiosrc ! udpsink host="127.0.0.1" 
port=3000

Receiving: GST_DEBUG=3 gst-launch -v udpsrc host="127.0.0.1" port=3000 ! 
fakesink dump=1

Original comment by andre.d...@gmail.com on 25 Jan 2012 at 4:18

GoogleCodeExporter commented 9 years ago 
It does not work because Windows version is not well managed, it has bug with 
Windows 7 and 8. You are doing somewhere else wrong, to fix it you can try the 
default one from Windows.

Original comment by shamun.toha@gmail.com on 25 Jan 2012 at 4:23

GoogleCodeExporter commented 9 years ago 
I'm sorry I didn't follow. Is my pipeline wrong, there is a bug on udp or both?

What do you recommend me to try?

Thank you

Original comment by andre.d...@gmail.com on 25 Jan 2012 at 6:20

GoogleCodeExporter commented 9 years ago 
Nevermind. Problem was to use host="localhost" instead of 127.0.0.1, which I 
think triggers this bug: https://bugzilla.gnome.org/show_bug.cgi?id=534243.

Original comment by andre.d...@gmail.com on 28 Jan 2012 at 7:32