caller graphs for library functions
James Jones <[email protected]> Tue, 21 Mar 2023 08:33:37 -0500
| Newsgroups | gmane.text.doxygen.general |
|---|---|
| Message-ID | <CAFY=aDapJjeHe=atd2sO8ach1FPBxnaJ-vKukA+-G44wxWewow@mail.gmail.com> |
--===============3139130047694867064== Content-Type: multipart/alternative; boundary="000000000000f5e69f05f769177e" --000000000000f5e69f05f769177e Content-Type: text/plain; charset="UTF-8" If one's configuration file includes CALLER_GRAPH = YES does doxygen generate caller graphs for library functions? If it does, is there a way to keep that from happening while still allowing caller graphs for other functions? --000000000000f5e69f05f769177e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">If one's configuration file includes<div><br><div><fon= t face=3D"monospace">CALLER_GRAPH =3D YES</font></div><div><br></div><div>d= oes doxygen generate caller graphs for library functions? If it does, is th= ere a way to keep that from happening while still allowing caller graphs fo= r other functions?</div></div></div> --000000000000f5e69f05f769177e-- --===============3139130047694867064== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============3139130047694867064== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Doxygen-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/doxygen-users --===============3139130047694867064==--