corinthia-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jan iversen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COR-22) Do not use within-repository folders for any build-related activity
Date Sat, 10 Jan 2015 21:37:34 GMT

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

jan iversen commented on COR-22:
--------------------------------

it seems our build instructions needs to be updated, we build today without using any environment
variables.

I have nothing against environment variables when really needed, but that is of course only
my opinion. if all others are in favour of using it, then I will not block it.

I have simply seen through experience from e.g. AOO how the use of environment variables can
explode and lead to many funny effect when not set correctly.



> 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