Project

General

Profile

Feature #9445

Support build bases provided in form of archives and placed at standard locations

Added by Evgeny Novikov 4 months ago. Updated 4 months ago.

Status:
Closed
Priority:
Urgent
Category:
-
Target version:
Start date:
01/23/2019
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

Before program sources can be provided in various forms and they can be placed at one of standard locations. For build bases this is not the case that is not convenient.

History

#1

Updated by Evgeny Novikov 4 months ago

  • Status changed from New to Closed

I did this in branch build-base-archives. This branch passed tests. OpenStack Klever instances work. So, I merged the branch to master in 5a4ae8324.

Build bases archives can be at least ZIP, TAR, TAR GZ and TAR BZ2 archives. You should not use any intermediate directories when archiving build bases, i.e. at the top level in archives there should be directories like CC, Callgraph, etc.

Build bases are additionally searched for in subdirectory build bases at standard locations. Using that directory is convenient since there may be many build bases.

Please, note, that you should not specify environment variables KLEVER_WORK_DIR and KLEVER_BUILD_BASES anymore. Instead you can specify environment variable KLEVER_DATA_DIR that has almost the same intention as KLEVER_WORK_DIR but data in a corresponding directory should not be modified by Klever (at least it is assumed).

Also available in: Atom PDF