Re: [Libmesh-devel] libmesh+automake

2012-03-07 Thread Kirk, Benjamin (JSC-EG311)
>> We'd clearly prefer to use the directory structure, but I don't know >> of a way to do that with automake. > > I'll continue to work this. I know how to have a single 'make' build > *everything* at once - opt, dbg,devel,etc... but that might be too much in > the other direction. > > What woul

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread Kirk, Benjamin (JSC-EG311)
Yeah I use macports to give my machine some more respectability... ;-) On Mar 5, 2012, at 8:02 PM, "Derek Gaston" mailto:fried...@gmail.com>> wrote: I'll spend more time with it tomorrow (how did it not work on Lion or Snowleopard today? I thought you develop, at least partially, using a Mac

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread Derek Gaston
I'll spend more time with it tomorrow (how did it not work on Lion or Snowleopard today? I thought you develop, at least partially, using a Mac laptop!). I'm sure we can work something out here. I know I'm coming off like a crazy man... this whole thing just threw me for a loop. I have so many

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread Kirk, Benjamin (JSC-EG311)
> On Mon, 5 Mar 2012, Derek Gaston wrote: > >> First: Thanks for the good reply. Good to see what's in your head on this >> subject. ;-) > > Whoa, whoa, let's cut down on the politeness level, everyone. I've > already decided that further disagreements here ought to be settled > via physical co

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread Roy Stogner
On Mon, 5 Mar 2012, Derek Gaston wrote: First: Thanks for the good reply. Good to see what's in your head on this subject. ;-) Whoa, whoa, let's cut down on the politeness level, everyone. I've already decided that further disagreements here ought to be settled via physical combat, and if

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread Paul T. Bauman
On Mon, Mar 5, 2012 at 5:42 PM, Derek Gaston wrote: > > Yikes about having to install it. Where to install it? Right now > everything is self-contained… > > I think we need to get you access to MOOSE so you can see what we're > dealing with here. As things are they work perfectly… if you had t

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread Derek Gaston
First: Thanks for the good reply. Good to see what's in your head on this subject. ;-) On Mar 5, 2012, at 3:07 PM, Kirk, Benjamin (JSC-EG311) wrote: > Really - a no go? I guess then 'svn add' is simply asking too much of a > developer too? I'm just a believer in the "only store things in on

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread Kirk, Benjamin (JSC-EG311)
On 3/5/12 1:08 PM, "Derek Gaston" wrote: > FirstlyŠ I'm still against this idea. I think it's adding complication to > something that currently works well for the majority of users and use cases. Understood. > On Mar 5, 2012, at 11:16 AM, Kirk, Benjamin (JSC-EG311) wrote: > > (1) files must

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread Roy Stogner
On Mon, 5 Mar 2012, Kirk, Benjamin (JSC-EG311) wrote: > As part of this process I have also cleaned up almost all of our M4 sources > for consistency and brevity. Possibly at some cost in correctness? Autodetection is now failing for me on vtk and fparser (?!). --- Roy ---

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread John Peterson
On Mon, Mar 5, 2012 at 12:16 PM, Kirk, Benjamin (JSC-EG311) wrote: > Indeed - ill add some minimum version checking and turn off anything > unnecessary. > > While I'm at it, what is your automake and libtool (or glibtool on the Mac) > version? > > I intend to try successively older versions unti

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread Derek Gaston
Exactly... it fails on Lion as well. This is exactly the kind of stuff I'm worried about. We have users using ridiculously old OSes in secure environments where they can't just easily upgrade something... Here are the errors on Lion: [gastdr][~/projects/libmesh.automake]> ./bootstrap autoreconf

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread Kirk, Benjamin (JSC-EG311)
Indeed - ill add some minimum version checking and turn off anything unnecessary. While I'm at it, what is your automake and libtool (or glibtool on the Mac) version? I intend to try successively older versions until I find what is really needed. -Ben On Mar 5, 2012, at 1:09 PM, "John Peter

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread John Peterson
On Mon, Mar 5, 2012 at 11:16 AM, Kirk, Benjamin (JSC-EG311) wrote: > This coming along quite nicely I think.  My last step is to clean out the > Make.common definitions and then test including it in client projects.  I > started on that over the weekend and don't see any issues with maintaining >

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread Derek Gaston
Firstly… I'm still against this idea. I think it's adding complication to something that currently works well for the majority of users and use cases. On Mar 5, 2012, at 11:16 AM, Kirk, Benjamin (JSC-EG311) wrote: > (1) files must manually be added to ./Makefile.am and ./include/Makefile.am Fo

Re: [Libmesh-devel] libmesh+automake

2012-03-05 Thread Roy Stogner
On Mon, 5 Mar 2012, Kirk, Benjamin (JSC-EG311) wrote: > Roy - a long time ago you hoped using automake might help with IDE > integration - is that something you are still interested in, and if > so might you check it out? Well, this is ironic. KDevelop4 appears to have dropped their automake-sp

[Libmesh-devel] libmesh+automake

2012-03-05 Thread Kirk, Benjamin (JSC-EG311)
This coming along quite nicely I think. My last step is to clean out the Make.common definitions and then test including it in client projects. I started on that over the weekend and don't see any issues with maintaining that functionality. The biggest changes from the developer's perspective