-
-
Notifications
You must be signed in to change notification settings - Fork 21.6k
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
Error using --gdscript-docs command tool #86604
Comments
I didn't even know there was a doctools kinda thing! I have been making a plugin in gdscript and just using the inline remarks seems to create automatic docs which are pretty good. Not sure about C# and so on. |
Hi! That works fine for in-editor docs, but the command line tool is supposed to generate the xml files that then you can use to create a static website (with parsing of the xml files, etc), like the godot online documentation itself. |
Ah, okay. I never quite understood that because those help docs are not visible in-engine. I wish the gdscript help was, for example. What do you gain by this for your plugin? Am I missing some obvious help button somewhere? |
@donn-xx it's not that I gain much, just the possibility of having a static website with the docs of the plugin to make it easier to check them, so you don't have to actually download the plugin to your project and activate it if you want to see what it does beforehand. |
I used the MRP privided in the .zip file and followed the instructions to reproduce the problem, using Godot 4.2.1. on Linux. I also see a bunch of GDScript compilation errors when running the command. When running the command from the root folder of the project (where project.godot is located) it does create three .xml files for me, two of them as hidden files:
When running the command from within addons/GodotPlayGameServices, it creates these two .xml files instead:
In both cases this is not the expected behavior, as many other classes are missing, and none of the generated files should be hidden. There is also no helpful error message. So I would say I can confirm this as being a bug. |
This may be related to #84579? The workaround mentioned in this comment seems to work, i.e. execute the command from the root project folder with the argument |
Ran into this when attempting to generate the documentation for GUT
This worked for me. I also had to ctrl+c to kill it, but things were generated. I have not investigated the resulting xml yet, but files of various sizes exist where I expected them to. Results for various commands
From the project root. Using relative path and
From the project root. Using the absolute path to the directory generates a lot of errors, and hangs, but it does generate SOME xml files, but not as many as when using
From the project root. Using
|
Tested versions
System information
Windows 10
Issue description
Hi, I'm trying to generate the xml files of the docs for a plugin I'm developing, but when I run this command
godot --doctool <path_to_docs_folder> --no-docbase --gdscript-docs .
(assuming I'm in the directory of the plugin, ie./godot_project/addons/name_of_plugin
)I get a bunch of errors, as if the command tool was trying to run the project, but missing information. For example:
And then, the xml files are not generated.
Steps to reproduce
addons/GodotPlayGameServices
. If you download the plugin from the repo, it'splugins/export_scripts_template
godot --doctool <path_to_docs_folder> --no-docbase --gdscript-docs .
Minimal reproduction project (MRP)
You can download the repo of the plugin, I tested using this specific commit: godot-sdk-integrations/godot-play-game-services@92adb37
The classes I want to convert to xml are in the
plugin/export_scripts_template
folder.I have also attached a zip with the godot project, there I tried executing the doctool inside the
addons/GodotPlayGameServices
folder.mrp.zip
The text was updated successfully, but these errors were encountered: