mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-01-27 14:36:16 +01:00
Merge branch 'document-generated-headers-caveats-for-genmarshal-too' into 'master'
docs: Document generated headers caveats for genmarshal See merge request GNOME/glib!1386
This commit is contained in:
commit
f55ff88531
@ -449,7 +449,23 @@ mainlib = library('project',
|
|||||||
)
|
)
|
||||||
</programlisting></informalexample>
|
</programlisting></informalexample>
|
||||||
<para>
|
<para>
|
||||||
For more information, see the <ulink url="https://mesonbuild.com/Gnome-module.html#gnomegenmarshal">Meson
|
Additionally, if you are including the generated header file inside a build
|
||||||
|
target that depends on the library you just built, you must ensure that the
|
||||||
|
internal dependency includes the generated header as a required source file:
|
||||||
|
</para>
|
||||||
|
<informalexample><programlisting>
|
||||||
|
mainlib_dep = declare_dependency(sources: marshal_files[1], link_with: mainlib)
|
||||||
|
</programlisting></informalexample>
|
||||||
|
<para>
|
||||||
|
You should not include the generated source file as well, otherwise it will
|
||||||
|
be built separately for every target that depends on it, causing build
|
||||||
|
failures. To know more about why all this is required, please refer to the
|
||||||
|
<ulink url="https://mesonbuild.com/FAQ.html#how-do-i-tell-meson-that-my-sources-use-generated-headers">
|
||||||
|
corresponding Meson FAQ entry</ulink>.
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
For more information on how to use the method, see the
|
||||||
|
<ulink url="https://mesonbuild.com/Gnome-module.html#gnomegenmarshal">Meson
|
||||||
documentation for <literal>gnome.genmarshal()</literal></ulink>.
|
documentation for <literal>gnome.genmarshal()</literal></ulink>.
|
||||||
</para>
|
</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
@ -530,7 +530,9 @@ mainlib_dep = declare_dependency(sources: enum_files[1], link_with: mainlib)
|
|||||||
<para>
|
<para>
|
||||||
You should not include the generated source file as well, otherwise it will
|
You should not include the generated source file as well, otherwise it will
|
||||||
be built separately for every target that depends on it, causing build
|
be built separately for every target that depends on it, causing build
|
||||||
failures.
|
failures. To know more about why all this is required, please refer to the
|
||||||
|
<ulink url="https://mesonbuild.com/FAQ.html#how-do-i-tell-meson-that-my-sources-use-generated-headers">
|
||||||
|
corresponding Meson FAQ entry</ulink>.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
Loading…
Reference in New Issue
Block a user