Will this speed up the `make build` or `sage -br` process? It used to be 
really quick, but now it takes much longer and rechecks all the packages.
I really don't want this if I'm just changing a line of code to see, if 
this fixes my problem.

Am Sonntag, 19. April 2020 01:48:23 UTC+2 schrieb Dima Pasechnik:
>
> On Sun, Apr 19, 2020 at 5:11 AM Nils Bruin <nbr...@sfu.ca <javascript:>> 
> wrote: 
> > 
> > On Saturday, April 18, 2020 at 1:51:29 PM UTC-7, John H Palmieri wrote: 
> >> 
> >> 
> >> Some disadvantages: 
> >> 
> >> - It adds one step or a least requires the typing of some extra 
> characters 
> >> - It's not what we're used to doing to build Sage. 
> >> 
> > 
> > Isn't it possible to have a make target "make configure"? 
> > 
> > Wouldn't it be possible to make this part of a "make cleanall", or 
> whatever an appropriate metatarget is? 
> > 
> > Is there some way to detect when  ./confiugre absolutely needs to be 
> run, and make that part of some metatarget? 
> > 
> > What I envision is that we can have both: 
> > 
> >  * running ./configure; make works (and doesn't do way too much work) 
> >  * running "make", or perhaps some target "make confbuild" works and 
> runs configure. 
> > 
> > There is of course the issue that make already runs loads of submakes of 
> packages, that in turn must run ./configure, so in the sage build process, 
> "./configure" is already commonly triggered by make. I don't think we'd 
> want to change that, so it seems to me it makes sense to have "./configure" 
> run under control of make for sage as well (under certain conditions). 
>
> make should not trigger the "normal" run of main ./configure, as this 
> leads to various chicken vs egg problems, which can only be cured by 
> repeatedly triggering ./configure runs 
> all the time, As out ./configure is slow, this is a waste of time to have 
> this. 
> We can of course create a special target that will trigger 
> ./configure, but why defviate from the usual commonmy known 
> ./configure && make ? 
>
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "sage-devel" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-...@googlegroups.com <javascript:>. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/74a8fed6-eb02-492e-9e9e-5d7e28857b0a%40googlegroups.com.
>  
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3da8c90b-7a0f-4d29-8f3c-4f1c5456c1bf%40googlegroups.com.

Reply via email to