Greg Stacey wrote:
Not to be a pest, but if this is ok can someone commit it to 130?
I see it's been CR'd for 130NepX. I checked it in for you.
I believe it's already in 150Cay. Which build branch would confirm that?
Building player_all from realplay_gtk_current pulls 150Cay.
Looking at CVS, looks to me like it into HEAD last September before the cayenne branch, and got picked up when 150Cay got branched.
I checked the realplay_gtk_current bif file and it has <inherit id="hxclient_1_5_0_cayenne"/> <cvs root="helix"/> <cvs tag="HEAD"/>
Does that mean it is 150? Or is it HEAD? The hxclient_1_5_0_cayenne is a client only (no player) build right?
The player module (stuff under $BUILD_ROOT/player) gets pulled from HEAD, the client gets pulled from 150Cay.
hxclient_1_5_0_cayenne.bif defines a player from the cayenne branch. realplay_gtk_current builds on this by adding player modules from HEAD.
Thanks,
Greg Stacey
Principal Consultant
Advanced Technologies Integration
-----Original Message----- From: Greg Wright [mailto:[EMAIL PROTECTED] Sent: Friday, April 15, 2005 1:21 PM To: Greg Stacey Cc: 'Nicholas Hart'; [EMAIL PROTECTED] Subject: Re: [Audio-dev] CR-Client: HP audio
Greg Stacey wrote:
So... what's the consensus? Can this go into 130?
Yes, I think that is fine. Don't ignore the other branches though. You will want it in 150Cay if it isn't there already. That way it will be in whatever branch the linux player moves to next.
--greg.
Greg Stacey Principal Consultant Advanced Technologies Integration
-----Original Message----- From: Nicholas Hart [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 12, 2005 3:59 PM To: Greg Wright Cc: Greg Stacey; [EMAIL PROTECTED] Subject: Re: [Audio-dev] CR-Client: HP audio
I don't see any reason we can't commit to nepx130 as long as the scope is limited to hpux.
On Tue, 2005-04-12 at 13:27, Greg Wright wrote:
Greg Stacey wrote:
Can this be merged into the 130 branch? Or is that "locked down" now? I was hoping to get a
stable HPUX build off the 1.0 Helix
release if possible, while working on getting the 2.0 release down the road.
what diffs are required for a stable HPUX release off of 130NepX? If it is only these audio changes, which are #ifdef for HPUX only, then I don't see why not. If there are going to be more changes then we would have to look at them as a whole.
--greg.
_______________________________________________Thanks,
Greg Stacey Principal Consultant Advanced Technologies Integration
-----Original Message----- From: Greg Wright [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 12, 2005 12:22 PM To: Greg Stacey Cc: [EMAIL PROTECTED] Subject: Re: [Audio-dev] CR-Client: HP audio
So what branch are you asking this be merged to? It appears to have already been merged to 150Cay.
--greg.
Greg Stacey wrote:
In consideration for RealNetworks' hosting and maintenance of my modification, I agree to assign to RealNetworks full copyright ownership of the code included in the attached patch, and agree that RealNetworks has no duty of accounting to me for it. I warrant that this code is entirely original to and owned by me, that I can legally grant the copyright assignment, and that my contribution does not violate any other person's rights, and laws or breach any contract. I understand that RealNetworks may license this code under RPSL, RCSL, and/or any other license at RealNetworks' discretion, and use the code in any way.
Modified by: Greg Stacey [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Date: April 12, 2005
Synopsis / Overview: This is actually a resubmission. When I originally submitted this patch is was committed to HEAD and I thought it was going to be committed to stable but that never happened. It's a couple of build fixes for HP audio affecting HP specific files and a #ifdef HPUX section in math64.h.
Greg Stacey
Principal Consultant
Advanced Technologies Integration
------------------------------------------------------------------------
_______________________________________________
Audio-dev mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/audio-dev
Audio-dev mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/audio-dev
-- Nicholas Hart [EMAIL PROTECTED] Technical Lead, Helix Player https://player.helixcommunity.org http://www.real.com
_______________________________________________ Audio-dev mailing list [email protected] http://lists.helixcommunity.org/mailman/listinfo/audio-dev
-- Ryan Gammon [EMAIL PROTECTED] Developer for Helix Player https://player.helixcommunity.org
_______________________________________________ Audio-dev mailing list [email protected] http://lists.helixcommunity.org/mailman/listinfo/audio-dev
