obmc-phosphor-systemd: allow systemd unit from repo

If a recipe inherits obmc-phosphor-systemd, all the systemd units
defined in the recipe shall exist in the code tree, otherwise it reports
"Did not find unit file" error.

This commit changes the behavior, and do not report the error if a unit
does not exist in code tree. This allows the system unit to be installed
from repo, as long as the repo does install the systemd unit to expected
path.

Tested: Verify the below case passes the build and the unit is installed
        correctly in the built image:
           * Put a systemd unit in repo;
           * In repo, install the unit into /lib/systemd/system
           * The repo's recipe defines SYSTEMD_SERVICE_${PN} without
             putting the unit in openbmc tree
        And verify if the systemd unit in repo is not installed, the
        build fails due to missing the unit.

Change-Id: I41842798dc93a2c4fa4b6ec212554487a941b9bf
Signed-off-by: Lei YU <mine260309@gmail.com>
1 file changed
tree: ecf46ce806d25648699f74cd0d3fa3e40f6b345b
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-phosphor/
  10. recipes-protocols/
  11. recipes-support/
  12. recipes-textproc/
  13. COPYING.apache-2.0
  14. COPYING.MIT
  15. LICENSE
  16. MAINTAINERS
  17. README.md
  18. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.