You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@corinthia.apache.org by "jan iversen (JIRA)" <ji...@apache.org> on 2015/01/10 15:06:34 UTC
[jira] [Commented] (COR-22) Do not use within-repository folders
for any build-related activity
[ https://issues.apache.org/jira/browse/COR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272507#comment-14272507 ]
jan iversen commented on COR-22:
--------------------------------
I can see your point, but I definitively don´t want our build system to be depending on environment variables like PROJECT_PATH.
In my tree I have "externals" (which are filled once with your scripts) and "build" as the only non-git directories, I don´t feel that disturbing, but I am also not against your idea if it can be solved without environment variables.
"build" is only in the tree due to my choice.
> 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)