corinthia-dev mailing list archives

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


Dennis E. Hamilton commented on COR-22:

Let's back up a little.

"build" or whatever name we give it can be anywhere.  In particular, that allows performance
and access issues to be handled for the build separately from wherever the working copy of
the repository is located.  It also means all of the cruft that is generated as part of creating
a buildable structure is in some appropriate temporary but perhaps high-performing location.
 It's voluminous but there is no penalty in simply deleting it all when no longer of immediate

That is not true for external\ which is locked into the repository structure and which is
hammered a fair amount in order to create three folders of necessary material.  It makes a
weak point in the structure.  (If the source tree were on a CD-ROM or a USB stick, this would
be even more apparent.)

We've already encountered issues around that when the working clone is on an external drive.

The current build instructions use an environment variable although it is actually not needed.
 There are all manner of environment variables that are set during builds, it is just not
something the developer has to pay attention to usually.

I'm not proposing a definite action.  I think we should keep looking.

I don't quite understand a blanket objection to environment variables.  I also prefer to avoid
depending on ones having to be set by the developer for something to work.  For me that's
different than not having them.

> Do not use within-repository folders for any build-related activity
> -------------------------------------------------------------------
>                 Key: COR-22
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message