> On Sat, 3 Jul 2010, John Peterson wrote: > >> On Sat, Jul 3, 2010 at 10:00 AM, Paul T. Bauman <ptbau...@gmail.com> wrote: >> If there are no plans to change to autotools (or better, modern >> build system *cough* SCons *cough*) then consider this a feature >> request for "make install" behavior for the reasons listed in my >> previous email. >> >> This would be my vote (add make install to existing build system) as well. > > I kind of liked that "we move to automake, but someone other than me > does all the work" option. > > But just adding a "make install" target would be easier. > >> I think this is the biggest 'pro' you listed that we are currently >> lacking... > > For me the only unlisted pro of automake is that IDEs understand it... > but that's just based on my failed attempt to import libMesh into > eclipse (or was it some KDE thing?) years ago; it may be outdated > info.
Consider this thread revived. In addition to not writing a make install in the previous 18 months, there is another missing feature which I've recently had an increased need for: proper VPATH builds. After a few years of learning autotools for FIN-S I have a proper appreciation for it... Many ages ago we successfully introduced the METHOD concept as a way for managing multiple build versions, but there is a serious Achilles heel - Make.common must always be the same. So it is easy to build opt, dbg, devel on the same platform, but forget managing a build for multiple systems out of the same $LIBMESH_DIR. For me at least this would be a very nice feature - I currently maintain three libmesh installations on different machines that can all see the same filesystem because they all have different Make.common's. Derek made an argument agains autotools at one point because our current system 'just works' - but I think that is more because it is properly maintained. It is easy to write a poorly constructed autotools installation, but a well constructed one will work as well as what we have. Plus, moving to a proper libtool installation will help in the future with shared libraries on multiple platforms (yeah, looking at you OSX). Anyone have a serious change of heart in the past 18 months and would leave the project if we did this? If not I might start a branch and see how bad it gets... -Ben ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
