![]() ![]() ![]() Applications that link to frameworks in other directories, such as ~/Library/Frameworks or /Network/Library/Frameworks, must specify the exact path to the framework at build time so that the dynamic linker can find it. Frameworks in this location are discovered automatically by the compiler at compile time and the dynamic linker at runtime. If they are to be used across a local area network, they can be installed in /Network/Library/Frameworks however, this option should be avoided if possible.įor nearly all cases, installing your frameworks in /Library/Frameworks is the best choice. If your framework should only be used by a single user, you can install it in the ~/Library/Frameworks subdirectory of the current user however, this option should be avoided if possible. Most public frameworks should be installed at the local level in /Library/Frameworks. Third-party frameworks can go in a number of different file-system locations, depending on certain factors. Where you install a framework also helps determine how to install the framework. Once your framework is ready to go, you need to decide where to install it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |