From: Christian F. K. S. <Ur...@li...> - 2001-12-17 17:11:42
|
Hi people, In order to speed up development even more we are now adopting a new Fast Forward (tm) development model. It will enable us to move ahead faster. The first decision made using this model is that we will standarize on gst and our directory and application prefix. This means CVS and appname will be set/changed to the following: gst-core gst-plugins gst-gui gst-bind gst-launch gst-mediaplay gst-guilaunch If you have objections to this screem now or be forever ignored. Christian |
From: Erik W. <om...@te...> - 2001-12-17 20:59:24
|
On 17 Dec 2001, Christian Fredrik Kalager Schaller wrote: > This means CVS and appname will be set/changed to the following: > gst-core > gst-plugins > gst-gui > gst-bind > > gst-launch > gst-mediaplay > gst-guilaunch > > If you have objections to this screem now or be forever ignored. OK, here's what thomasvs, wingo, and I worked out in IRC just now: gst-core/ gst/ libgst.so {headers} autoplug/ ...so {headers} schedulers/ ...so {headers} libs/ gst/ launch/ libgstlaunch.so gstlaunch.h bytestream/ libbytestream.so gstbs.h bitstream/ [?] test/ docs/ tools/ -complete -compprep -register -inspect -launch [1] -register gst-player/ libgstplay/ libgstplay.so {headers} src/ gstmediaplay gst-bind/ swig/ ... gst-editor/ libgsteditor/ libgsteditor.so {headers} src/ gst-editor gst-guilaunch Notes: 1: remove X dep from launch by adding xvideosink toplevel=1 Some specific names, like gst-player, are still debatable, but we've worked out some details that should make life easier. Specifically: 1) keep various data-agnostic libs into the core, but add a gst/ directory in the middle to aid with include files, i.e. so both app code and headeres in gst-core can use #include <gst/$libname/...> 2) remove the X dependency from launch so it can stay in the core. this has to be done with a mod to any videosink that requires a toplevel directory, so it can create its own 3) putting guilaunch into the -editor module, becuaase so much is shared (or should be) between those two programs. Moved the library into gst-editor/libgsteditor/, and put both the applications (gst-editor and gst-guilaunch) into a src/ directory. Erik Walthinsen <om...@te...> - System Administrator __ / \ GStreamer - The only way to stream! | | M E G A ***** http://gstreamer.net/ ***** _\ /_ |
From: Arik D. <ad...@an...> - 2001-12-17 23:22:43
|
gst-player is kinda lame but it's better then gst-mediaplayer the libgstplay / src change doesn't bother me, i think it's a good idea cause i want (eventually) other projects like mozstreamer to use libgstplay as well. arik |
From: Thomas V. S. <th...@ur...> - 2001-12-20 11:44:53
|
Hey omega, I was planning to work on gst-editor since that seems settled for the most, but I had some questions for you to decide on before I can : > gst-core/ > gst/ > libgst.so > {headers} > autoplug/ > ...so > {headers} > schedulers/ > ...so > {headers} > libs/ > gst/ > launch/ > libgstlaunch.so > gstlaunch.h > bytestream/ > libbytestream.so > gstbs.h > bitstream/ [?] Where does the actual source code go for the libs in this case ? Also, is it useful to heave the headers in separate subdirs ? Won't that end up with each gstreamer header in it's separate header dir in prefix/gst ? Should we also take this opportunity to rename either gstbs.h to gstbytestream.h or bytstream.h ? > gst-player/ > libgstplay/ > libgstplay.so > {headers} Just to keep it in sync with the core, I'd change libgstplay to libs/gstplay, unless I read the core wrong. If we call the main gst header and dir gst/gst.h, it should be gstplay/gstplay.h for the player. Also, here again, is there a good reason to put it in gstplay/ and not in gst/ ? I'm just not sure atm what headers are going to end up in gst/ . If it's only one, then the use for the separate dir is limited. So I just wanted to bring it up since I know you have more experience with this sort of thing. > gst-editor/ > libgsteditor/ > libgsteditor.so > {headers} > src/ > gst-editor > gst-guilaunch Same thing here. I'm sorry for the trouble I've caused this week and I hope we can get everything sorted out by the weekend. Thomas The Dave/Dina Project : future TV today ! - http://davedina.apestaart.org/ <-*- -*-> and it's moving so fast slow down honey <-*- th...@ap... -*-> URGent, the best radio on the Internet - 24/7 ! - http://urgent.rug.ac.be/ |
From: Arik D. <ad...@an...> - 2001-12-20 12:40:05
|
> Just to keep it in sync with the core, I'd change libgstplay to > libs/gstplay, unless I read the core wrong. > If we call the main gst header and dir gst/gst.h, it should be > gstplay/gstplay.h for the player. Also, here again, is there a good > reason to put it > in gstplay/ and not in gst/ ? I'm just not sure atm what headers are going > to end up in gst/ . If it's only one, then the use for the separate dir > is limited. So I just wanted to bring it up since I know you have more > experience with this sort of thing. i'm not sure i understand this, but what i seem to understand i don't think i like. moving libgstplay from gstplay/src to gstplay/gstplay i can handle but you want gstplay/libs/gstplay/ or you want libgstplay under gst/? moving things to dirs is a good idea if it makes things more clear. there is nothing in your proposal that makes sense to me when applied to gstplay, noone is going to be confused about what libs they need for gstplay and the build system doesn't use gst's configure.ac at all right now anyway cause i'm in my own module. basically i'm gonna need alot better understanding of all this before any change to gstplay happens :-) thanks, arik |
From: Thomas V. S. <th...@ur...> - 2001-12-20 13:03:42
|
> > in gstplay/ and not in gst/ ? I'm just not sure atm what headers are going > > to end up in gst/ . If it's only one, then the use for the separate dir > > is limited. So I just wanted to bring it up since I know you have more > > experience with this sort of thing. > > i'm not sure i understand this, but what i seem to understand i don't > think i like. moving libgstplay from gstplay/src to gstplay/gstplay i > can handle but you want gstplay/libs/gstplay/ or you want libgstplay > under gst/? Hey arik, well the main thing was discussed on irc. Omega told me that whatever you do, you need to have a dir called gst/ with the headers in it if you want to be able to compile both internally with them as well as externally. This is because external programs will use #include <gst/gst.h>, and internal programs should do this too, and this only works if in your source tree you also have a gst/ dir with gst.h in it. That seems to make sense to me. So my idea, which omega liked, was that we put it in libs/gst and for uninstalled gstreamer/internal compilation you just add the -L$(top_srcdir)/libs flag, so that it works for everyone. I was only wondering if this reasoning should be carried over to the other modules as well, and that's up for you and others to decide because atm I have no idea if these header files are meant to be installed system wide. So I guess that's what I was asking ;) BTW anyone who feels like taking on this part of the split up, please do ;) I think I'm not familiar enough with all the issues involved here. I do want to help if I can though. Thomas The Dave/Dina Project : future TV today ! - http://davedina.apestaart.org/ <-*- -*-> Smelled you on my hand for days I can't wash away your scent I'm a dog and you're a bitch <-*- th...@ap... -*-> URGent, the best radio on the Internet - 24/7 ! - http://urgent.rug.ac.be/ |