Re: [Mesa-dev] CVS of Mesa 3.3
the 3.3 development branch is the default and needs no tag. On Thu, 27 Jan 2000, emanuel stiebler wrote: > Hi, > > Just tried to checkout the 3.3 version, but a > > cvs checkout -r mesa_3_3_dev Mesa > > gives me a > > cvs [server aborted]: no such tag mesa_3_3_dev > > What's wrong ? > > cheers & thanks, > emanuel > > > > > ___ > Mesa-dev maillist - [EMAIL PROTECTED] > http://lists.mesa3d.org/mailman/listinfo/mesa-dev > C.J. Beyer [EMAIL PROTECTED] http://styx.phy.vanderbilt.edu/~cj/ ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] SGI Opensources OpenGL! (fwd)
-- Forwarded message --
Date: Wed, 26 Jan 2000 10:39:14 -0600 (CST)
From: Stephen J Baker <[EMAIL PROTECTED]>
Subject: Re: [Mesa-dev] SGI Opensources OpenGL!
On Wed, 26 Jan 2000, C.J. Beyer wrote:
> Well, from reading the licence FAQ...
Which is here BTW:
http://oss.sgi.com/projects/ogl-sample/faq.html
> ... it might answer Gareth Hughes question about that extension:
>
> "Some ways we can work together might include implementations of new
>ARB-specified OpenGL extensions..."
Yep. Although I think they are talking more in terms of sharing the
code for those extensions rather than the specification of the
extension which (I guess) is what Gareth is talking about.
> However, I'd really like to here responces to this comment:
>
> "Based on discussions with some of the active Mesa developers,
>there's a reasonable chance of merging the two together
>into a single reference implementation and driver kit over time."
Someone at SGI once told me that there had been discussions about dumping
SGI's reference implementation in favor of Mesa - but that was a LONG time
ago - before OpenGL 1.2 and the optional imaging subset stuff (which Mesa
doesnt implement - but the reference implementation must).
It would be kinda ironic if the one implementation of the OpenGL API that
isn't allowed to be called OpenGL would end up being the reference
implementation!
I have a couple of comments (now I've read the FAQ):
1) They mention that this release does not include the dynamic code
generation rasterizer that's in SGI's OpenGL for Windoze.
That's a shame because that could have benefitted software-only
rendering under Mesa.
2) It *does* include the optional imaging subset of OpenGL 1.2 - which
would be a nice addition to Mesa.
3) To quote the FAQ:
"Do I still need a license for OpenGL? Yes"...
So, if I read this right (and IANAL), if you take this code and do something
to it, you *still* can't call it OpenGL. That's actually pretty reasonable
because you'd still need to pass the conformance test suite and that's *still*
not OpenSourced.
Later on they say:
"...we allow you to use the following exact attribution (no more,
no less) in your software products that are based on this
Sample Implementation:
This software was created using the published OpenGL® version
1.2.1 Sample Implementation, but has not been independently
verified as being compliant with the OpenGL®1 version 1.2.1, GLU
version 1.3, or GLX version 1.3 Specifications."
...well, at least it's made crystal clear what you have to do to
stay legal.
The big favor I'd like to ask of SGI is whether they'd release the
compliance suite for public use (not necessarily as "Open" or as
"Source" - there might be good reasons not to do that).
Whilst that wouldn't change the use of the OpenGL *name*, it would allow
Joe Public to test SquonkGL ("...created using the published OpenGL..")
to see if it is still "an implementation of the OpenGL API".
Given the potential for this newly freed code to create multiple Mesa-like
"implementations of the OpenGL API" (we need a non-copyrighted name for
those things), it would be nice to have a reasonably official way
to test them for yourself against the gold standard.
I appreciate that there is already a partial freeware "test"
suite (GLEAN), it's still FAR from being a comprehensive test
harness.
Steve Baker(817)619-2657 (Vox/Vox-Mail)
Raytheon Systems Inc. (817)619-2466 (Fax)
Work: [EMAIL PROTECTED] http://www.hti.com
Home: [EMAIL PROTECTED] http://web2.airmail.net/sjbaker1
___
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] SGI Opensources OpenGL!
Well, from reading the licence FAQ it might answer Gareth Hughes question about that extension: "Some ways we can work together might include implementations of new ARB-specified OpenGL extensions..." However, I'd really like to here responces to this comment: "Based on discussions with some of the active Mesa developers, there's a reasonable chance of merging the two together into a single reference implementation and driver kit over time." Have they talk to you about it Brian? Or are you at liberty to discuss it? What kind of "time" are we talking about and how does this relate to getting an "official" OpenGL implementation branding? On Wed, 26 Jan 2000, Stephen J Baker wrote: > So, what does this: > >http://www.quicken.com/investments/news/story/pr/?story=/news/stories/pr/2126/sfw052.htm&symbol=SGI > ...mean for the future of Mesa? C.J. Beyer [EMAIL PROTECTED] http://styx.phy.vanderbilt.edu/~cj/ ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] automake fix & questions
The way I read the libtool manual (http://www.profitpress.com/libtool/) you are trying to do exactly what libtools tells you not to do because it is "an abuse that only fosters misunderstanding of the purpose of library versions." That is, trying to assign the library version to the software release version. Personally I like the scheme you decided on, but aparantly libtools doesn't agree. On Tue, 16 Nov 1999, Brian Paul wrote: > [EMAIL PROTECTED] wrote: > > > I read a bit in libtool.info an _I_ think we should switch from > > "-version-info" to "-release", which might not be "the right thing > > to do" but at least we stay compatible with the older scheme. > > Mesa (not to say other libGl's we wanna be compatible to) was not > > developed with libtools understanding of "library versions". > > > > So changing > > libglut_la_LDFLAGS = -version-info $(LIBGLUT_VERSION) > > to > > libglut_la_LDFLAGS = -release $(LIBGLUT_VERSION) > > > > and defining LIBGLUT_VERSION = 3.7.x in configure.in > > (x = Mesa version) > > > > Same for libglu and libGL. > > > I tried this. No go. Using -release, if LIBGLUT_VERSION > is x.y.z then you get a file named libGL-x.y.z.so instead > of libGL.so.x.y.z > > I spent some time wrestling with automake to make it generate > the libnames I want. What a $!%@#$& headache! > > In configure.in suppose you set LIBGL_VERSION=C:R:A where C=current, > R=revision and A=age. Then the library file will be named > libGL.so.M.A.R where M = C - A. And that's just for Linux! The > naming method/computation is different of other OS's! I don't > understand the logic behind this. As it is now, I don't know what > version numbers will result on other OS's. > > The best I could manage (for Linux) is to make libGL.so.1.2.0 with > LIBGL_VERSION=3:0:2, libGLU.so.1.2.0 with LIBGLU_VERSION=3:0:2 and > libglut.so.3.7.0 with LIBGLUT_VERSION=10:0:7 > > Thomas Tanner originally contributed the automake support but doesn't > appear to me reading the list anymore. If anyone else can explain > what's going on I'd appreciate it. > > -Brian > > > ___ > Mesa-dev maillist - [EMAIL PROTECTED] > http://lists.mesa3d.org/mailman/listinfo/mesa-dev > C.J. Beyer [EMAIL PROTECTED] http://styx.phy.vanderbilt.edu/~cj/ ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Using CVS
Hey people. I updated the developers section of the webpage to reflect the new branching scheme. I also updated the lxr tree so you can browse the different branches via the web. Cowabunga dewds. C.J. Beyer [EMAIL PROTECTED] http://styx.phy.vanderbilt.edu/~cj/ ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Back on the list!
> BTW, I noticed that the CVS archives have changed since I last logged > on. I pulled down all the latest files, but they ended up under the > 'Mesa' directory instead of the 'MesaCVS' directory that it used to Well, actaully, in the last archive you created the MesaCVS directory and then checked out the archive into that. In the new archive, Mesa is in a subdir, so we can have other stuff on the archive without having it be a part of Mesa. > be under. I assume this was because of the hardware crash that the > CVS repository suffered? Yeah, we had to rebuild the repository from a cvs checkout because of some hardware failure at VA Linux. They have assured us though that this will never happen again. And in fact they just sent out a note saying they are moving things to a tape backed up RAID array. C.J. Beyer [EMAIL PROTECTED] http://styx.phy.vanderbilt.edu/~cj/ ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] status of MesaCVS.tar.gz
> After unpacking it, i found out, that the content of this file is old, > (newest file is about mid of june). > Is there something wrong with the shell script, which updates this file ? Yeah, thanks for pointing it out. > emanuel C.J. Beyer [EMAIL PROTECTED] http://styx.phy.vanderbilt.edu/~cj/ ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
[Mesa-dev] experimental branch
> Ah, I'd was curious why there'd been no cvs updates in so long! It the > experimental-1 branch where development occurs, then? A note about this > on the website would be helpful! Actually, I was under the impression that the experimental branch was just a temporary thing until Mesa-3.1-beta2 was released. Now that beta2 has been released the development tree is no longer necessary. Keith? C.J. Beyer [EMAIL PROTECTED] http://styx.phy.vanderbilt.edu/~cj/ ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] CVS question+Polygon Offset (fwd)
-- Forwarded message -- From: "Mikl[ISO-8859-1] ós Fazekas" <[EMAIL PROTECTED]> Hello! I think that nightly updates are OK. But I think we should really post discovered bugs/what part of Mesa development we are working into this newsgroup. Btw. Is there anyone working on adding polygon_offset support for FX Mesa. It's used in Quake3. It doesn't seem to hard to implement at all. Any toughs where/how should it implemented? Miklos. ------ >From: "C.J. Beyer" <[EMAIL PROTECTED]> >To: Keith Whitwell <[EMAIL PROTECTED]> >Subject: Re: [Mesa-dev] Bug in clipping code - and CVS question >Date: Thu, Apr 29, 1999, 2:17 PM > > > Keith, > I dont have access to the cvs server. I have a nightly > cron job that notifies Fazekas whenever files are changed, and > which files they are. If you don't think this is sufficient. > I can petition VA research to give me access to the cvs server, > or ask them to to do as you describe. I have a cvs-updates > mailing list, but as I said it only runs nightly. So > is that too slow? > > Anyone else want to comment? > >> CJ Beyer - it is possible to enable CVS to automatically generate email >> to a certain address whenever there is a check-in, by putting a call to > >> Keith > > C.J. Beyer > [EMAIL PROTECTED] > http://styx.phy.vanderbilt.edu/~cj/ > > > > ___ > Mesa-dev maillist - [EMAIL PROTECTED] > http://lists.mesa3d.org/mailman/listinfo/mesa-dev > ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Daily CVS Archive?
Paul, How about ftp://ftp.mesa3d.org/mesa/beta/MesaCVS.tar.gz It will update nightly. On Wed, 28 Apr 1999, Paul Sargent wrote: > Hi all, > > I'm just wondering wether anybody does a daily tar of the CVS repository. > > I ask as I'm behind a firewall so I can't get at the latest code base. Any > suggestions welcolme. > > Paul > > > ___ > Mesa-dev maillist - [EMAIL PROTECTED] > http://lists.mesa3d.org/mailman/listinfo/mesa-dev > C.J. Beyer [EMAIL PROTECTED] http://styx.phy.vanderbilt.edu/~cj/ ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
[Mesa-dev] [mesadev] CVS updates
If anyone wants to be mailed a list of the cvs files that have been updated, just drop me an email. I have a cronjob that runs nightly whos byproduct (if there are any changes) is a list of the patched files. I've attached last night's mail below. C.J. Beyer [EMAIL PROTECTED] http://styx.phy.vanderbilt.edu/~cj/ -- Forwarded message -- Date: Tue, 20 Apr 1999 00:01:48 -0700 From: Cron Daemon <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Cron /home/cjbeyer/cvs.sh P VERSIONS P src/dotprod_tmp.h P src/linetemp.h P src/points.c P src/texture.c P src/vb.c P src/FX/fxdd.c P src/FX/fxvsetup.c ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
cvs src http && license
For your viewing pleasure I've made the cvs src viewable via the web at: http://www.mesa3d.org/lxr/source?v=cvs updated nightly at 12am at PST. Also, just to clarify, the cvs src is still under the gnu license right? Its not the bsd tree that PI has? C.J. Beyer [EMAIL PROTECTED] http://styx.phy.vanderbilt.edu/~cj/
Re: mesa-dev return-path field (was Re: mesa-dev reply-to field)
> > **Can we get mesa-dev messages set up so that replies go to the whole list > > **by default? > But I would like it if the return-path [1] identified the message as coming > from the mesa-dev or mesa-bugs list, much as occurs on the main mesa list. I dont think either of these features are possible currently as the mailing list just uses sendmail aliases since the server doesnt have a list manager like majordomo installed. C.J. Beyer [EMAIL PROTECTED] http://styx.phy.vanderbilt.edu/~cj/
[mesadev] Anon CVS
What is that status of getting anonymous CVS access? C.J. Beyer [EMAIL PROTECTED] http://styx.phy.vanderbilt.edu/~cj/
