Andreas Schuh

This will be possible after use of a `.ini` read via config parser module, see #314.

**Comment by [schuhschuh](https://github.com/schuhschuh)** _Thursday Jan 16, 2014 at 18:21 GMT_ --- Andrew's comment: > what do you think of creating a super build template, or supporting super-build in the standard...

**Comment by [schuhschuh](https://github.com/schuhschuh)** _Thursday Jan 16, 2014 at 18:21 GMT_ --- ;) Yes, I was thinking about it when making the final touches for the current one, but thought this...

**Comment by [ahundt](https://github.com/ahundt)** _Thursday Jan 16, 2014 at 18:24 GMT_ --- Yes, I also have some code I'm planning to integrate from my old CMakeMesh repository as part of issue...

**Comment by [ahundt](https://github.com/ahundt)** _Thursday Jan 16, 2014 at 18:28 GMT_ --- We may also want to consider a Config.cmake script in the top level of BASIS itself. If we can...

**Comment by [schuhschuh](https://github.com/schuhschuh)** _Thursday Jan 16, 2014 at 18:30 GMT_ --- Right, I think I mentioned this somewhere. Similar to a `config.h.in` file for C++ maybe on another subject though....

**Comment by [schuhschuh](https://github.com/schuhschuh)** _Thursday Jan 16, 2014 at 18:42 GMT_ --- Let's see, maybe I got your idea, but using such `Config.cmake` for the actual project being build, not BASIS...

**Comment by [schuhschuh](https://github.com/schuhschuh)** _Thursday Jan 16, 2014 at 18:45 GMT_ --- In particular, the `Config.cmake` file or build-specific super-build script would cache the options and variables set by the user...

**Comment by [ahundt](https://github.com/ahundt)** _Thursday Jan 16, 2014 at 18:46 GMT_ --- We could set up an ExternalProject.cmake so that it forwards the internal options along.

**Comment by [schuhschuh](https://github.com/schuhschuh)** _Thursday Jan 16, 2014 at 18:54 GMT_ --- So if `basis_find_package` takes care of adding external projects for the dependencies, then it probably would have to set...