https://forge.ispras.ru/https://forge.ispras.ru/favicon.ico?16490126692019-01-23T09:57:24ZOpen-Source ProjectsKlever - Feature #9445: Support build bases provided in form of archives and placed at standard locationshttps://forge.ispras.ru/issues/9445?journal_id=355102019-01-23T09:57:24ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>I did this in branch <em>build-base-archives</em>. This branch passed tests. OpenStack Klever instances work. So, I merged the branch to master in <a class="changeset" title="Update deployment scripts to follow recent changes" href="https://forge.ispras.ru/projects/klever/repository/331/revisions/5a4ae83249661b59bb64585ef221ed5959d17df8">5a4ae8324</a>.</p>
<p>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 <em>CC</em>, <em>Callgraph</em>, etc.</p>
<p>Build bases are additionally searched for in subdirectory <em>build bases</em> at standard locations. Using that directory is convenient since there may be many build bases.</p>
<p>Please, note, that you should not specify environment variables <em>KLEVER_WORK_DIR</em> and <em>KLEVER_BUILD_BASES</em> anymore. Instead you can specify environment variable <em>KLEVER_DATA_DIR</em> that has almost the same intention as <em>KLEVER_WORK_DIR</em> but data in a corresponding directory should not be modified by Klever (at least it is assumed).</p>