-
Notifications
You must be signed in to change notification settings - Fork 202
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
Documentation builds should use separate directories #1378
Labels
Milestone
Comments
Related to #389 |
After nasa/osal#1033 and #1561 this fixes half of the issue - now just between the detail design and user guide sharing the same subdirectory and "warnings.log" file. |
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Jun 8, 2021
Put the "detaildesign" and "users_guide" into separate working directories, and do a general cleanup/simplification of the generated doxyfiles. Detail design just includes all components, and use "exclude" where special treatment was needed, and to avoid UT code. Paths for each "arch" (target-specific) are written to separate files and included directly in the generated doxyfile, reducing the number of generated files/layers.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Jun 9, 2021
Put the "detaildesign" and "users_guide" into separate working directories, and do a general cleanup/simplification of the generated doxyfiles. Detail design just includes all components, and use "exclude" where special treatment was needed, and to avoid UT code. Paths for each "arch" (target-specific) are written to separate files and included directly in the generated doxyfile, reducing the number of generated files/layers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The 3 documentation targets (detaildesign, usersguide, osalguide) all share the same "doc" subdirectory for the doxygen run. This can become a problem when trying to validate documentation builds and building with the
-j
option. They work fine when built one at a time, but with-j
at one point my machine got into an endless loop with two doxygen builds running in parallel that kept stepping on the other's files.Describe the solution you'd like
Use separate dirs so that builds can be done in parallel without interfering with each other.
Additional context
This should also result in separate "warnings.log" files too, that can be more easily checked.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: