Re: [Mesa-dev] autoconf stuff
On 21-Sep-99 [EMAIL PROTECTED] wrote: I don't know the reasoning of the original libtool author. Maybe he wanted to keep the directory "clean". .libs contains libtool-specific data that must not be modified. And it contains the resulting library also and THAT's what I don't understand. (All the object files and symlinks are in the src directory... sot it's not that "clean") The filename(s) of the library is system-dependent (e.g. libGL.so.3.1.3, libGL.sl.3 ...) but the object files (.o and .lo) are not. The src directory contains only the files that are known to the make rules (.o, .lo, .la). There's no doubt that libtool-specific must be stored in a subdirectory but the question is why it should be hidden. I'll ask the original libtool maintainer. Thomas Tanner - email: tanner@(ffii.org|gnu.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] autoconf stuff
On 19-Sep-99 Thomas Tanner wrote: On 17-Sep-99 Brian Paul wrote: Ah, I didn't know about src/.libs (and I suspect a lot of other Mesa users won't either). Long-time Mesa users will realize that there's a configure script and therefore they'll assume that the usual "configure; make; make install" works. But I don't want to install the library - I use it with LD_LIBRARY_PATH since my primary libGL is from GLX project... Why is this directory hidden anyway? IMHO it's no good idea hiding things somewhere - I don´t want to get impressed by autoconf magic features but want to see what's going on... Andree PS: Don't get me wrong, I like autoconf... ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] autoconf stuff
Thomas Tanner wrote: Another important question: Is the upcoming beta 3 supposed to have autoconf support? Yes. If so, do you still want to split Mesa into the library and demos Yes. and how (configure.in doesn't support it yet)? I suggest to move all demos to a subdirectory "demos": demos - demos/demos 3Dfx/demos - demos/3Dfx BeOS - demos/BeOS book - demos/book ggi/demos - demos/ggi images- demos/images mtdemos - demos/mthread samples - demos/samples utils - demos/utils xdemos- demos/x11 That would be the only way to support the two separate packages with autoconf. Really?! It shouldn't be hard to detect the presence of those subdirs and conditionally build their contents. But then again, I don't know much about autoconf. In any case, I think it'd be a much cleaner directory structure (less stuff in the toplevel directory) You've got a point there. Brian, do you think that's reasonable? Could you move those directories on the CVS server? I'm hesitant to do that right now with beta 3 impending. Let's wait and see. -Brian ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] autoconf stuff
On Fri, 17 Sep 1999, Brian Paul wrote: Thomas Tanner wrote: I suggest to move all demos to a subdirectory "demos": demos - demos/demos 3Dfx/demos - demos/3Dfx BeOS - demos/BeOS book - demos/book ggi/demos - demos/ggi images- demos/images mtdemos - demos/mthread samples - demos/samples utils - demos/utils xdemos- demos/x11 That would be the only way to support the two separate packages with autoconf. Really?! It shouldn't be hard to detect the presence of those subdirs and conditionally build their contents. But then again, I don't know much about autoconf. We could modify the release-configure-script to call another script, which removes the demo directories from the SUBDIR variable in Makefile.in, if these are not present. Another way (I think, it will be the harder one - ) could be to do this in the toplevel Makefile. However, I recommend the first way. - Holger ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
RE: [Mesa-dev] autoconf stuff
On Fri, 17 Sep 1999, Thomas Tanner wrote: On 15-Sep-99 Holger Waechtler wrote: the fixam script, which enables automatic dependency tracking, if gcc and gnu make are available, is now called automatically from bootstrap. No, the other way round: fixam disables automatic dependency tracking, if gcc and gnu make are not available. I decided not to call it from bootstrap because a non-GNU developer you would always overwrite the default Makefile.am's (AUTOMAKE_OPTIONS commented out) when doing CVS checkins. Could you please undo your change? If I understood your script right, it works in both directions, doesn't it ? (I could not test it, since I have no none-gnu compiler - Brian ??) If so, it would be no problem, if people check in 'corrupted' Makefile.am's. Btw: Brian, we must make sure that automatic dependency tracking is disabled before we release beta 3. Otherwise configure won't work on non-GNU systems. That shouldn't be a problem -- in the release the dependent files shouldn't change anymore. - Holger ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] autoconf stuff
Hi Brian, I removed the automatic fixam call in bootstrap. And I fixed fixam to work in both directions (I was wrong -- it couldn't do the job right; hope it will now - ). - Holger ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] autoconf stuff
Holger Waechtler wrote: Hi everybody, the fixam script, which enables automatic dependency tracking, if gcc and gnu make are available, is now called automatically from bootstrap. Beside this, SUBDIRS in src/Makefile.am are now filtered, this should make compilation possible, even if somebody forgot some #ifdef's. I hope, this will make the autoconf stuff more robust. After ./configure and make, the lib/ directory is empty and I only find static libraries in the src*/ directories. It would be nice if the libraries wound up in the lib/ directory. I thought shared libs would be made by default. I tried ./configure --enable-shared but that didn't make shared libs either. I'm using a RedHat 5.1 system at the moment. -Brian ___ Mesa-dev maillist - [EMAIL PROTECTED] http://lists.mesa3d.org/mailman/listinfo/mesa-dev
