90eed5c8f8
This tools needs to CD to directory holding the library because it requires that the library be in the current working directory when objects are inserted. Previously, the tool did this by creating an absolute path to the object file itself. So instead of the object file being in the current directory and the library in a directory at an absolute path, this tool used an abolte path to the object file with the library in the current directory. For the most part, that worked fine. However, in the apps directory the object file names are greatly extended in length. In the object file name was extended to a full absolute path and these huge file names were were exceeding some internal limit within the ZDS-II librarian. But useing shorter, relative paths, we were able to avoid hitting this limit and the entire build completed correctly. |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| Makefile | ||
| README.txt | ||
| zds_Config.mk | ||
| zdsar.c | ||
README.txt ========== tools/zds/zdsar.c: This is a wrapper around the ZDS_II librarian. It simplifies the build scripts by replacing large sequences of complex Bash script that were added to the build files. Not only does this clean upi the build files but it also improves performance and, more importantly,i provides a common solution for the Windows native build case. tools/zds/zds_Config.mk: This makefile fragment is include by ZDS-II Make.defs files after including tools/Config.mk. The definitions in this file override some of the the definitions in tools/Config.mk to customize the build for use with the ZDS-II tools. These tools should work with all ZDS-II based platforms including z8, zNeo, and ez80.