Fix typo in cross partition dependency generation

intention was to symlink modules in vendor_dlkm to system_dlkm. Typo
caused the same modules to link itself.

Test: build, make sure vendor_dlkm's modules.dep contains system
dependency

Change-Id: I19664cd9a8578566d3a038885b8ce27556801a79
1 file changed
tree: 62b26292e51015cb97726bd6e029d4d432ca64f2
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. banchanHelp.sh
  9. buildspec.mk.default
  10. Changes.md
  11. CleanSpec.mk
  12. Deprecation.md
  13. envsetup.sh
  14. finalize-aidl-vndk-sdk-resources.sh
  15. finalize-cleanup.sh
  16. finalize-sdk-rel.sh
  17. finalize-step-1-for-build-target.sh
  18. finalize-step-1.sh
  19. finalize-step-2.sh
  20. finalize_branch_for_release.sh
  21. help.sh
  22. METADATA
  23. navbar.md
  24. OWNERS
  25. PREUPLOAD.cfg
  26. rbesetup.sh
  27. README.md
  28. tapasHelp.sh
  29. Usage.txt
README.md

Android Make Build System

This is the Makefile-based portion of the Android Build System.

For documentation on how to run a build, see Usage.txt

For a list of behavioral changes useful for Android.mk writers see Changes.md

For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.

This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.