#19043: Move configuration part of build/make/install to configure
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.9
Component: build | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jdemeyer/move_install_to_configure|
4178b80c3ff5ce8e1753bffe48f32dc5bcccb728
Dependencies: #18885, #19187 | Stopgaps:
-------------------------------------+-------------------------------------
Old description:
> Most of what `build/make/install` does really belongs in `configure`, in
> particular creating `build/make/Makefile`. This ticket moves that part to
> `configure` and adjusts the top-level build system to make this work.
>
> There are two advantages:
> 1. Running `make` is a lot simpler and hence faster.
> 2. It allows using `./configure` to configure the list of packages (note
> that this ticket does not implement that, it just makes it possible to
> implement that in future tickets)
>
> There is an important change for developers: any change to the list or
> versions of packages will require a run of `./configure` to take effect.
> Note that `./configure` will be re-run automatically if `./configure`
> itself changes, which happens with every Sage version. So there is no
> need to manually rerun `./configure` if you're just switching between
> versions.
>
> '''Note to reviewers''': this branch currently has conflicts. However, in
> order to avoid endless rebasing, I will rebase whenever somebody plans to
> review this ticket.
New description:
Most of what `build/make/install` does really belongs in `configure`, in
particular creating `build/make/Makefile`. This ticket moves that part to
`configure` and adjusts the top-level build system to make this work.
There are two advantages:
1. Running `make` is a lot simpler and hence faster.
2. It allows using `./configure` to configure the list of packages (note
that this ticket does not implement that, it just makes it possible to
implement that in future tickets)
There is an important change for developers: any change to the list or
versions of packages will require a run of `./configure` to take effect.
Note that `./configure` will be re-run automatically if `./configure`
itself changes, which happens with every Sage version. So there is no need
to manually rerun `./configure` if you're just switching between versions.
--
Comment (by jdemeyer):
Rebased. I know the git history looks funny, but you really should just
review the result, not the individual commits.
--
Ticket URL: <http://trac.sagemath.org/ticket/19043#comment:9>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
