Maneage - Tasks: task #15272, Single target to build all...
You are not allowed to post comments on this tracker with your current authentication level.
task #15272: Single target to build all high-level software (for testing)
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Mon 06 May 2019 12:40:55 PM UTC | ||
Should Start On: | Sun 05 May 2019 11:00:00 PM UTC | Should be Finished on: | Sun 05 May 2019 11:00:00 PM UTC |
Category: | Software | Priority: | 5 - Normal |
Status: | Postponed | Privacy: | Public |
Assigned to: | None | Percent Complete: | 0% |
Open/Closed: | Open | Effort: | 0.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-f8d8.
Corresponding source code
Right now, the user has to specify which target they want the project to build, and only those software that the project needs are installed. This is ofcourse, the needed behavior for each project.
But for testing purposes (for example when a change to a low-level program is made), we want to see how/if it affects the builds of all programs. One way is to manually add the higher-level programs, but as our library of installed software increases, we can't manually add/remove them.
Therefore, for such testing cases, it would be very useful to have a special target in `TARGETS.mk' (for example `build-all-high-level'). When this variable is given a value of `yes', then an simple Make command in `high-level.mk' can go and read all the software names from `versions.mk' and set them as a target to build (ignoring the two `top-level-programs' and `top-level-python' variables).