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] [Commented] (COR-22) Do not use within-repository folders for any build-related activity
Date Sun, 11 Jan 2015 16:17:34 GMT

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

Dennis E. Hamilton commented on COR-22:
---------------------------------------

I have been thinking about this some more, without a clear resolution just yet.

There are two reasons to move the download and extraction of externals to the build structure.
 First, to have all creation of transient and intermediate material be in the same place.

The second reason is the step needed for moving DLLs into the build/bin/ area so that those
run-time dependencies are satisfied.  (This could be done at extract time into the same bin/
folder, I imagine.)

As the deployment of binaries and test units is developed farther, this will possibly become
more elaborate, and it will vary even more based on platform.

I don't have a clear picture to offer.  This is what I am thinking would be desirable, so
the platform-specific builds are basically one-click procedures, if that is how we want to
go about it.

> 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