#202: Document build procedures -----------------------+---------------------------------------------------- Reporter: levill_r | Owner: levill_r Type: task | Status: new Priority: critical | Milestone: Component: Trac | Version: 1.0 Resolution: | Keywords: gcc icpc -----------------------+----------------------------------------------------
Old description:
Write a Trac page (several pages?) on these topics:
- Why `make` is the way to go.
- Why you should (normally) run `bootstrap` only once.
- Why you should (normally) run `configure` only once per build
directory.
- How to build Olena with the Intel C++ Compiler (ICC)
- By setting it a build time (not very good).
- By setting it a configuration time (better).
- By setting it in a `config.site` file (the best).
- How to automate things using `CONFIG_SITE`.
- Why compiling from Emacs (using `M-x compile`) is better than...
- ...Compiling with `make` from a terminal.
- ...Compiling with `g++` from a terminal (arg!).
This is not restricted to Olena, so we might want to move this material elsewhere later.
New description:
Write a Trac page (and/or a few paragraphs in `HACKING`) on these topics:
* Why `make` is the way to go. * Why you should (normally) run `bootstrap` only once. * Why you should (normally) run `configure` only once per build directory. * How to build Olena with the Intel C++ Compiler (ICC) * By setting it a build time (not very good). * By setting it a configuration time (better). * By setting it in a `config.site` file (the best). * How to automate things using `CONFIG_SITE`. * Why compiling from Emacs (using `M-x compile`) is better than... * ...Compiling with `make` from a terminal. * ...Compiling with `g++` from a terminal (arg!).
This is not restricted to Olena, so we might want to move this material elsewhere later.
--
Comment(by levill_r):
Mention `HACKING` as a location for this information.