mirror of
https://github.com/loot/libloot.git
synced 2026-07-27 14:16:01 -07:00
Rename "LOOT API" to "libloot"
To avoid confusion when talking about the library vs. its API. The GitHub repository has not yet been renamed, so all references to it are unchanged.
This commit is contained in:
+1
-1
@@ -32,7 +32,7 @@ DOXYFILE_ENCODING = UTF-8
|
||||
# title of most generated pages and in a few other places.
|
||||
# The default value is: My Project.
|
||||
|
||||
PROJECT_NAME = "LOOT API"
|
||||
PROJECT_NAME = "libloot"
|
||||
|
||||
# The PROJECT_NUMBER tag can be used to enter a project or revision number. This
|
||||
# could be handy for archiving the generated documentation or if some version
|
||||
|
||||
@@ -25,6 +25,10 @@ Added
|
||||
Changed
|
||||
-------
|
||||
|
||||
- Renamed the library from "the LOOT API" to "libloot" to avoid confusion
|
||||
between the name of the library and the API that it provides. The library
|
||||
filename is changed so that the ``loot_api`` part is now ``loot``, e.g.
|
||||
``loot.dll`` on Windows and ``libloot.so`` on Linux.
|
||||
- :cpp:any:`CyclicInteractionError` has had its constructor and methods
|
||||
completely replaced to provide a more detailed and flexible representation of
|
||||
the cyclic path that it reports.
|
||||
|
||||
@@ -2,10 +2,10 @@
|
||||
Credits
|
||||
*******
|
||||
|
||||
The LOOT API is written by `Ortham`_ in C++ and makes use of the `Boost`_,
|
||||
libloot is written by `Ortham`_ in C++ and makes use of the `Boost`_,
|
||||
`esplugin`_, `libgit2`_, `libloadorder`_, `loot-condition-interpreter`_,
|
||||
`spdlog`_ and `yaml-cpp`_ libraries. The copyright licenses for all of these and
|
||||
the LOOT API itself in :doc:`../licenses/texts`.
|
||||
libloot itself in :doc:`../licenses/texts`.
|
||||
|
||||
.. _Ortham: https://github.com/Ortham
|
||||
.. _Boost: http://www.boost.org/
|
||||
|
||||
@@ -11,5 +11,5 @@ thousands of Bash Tag suggestions.
|
||||
This metadata that LOOT supplies is stored in its masterlist, which is
|
||||
maintained by the LOOT team using information provided by mod authors and users.
|
||||
Users can also add to and modify the metadata used by LOOT through the use of
|
||||
userlist files. The LOOT API provides a way for third-party developers to access
|
||||
userlist files. libloot provides a way for third-party developers to access
|
||||
this metadata for use in their own programs.
|
||||
|
||||
Reference in New Issue
Block a user