-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change naming from library <=> module #48
Comments
We just need this for exports & tools now |
Early in the development, there was a confusion on the meaning of "module" and "library" in context of the Vita. After the tools were written initially, we decided to reverse the meaning of those two words. All user-facing usage of those words have been changed (console outputs, messages, etc) but it is too much word to change all internal usage of those words (function/variable names, etc). Therefore you may be confused when reading the source since the meaning of "module" and "library" is used inconsistently. It would be great if someone could take the time to correct all the usages ("module" exports one or more "libraries" and imports zero or more "libraries"; eboot.bin is a module). |
@yifanlu When you say "for exports & tools now", which do you mean ? |
Like |
Deprecates the use of 'modules' in export configurations. This is for consistency with import configurations. See issue vitasdk#48 for more details
Deprecates the use of 'modules' in export configurations. This is for consistency with import configurations. See issue #48 for more details
As per specification 1.2 changes, references to the term "module" and the term "library" should be reversed.
Module refers to the entire SELF/suprx/skprx. Library refers to a collection of exports. Spec 1.0 had these terms reversed.
The text was updated successfully, but these errors were encountered: