2016-02-08 23:45:57 +01:00
|
|
|
.. _doc_introduction_to_godot_development:
|
2016-02-08 22:07:55 +01:00
|
|
|
|
2015-12-12 17:57:44 +01:00
|
|
|
Introduction to Godot development
|
|
|
|
=================================
|
|
|
|
|
2016-05-04 11:07:37 +02:00
|
|
|
This page is meant to introduce the global organization of Godot Engine's
|
2016-05-02 09:41:43 +02:00
|
|
|
source code, and give useful tips for extending/fixing the engine on the
|
|
|
|
C++ side.
|
|
|
|
|
|
|
|
Architecture diagram
|
|
|
|
--------------------
|
|
|
|
|
2016-05-04 11:07:37 +02:00
|
|
|
The following diagram describes the architecture used by Godot, from the
|
|
|
|
core components down to the abstracted drivers, via the scene
|
2016-05-02 09:41:43 +02:00
|
|
|
structure and the servers.
|
|
|
|
|
|
|
|
.. image:: /img/architecture_diagram.jpg
|
2015-12-12 17:57:44 +01:00
|
|
|
|
|
|
|
Debugging the editor with gdb
|
|
|
|
-----------------------------
|
|
|
|
|
2016-05-02 09:41:43 +02:00
|
|
|
If you are writing or correcting bugs affecting Godot Engine's editor,
|
|
|
|
remember that the binary will by default run the project manager first,
|
|
|
|
and then only run the editor in another process once you've selected a
|
|
|
|
project. To launch a project directly, you need to run the editor by
|
|
|
|
passing the ``-e`` argument to Godot Engine's binary from within your
|
|
|
|
project's folder. Typically:
|
|
|
|
|
|
|
|
.. code:: bash
|
|
|
|
|
|
|
|
$ cd ~/myproject
|
|
|
|
$ gdb godot
|
|
|
|
> run -e
|
|
|
|
|
|
|
|
Or:
|
|
|
|
|
|
|
|
.. code:: bash
|
|
|
|
|
|
|
|
$ gdb godot
|
2018-10-07 00:12:30 +02:00
|
|
|
> run -e --path ~/myproject
|