Re: [Mesa-dev] 3dnow and g200
On Mon, 7 Jun 1999 14:04:49 -0700, Keith Whitwell wrote: >Can't we have a prebuilt ./configure in the repository? This is generally considered to be a Bad Idea, since configure is autogenerated code and it's easy to forget to update it before checking in changes (and it wastes space). The general model is for the cvs developers to install autoconf and friends; configure *is* included in any source distributions so others can use that. 'make dist' then takes care of keeping it up-to-date. That said, I've included configure in the glx module cvs. :) We're maintaining a dual build system (autoconf and a menuconf script+imake) and I thought that was the best way to get people to test. Also, cvs is our only source distribution method at the moment. The expectation is we'll take it out when more people are using it/we start making snapshots available. Just my 0.08 bits, -ralph --- Please cc me on replies, I'm only pretending to be on the list. [EMAIL PROTECTED] ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] 3dnow and g200
On Mon, 7 Jun 1999 [EMAIL PROTECTED] wrote: > On Mon, 7 Jun 1999 14:04:49 -0700, Keith Whitwell wrote: > > >Can't we have a prebuilt ./configure in the repository? > > This is generally considered to be a Bad Idea, since configure is > autogenerated code and it's easy to forget to update it before checking > in changes (and it wastes space). The general model is for the > cvs developers to install autoconf and friends; configure *is* included > in any source distributions so others can use that. 'make dist' then > takes care of keeping it up-to-date. > False. A prebuilt script is a good idea, - at this time I can't create it on my own, since my autoconf is too old. It should be no problem to run a script on the CVS-Server at every checkin, which generates a new configure file. The g200 people implemented something like this to forward a mail to their dev-list with the commit-log. I don't know, if everybody is allowed to install this script, possibly Rob or Brian have to do this. - Holger ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] 3dnow and g200
On Tue, 8 Jun 1999, Holger Waechtler wrote: > > > On Mon, 7 Jun 1999 [EMAIL PROTECTED] wrote: > > > On Mon, 7 Jun 1999 14:04:49 -0700, Keith Whitwell wrote: > > > > >Can't we have a prebuilt ./configure in the repository? > > > > This is generally considered to be a Bad Idea, since configure is > > autogenerated code and it's easy to forget to update it before checking > > in changes (and it wastes space). The general model is for the > > cvs developers to install autoconf and friends; configure *is* included > > in any source distributions so others can use that. 'make dist' then > > takes care of keeping it up-to-date. > > > > False. > > A prebuilt script is a good idea... I disagree. We should keep configure.in and Makefile.am in the repository but only deliver configure itself with distributions. IMHO, repositories should contain the ultimate sources for things and nothing else. We don't want some misguided person fixing a configuration problem by editing 'configure' and putting it into the repository, only to have it ignored the next time someone runs autoconf. > ...at this time I can't create it on my > own, since my autoconf > is too old. If your autoconf is too old - and you are a developer - just download the new one - it's free and it won't take but 10 minutes to get it up and running. 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] 3dnow and g200
On 08-Jun-99 Holger Waechtler wrote: > A prebuilt script is a good idea, - at this time I can't create it on my > own, since my autoconf is too old. Upgrade! You're a developer. > It should be no problem to run a script on the CVS-Server at every > checkin, which generates a new configure file. The g200 people implemented > something like this to forward a mail to their dev-list with the > commit-log. That are two different things: reporting changes to a mailing list is done by calling a script, which must be listed in CVSROOT/loginfo. It's called for _every directory_ you commit something to. Such a CVS-commit mailing list for Mesa would be a good thing, however. If you want to call a script for every checkin you have to add it to CVSROOT/modules and that'd require all users to recheckout the whole Mesa tree. But it's not necessary, anyway. Thomas Tanner - email: tanner@(ffii.org|gnu.org|ggi-project.org|gmx.de) web: http://home.pages.de/~tanner GGI/Picasso: http://picasso.ffii.org ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] 3dnow and g200 [was: headers for src/asm_mmx.c]
Holger Waechtler wrote: > > On Mon, 7 Jun 1999, Keith Whitwell wrote: > > > > > I think a better approach would be to compile everything > > we are capable of & do the checks at runtime. > > That's exactly the thing I want to do. The linux-3dnow target is currently > the one which compiles in all available optimisations and decides at > startup, which ones it will use. This is done by gl_identify_cpu_features. > > To be shure, that the feature-detection-function works correct, it gives > out some messages at this time. As soon it is well tested, we can remove > all related printf's. > > Later we can rename the linux-3dnow(-glide) to linux-generic-x86 or > something like this. OK. I think we should do this real soon (eg, right now) that way we can get bug reports from the widest possible set of users to track down problems. > (And if the autoconf stuff works, we won't need these targets anymore - ) This sounds like it is done, perhaps we should disable the old methods on the experimental branch for the same reasons - get people using autoconf by default so we can shake out any problems. > I would be happy, if we could do something similiar with the FX/NV/G200 > driver - Mesa would become a generic super-driver similiar to the SVGA > X-Server, which decides at runtime, which hardware driver it will use. > > Hmmm..., what interface use the GLX-drivers -- could we use them for a > Mesa-without-glx, too ??? I like this idea too, at least as a stopgap until PI's work is in widespread use. The mlx/aclapi drivers were a step in this direction. Simon P. indicated some interest in porting the g200 work to that api - I don't know if he is still working on this or not. Keith ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] 3dnow and g200 [was: headers for src/asm_mmx.c]
On 07-Jun-99 Keith Whitwell wrote: >> (And if the autoconf stuff works, we won't need these targets anymore - ) > This sounds like it is done, Yep. > perhaps we should disable the old methods > on the experimental branch for the same reasons - get people using > autoconf by default so we can shake out any problems. OK. We could rename the old Makefile to Makefile.old and write a new Makefile, which tells users to install autoconf 2.13 and automake 1.4 and to run ./bootstrap. This way you could still fall back to "make -f Makefile.old ..." Thomas Tanner - email: tanner@(ffii.org|gnu.org|ggi-project.org|gmx.de) web: http://home.pages.de/~tanner GGI/Picasso: http://picasso.ffii.org ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] 3dnow and g200 [was: headers for src/asm_mmx.c]
Thomas Tanner wrote: > > On 07-Jun-99 Keith Whitwell wrote: > >> (And if the autoconf stuff works, we won't need these targets anymore - ) > > This sounds like it is done, > > Yep. > > > perhaps we should disable the old methods > > on the experimental branch for the same reasons - get people using > > autoconf by default so we can shake out any problems. > > OK. We could rename the old Makefile to Makefile.old > and write a new Makefile, which tells users to install autoconf 2.13 > and automake 1.4 and to run ./bootstrap. > This way you could still fall back to "make -f Makefile.old ..." > Can't we have a prebuilt ./configure in the repository? Keith ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
