emulated_drives_lower_case.txt 917 B

123456789101112131415161718192021222324252627282930
  1. It can happen that a bld.inf has PRJ_EXPORTS which have drive letters in both
  2. upper and lower case. For example, a bld.inf might have contents as follows:
  3. ----------------------------
  4. PRJ_PLATFORMS
  5. ARMV5 WINSCW
  6. PRJ_EXPORTS
  7. foo.txt z:/foo.txt
  8. bar.txt Z:/bar.txt
  9. ----------------------------
  10. In previous versions of Raptor, the following exports result:
  11. $EPOCROOT/epoc32/data/z/foo.txt
  12. $EPOCROOT/epoc32/release/winscw/udeb/z/foo.txt
  13. $EPOCROOT/epoc32/release/winscw/urel/z/foo.txt
  14. $EPOCROOT/epoc32/data/Z/bar.txt
  15. $EPOCROOT/epoc32/release/winscw/udeb/Z/bar.txt
  16. $EPOCROOT/epoc32/release/winscw/urel/Z/bar.txt
  17. Notice the z and Z directories under the directories
  18. $EPOCROOT/epoc32/release/winscw/udeb/
  19. $EPOCROOT/epoc32/release/winscw/urel/
  20. $EPOCROOT/epoc32/data/
  21. This is a problem on Linux, since the directories "z" and "Z" are different.
  22. The fix is to make the drive letter lower case in the target drive exports.