Re: [Libmesh-devel] Compiling libMesh taking a lot longer these days

[Vikram G. <sim...@gm...>]

Ok, no problems then. I just wanted to make sure that it was indeed a
genuine case of changes in the library, not some inefficiency with how my
build system is set up.

Thanks.

On Tue, Jan 29, 2013 at 9:39 AM, Roy Stogner <roy...@ic...>wrote:

>
> On Tue, 29 Jan 2013, Vikram Garg wrote:
>
>  I dont know if anybody has run into this issue, but doing a git pull and
>> compiling libMesh seems
>> to be taking a lot longer recently. It seems that the entire library is
>> being compiled everytime
>> I do a git pull. I am not sure, but I think this is because the configure
>> file seems to change
>> everytime I do a git pull.
>> Is anybody else having the same problem ?
>>
>
> A couple of those incidents were indeed the frequently-changing
> autotools files due to Derek's SolutionTransfer stuff; most of them
> are probably the frequently-changing header files due to my
> dof_id_type stuff.
>
> Sorry about the hassle!  I'm trying to make libMesh compile cleanly
> with several extra-paranoid warnings enabled (-Wconversion, for
> instance, so the compiler won't happily silently truncate 64-bit to
> 32-bit ints) and there are a ton of trivial changes involved.  Plus,
> I'm working on the headers before the source files, on the theory that
> extra recompiling-everything-every-**time pain should be gotten out of
> the way as soon as possible.
> ---
> Roy
>
> --
> Vikram Garg
> Postdoctoral Associate
> Center for Computational Engineering
> Massachusetts Institute of Technology
>
> http://www.runforindia.org/runners/vikramg
>