On Tue, May 24, 2022 at 10:04 AM Samuel Lelievre
<samuel.lelie...@gmail.com> wrote:
>
> Side note: if using `sage -i`, prepending `V=0` will
> suppress most of the build's verbosity. Example:
> ```
> $ V=0 sage -i jupyterlab_widgets
> ```
>
> I cannot answer the following two questions:
>
> - why does installing JupyterLab after building Sage
>   trigger recompilation of all Cython files in src/sage?
>
sagelib (including all Cython files in src/sage) has dependencies on
e.g. jupyter-core
(no idea why). Perhaps building jupyterlab leads to touching this or
some other dependency of sagelib, in turn triggering its rebuilding.

Dima


> - how can that be fixed?
>
> but there might be a workaround consisting in
> configuring the build so that JupyterLab is built
> along with the rest, rather than afterwards.
>
> After getting a new development release of Sage
> (with `git pull origin develop --tags` or by getting
> and unpacking the source tarball), do this:
>
> ```
> $ export MAKE='make -j8'
> $ ./bootstrap
> $ ./configure --enable-jupyterlab_widgets
> $ make -s V=0
> ```
>
> instead of something like
>
> ```
> $  export MAKE='make -j8'
> $ ./bootstrap
> $ ./configure
> $ make -s V=0
> $ ./sage -i jupyterlab_widgets
> ```
>
> Maybe fixing the unwanted recompilation of all
> cython files deserves a ticket?
>
> --
> 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/e9011f7c-6126-439c-90ef-718e35e82cd1n%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/CAAWYfq2shrjQeL6kBr_BaaOkfhBx1ysUQgUsrM%2BUDGWoWwTbfg%40mail.gmail.com.

Reply via email to