On 10 January 2015 at 15:14, Peter Kelly <[email protected]> wrote: > CMake lets you have your build directory anywhere - there's no requirement > for it to be in the source directory. > > The following will work right now: > > mkdir ~/build > cd ~/build > cmake -G "Unix Makefiles" ~/dev/Corinthia >
Exactly that is what I do, but Dennis also think about "externals". Peter@ did you get a jira account ? (we should comment on the issue) rgds jan i. > > — > Dr Peter M. Kelly > [email protected] > > PGP key: http://www.kellypmk.net/pgp-key <http://www.kellypmk.net/pgp-key> > (fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966) > > > On 10 Jan 2015, at 7:33 am, Dennis E. Hamilton (JIRA) <[email protected]> > wrote: > > > > Dennis E. Hamilton created COR-22: > > ------------------------------------- > > > > Summary: Do not use within-repository folders for any > build-related activity > > Key: COR-22 > > URL: https://issues.apache.org/jira/browse/COR-22 > > Project: Corinthia > > Issue Type: Improvement > > Environment: All > > Reporter: Dennis E. Hamilton > > > > > > When building from the source, all transient data, including downloads > of externals, should happen separate from the source-code repository > working copy. > > > > The repository working copy may be in a location that is not suitable > for writing. It may also be a performance bottleneck to use the same > location as the working repository for transient build-related material. > There may also be storage-limitation considerations. > > > > Ideally, a build directory can be created anywhere and all build > activities conduction in that location, separate from the source-code > repository. One complication is any downloading of external sources and > libraries, and how those can be included in any build of the source tree. > > > > > > > > -- > > This message was sent by Atlassian JIRA > > (v6.3.4#6332) > >
