Project

General

Profile

Actions
Copy link

Feature #10658

closed

Suggest working source trees automatically

Added by Evgeny Novikov almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Evgeny Novikov
Category:
Infrastructure of Core
Target version:
3.1
Start date:
01/12/2021
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

Working source trees allow to show and to use relative paths to source and object files. Unfortunately, they cannot be determined automatically in the general case but it seems that we can consider minimal common parts of paths to input/output files to compilation commands as a first approximation of them. Most likely, it will be enough for most projects.

Actions
Copy link
 #1

Updated by Evgeny Novikov almost 4 years ago

  • Target version set to 3.1

Let's do this in Klever 3.1.

Actions
Copy link
 #2

Updated by Evgeny Novikov over 3 years ago

  • Status changed from New to Resolved

I implemented the suggested approach in branch update-clade. Let's hope that it will be useful.

Actions
Copy link
 #3

Updated by Evgeny Novikov over 3 years ago

I made some improvements and fixes in the same branch. Now files from "/tmp" are ignored as they most likely do not correspond to original source and object files of programs. Also, if one of resulting working source trees is a common prefix for other ones, just it is considered as a working source tree. This is necessary to avoid most ambiguities.

Actions
Copy link
 #4

Updated by Evgeny Novikov over 3 years ago

  • Status changed from Resolved to Closed

Tests were passed, so, I merged the branch to master in b0ec6ed82. After update you can try not to specify working source trees for (re-)generated build bases - Klever will suggest them itself.

Actions
Copy link

Also available in: Atom PDF