Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Formalizes developement specific features

Description

Security of cars implies that developement specific features are fully removed.

So it is needed to link developement specific features to some explicit tag that can be easyly removed. A such tag should be available in at least 3 strategic places:

  1. within yocto to conditionally add behaviors in recipes using conditionals (see OVERRIDES)

  2. within yocto recipes to tune buid (see DISTRO_FEATURES)

  3. within C/C++ source files to conditionnally activate part of code specific to developement.

Environment

yocto build environement

Activity

Show:

Jose Bollo 
May 29, 2017 at 2:21 PM

Jose Bollo 
May 15, 2017 at 12:41 PM

I was thinking to add

CPPFLAGS += "-DAGL_DEVEL"

but it recompiled everything. So I propose that the correct procedure for tuning C/C++ build is to include in the recipe:

CPPFLAGS_append_agl-devel = " -DAGL_DEVEL"

In that case, any TEXT could be used in place of AGL_DEVEL. In one hand it solves the question of how to handle foreign/legacy code. In an other hand, it seems to forclude to formalize AGL_DEVL as a standard for AGL codes.

IMHO, recommanding the use of AGL_DEVEL tag in AGL code as a GOOD PRACTICE is the way to go because, conversely, enforcing to recompile every thing would be a nightmare for developpers, developpers that are the first involved.

 

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Components

Priority

Created May 15, 2017 at 11:45 AM
Updated July 24, 2017 at 11:45 PM
Resolved May 29, 2017 at 2:21 PM

Flag notifications