Skip to content

Conversation

@vissarion
Copy link
Member

Following the suggestion here this is a simplification for the documentation CI script.

cd $BOOST_ROOT
cd libs/geometry/doc
python ./make_qbk.py
$BOOST_ROOT/b2
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is perfect! So we call b2 now instead of make_qbk.py, cool.

Can we then remove the fact that make_qbk.py calls b2?
Is everyone following this workflow?
Or do we, if we do that, disturb the making of the official release documentation?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not know what scripts/workflow is used to build the official release documentation. @barendgehrels do you know?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I don't know that exactly...

Copy link
Collaborator

@barendgehrels barendgehrels left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@vissarion vissarion merged commit 966567f into boostorg:develop Sep 30, 2024
@vissarion vissarion deleted the fix/doc_ci branch September 30, 2024 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants