On Thu, Aug 30, 2018 at 3:09 PM Paul T. Bauman <ptbau...@gmail.com> wrote:
> On Thu, Aug 30, 2018 at 3:04 PM Paul T. Bauman <ptbau...@gmail.com> wrote:
>
>>
>>
>> On Thu, Aug 30, 2018 at 3:02 PM Derek Gaston <fried...@gmail.com> wrote:
>>
>>> In general you guys are talking about "features" though: when in my
>>> estimation the "core" capability of the development cycle is broken. I
>>> don't think that maintaining "nice" features is worth it at the cost of
>>> hurting the main development cycle
>>> (build->fix->build->fix->add_file->build->fix->test).
>>>
>>
> I should've added here, this is entirely how our build system currently
> works. I've had a build tree. I make a modification in the source. I hit
> `make` in the build tree. I edit the source. I hit `make` in the build
> tree. I hit make install. (With install -C so GRINS only rebuilds what's
> necessary)
>
Oh really? How do you do that when you add a file? I think you missed the
steps where you have to hunt down the scripts and get the Makefiles
modified. Then you have makefile modifications mixed in with your
changes. Do you try to save those off in separate commits - or do you just
smash everything together?
edit->make->test->add_file->make->test
No need for "install" at all. No need to modify Makefiles. No need to run
scripts - all done within my editor with source linking to compile errors.
Not currently possible.
Derek
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
