There have been many changes to gnash recently. A few examples: 1. Agg is now the default renderer. 2. dev-libs/libxml2 is now required. 3. Option --enable-gui now needs to be set or it will build both gtk and kde. 4. emake under src_install() now needs to be set to emake -j1 or it will crash during the install process. I will be attaching and ebuild that addresses these problems and more. But it is considerably different from the current one so you may not want to use it. That's ok I built it for myself. Harley
Created attachment 126665 [details] Example ebuild to fix recent cvs changes to Gnash. This is the ebuild that I currently use with Gnash cvs. There have been some changes to the USE flags. IF no USE flags are set it should build with the Gnash defaults with the exception of the plugins which are disabled unless set with there use flags. I need somebody to test whether the klash plugin works with the agg renderer. I don't have any computers with kde installed. I know it compiles ok. Harley
Created attachment 126711 [details] Example ebuild to fix recent cvs changes to Gnash. Fixed the condition when no gui USE flag is set to default to gtk only rather than the Gnash default of both gtk and kde. Harley
Comment on attachment 126711 [details] Example ebuild to fix recent cvs changes to Gnash. Major changes in cvs for the plugins last night. Making this ebuild obsolete after about 12 hours. :( Haven't had a chance to look at the new code yet but will post a revised ebuild when i can. Harley
Created attachment 126818 [details] Example ebuild to fix recent cvs changes to Gnash. Recent changes: -enable-plugin removed --disable-klash replaced with --disable-kparts --disable-nsapi added Nsplugin will no longer build with the kde gui it was disabled. Don't know why it worked fine.
Comment on attachment 126818 [details] Example ebuild to fix recent cvs changes to Gnash. Yet more changes. :(
Created attachment 126831 [details] Example ebuild to fix recent cvs changes to Gnash. The latest changes to cvs: nsplugin will build only with gtk gui. klash plugin will build only with kde gui. The ebuild has been changed to reflect this. Harley
Created attachment 132198 [details] Proposed example ebuild. Added support for the cairo renderer. Added support for the konqueror use flag to more closely match the proposed 0.8.1 ebuild. Didn't add the xml use flag as it is required by gnash and is not an option. Added parallel compile support. Enabled by default with the ability to disable it with the WANT_MP="false" setting put in make.conf or from the command line. Harley
Created attachment 133829 [details] Proposed example ebuild. 1. Added new use flags: cygnal, debug, gnome and parallel. Cygnal enables flash server support. Debug enables flash debugging support. Gnome enables gnome help support. Parallel enables parallel compiling support. 2. Tested the Gnash dependencies in a clean chroot environment and made changes were appropriate. 3. Added more package setup checks in order to simplify the dependency layout. 4. Cleaned up and made changes to the source compile options.
Created attachment 133835 [details] Proposed ebuild. For got to add the X dependencies. These are really sub dependencies but Gnash won't build if there missing.
Created attachment 133916 [details] Proposed ebuild. Added check for invalid cairo kde combination.
Created attachment 134183 [details] Final proposed ebuild. Added the ability to use the mad media handler and also to build without a media handler at all. The media handler is needed only for video and audio. Added the fb and sdl gui's. This will allow somebody to build a stand alone player with less dependencies. Neither of these gui's supports plugins. Unable to add the fltk gui as it requires fltk2 which is not in portage. Added the ability to enable disable the mit-shm X extension. Fixed a bug with the pkg_setup detection of nsplugin and !gtk. This is my last posting of proposed ebuilds as i am getting tired of talking to myself :) If anybody wants access to any future gnash cvs ebuilds by me i have made them available via a layman overlay. Instructions for accessing the overlay can be found at http://www.thepetersclan.com Harley
I get this when trying to add your overlay... gentoo ~ # layman -a gnash-cvs * Running command "/usr/bin/rsync -rlptDvz --progress --delete --delete-after --timeout=180 --exclude="distfiles/*" --exclude="local/*" --exclude="packages/*" "rsync://gnash.biterror.net/gnash-cvs/" "/usr/portage/local/layman/gnash-cvs""... @ERROR: access denied to gnash-cvs from ############## rsync error: error starting client-server protocol (code 5) at main.c(1386) [receiver=2.6.9] * Failed to add overlay "gnash-cvs". * Error was: Adding the overlay failed!
(In reply to comment #12) > I get this when trying to add your overlay... > > gentoo ~ # layman -a gnash-cvs > * Running command "/usr/bin/rsync -rlptDvz --progress --delete --delete-after > --timeout=180 --exclude="distfiles/*" --exclude="local/*" > --exclude="packages/*" "rsync://gnash.biterror.net/gnash-cvs/" > "/usr/portage/local/layman/gnash-cvs""... > > @ERROR: access denied to gnash-cvs from ############## > rsync error: error starting client-server protocol (code 5) at main.c(1386) > [receiver=2.6.9] > * Failed to add overlay "gnash-cvs". > * Error was: Adding the overlay failed! > Sorry had the rsync server restricted to the lan for got to change it. Should work now. Harley
Works now, thanks=)
Why does the ebuild claim that mad is audio-only? I have just built gnash with mad as a media handler and it can display audio and video in swf animations. I believe that when the README says that mad is "MP3 audio decoding only", it is saying that with the mad media handler you cannot play other kinds of *audio*, only MP3. I think that the media handler handles only the audio...
(In reply to comment #15) > Why does the ebuild claim that mad is audio-only? I have just built gnash with > mad as a media handler and it can display audio and video in swf animations. > > I believe that when the README says that mad is "MP3 audio decoding only", it > is saying that with the mad media handler you cannot play other kinds of > *audio*, only MP3. > > I think that the media handler handles only the audio... > (In reply to comment #15) > Why does the ebuild claim that mad is audio-only? I have just built gnash with > mad as a media handler and it can display audio and video in swf animations. > > I believe that when the README says that mad is "MP3 audio decoding only", it > is saying that with the mad media handler you cannot play other kinds of > *audio*, only MP3. > > I think that the media handler handles only the audio... > Mad is an audio only decoder. When i mean it can't display video i mean real video like at youtube.com Normal flash animation works fine even without a media handler at all. Harley
(In reply to comment #16) > Mad is an audio only decoder. > When i mean it can't display video i mean real video like at youtube.com > Normal flash animation works fine even without a media handler at all. I built gnash without a media handler and I can play swf files but with no sound. In any event, saying that mad is "audio only" is misleading. It makes it seem that if I build gnash with mad I will have only audio, which is not true (I can play swf animations with opengl/agg and mad). > > Harley >
(In reply to comment #17) > (In reply to comment #16) > > > Mad is an audio only decoder. > > When i mean it can't display video i mean real video like at youtube.com > > Normal flash animation works fine even without a media handler at all. > I built gnash without a media handler and I can play swf files but with no > sound. > > In any event, saying that mad is "audio only" is misleading. It makes it seem > that if I build gnash with mad I will have only audio, which is not true (I can > play swf animations with opengl/agg and mad). > > > > Harley > > > I would still have some sort of warning message. Other wise people will be complaining that they can't play (real) video. Feel free to modify the warning message or anything else with the ebuild. Harley
thank you very much. I have added your overlays to layman-global.txt and canged the in-portage ebuild to a stub to point to your overlay!
