On Fri, Aug 08, 2003 at 02:21:28AM -0400, David Dawes wrote: > On Fri, Aug 08, 2003 at 06:41:58AM +0200, Sven Luther wrote: > >On Thu, Aug 07, 2003 at 04:52:02PM -0400, David Dawes wrote: > >> On Wed, Jul 30, 2003 at 06:50:28PM -0400, George Georgalis wrote: > >> >On Tue, Jul 29, 2003 at 11:59:06PM -0400, David Dawes wrote: > >> >>On Tue, Jul 29, 2003 at 09:37:06PM -0400, George Georgalis wrote: > >> >>> > >> >>>I heard (second hand from via) that xfree86 2.3.99 has drivers > >> >>>for the CLE266 ( http://www.via.com.tw/en/apollo/cle266.jsp on a > >> >>>http://www.viavpsd.com/product/epia_m_spec.jsp?motherboardId=81 ) > >> > > >> >I got the cvs source this morning and it built without errors on my fast > >> >box. It's been compiling (for a while now) on the hardware I plan to > >> >run it from. I assume all will be okay. > >> > > >> >Here's my next question. After poking around in the source I found > >> >./programs/Xserver/hw/xfree86/drivers/via/ > >> > > >> >Lots of good stuff in that directory for making the CLE266 work... only > >> >how do in invoke it and confirm it's being run? It's confusing to me > >> >how a program (eg mplayer) would know to use xfree (and the cle266) for > >> >mpeg-2 decoding and not just do the decoding on its own. > >> > > >> > > >> >>4.3.99.9 has a known build problem (which you're seeing). Either try > >> >>4.3.99.8, or get the latest code via anoncvs. > >> > > >> >Humm, a README in that directory could contain note to that effect? > >> >or the changelog could be reissued for that file? Thanks for the fast > >> >responce anyhow. > >> > >> These are automatically generated code snapshots and nothing more. If > >> you look at <http://www.xfree86.org/develsnaps/> you'll see that there > >> is "no guanrantee that any given snapshot will build or run." > >> > >> >BTW - how do I tell what version of cvs I got? > >> > >> Assuming you checked out the trunk (which is the default), you got the > >> lastest development code as of the time you checked it out. The version > >> is "something later than the previous snapsnot". > > > >What about marking the version as 4.3.99.x for the snapshot, and once it > >is released, mark the version as 4.3.99.x+ or 4.3.99.x+<co date> for the > >CVS versions, until a new snapshot is taken. Maybe it could only be done > >in the XFree86.0.log output code, and not the actual version be changed. > > I usually update the date in xf86Date.h when committing. That > gives some indication, and is printed on the line after the version > in the log file. > > I don't think it matters that much personally, but if I wanted to > achieve something like this for my own checkouts, I'd use a script > that did something like this: > > #!/bin/sh > date=`date` > cvs co xc > echo "#undef XFree86CustomVersion" >> xc/config/cf/host.def > echo "#define XFree86CustomVersion \"$date\"" >> xc/config/cf/host.def > > I'm not sure how you'd make cvs automatically create a reliable > date for all possible ways of checking out the source.
Using a CVS date variable or something such, which the XFree86CustomVersion would be set to when taking it out of CVS, and which you would remove before doing the snapshots ? Friendly, Sven Luther _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
