corinthia-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (COR-22) Do not use within-repository folders for any build-related activity
Date Sun, 11 Jan 2015 17:11:34 GMT

    [ https://issues.apache.org/jira/browse/COR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272980#comment-14272980
] 

Dennis E. Hamilton edited comment on COR-22 at 1/11/15 5:10 PM:
----------------------------------------------------------------

Interesting idea about build.win.  

I think there should be a setup script in the repository, but the script could be run from
wherever we want the build tree to be constructed and operated.

This could even provide the properly-parameterized CMake command.

Just thoughts.  Not baked yet.  A lot depends on how many different things there are to build
and how many variations of builds for them are of interest.  It would be good to minimize
that in the core repository and let others worry about variations for custom purposes.


was (Author: orcmid):
Interesting idea about build.win.  

I think there should be a setup script in the repository, but the script could be run from
wherever we want the build tree to be constructed and operated.

This could even provide the properly-parameterized CMake command.

Just thoughts.  Not baked yet.

> 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
>              Labels: building, cmake, external-resources
>
> 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)

Mime
View raw message