Separate pimega build from area_detector. #33
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pimega build is something that we will probably do frequently here and throwing away the areadetector build cache to rebuild pimega is time consuming. Maybe this could be done for all modules? Particularly for me, pimega is enough, but standardization is never bad.
marcomontevechi1
force-pushed
the
break_areaDetector
branch
from
d3657c0 to
f1a6468
Compare
|
Closing the request as discussed in person. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pimega build is something that we will probably do frequently here and throwing away the areadetector build cache to rebuild pimega is time consuming.
Maybe this could be done for all modules? Particularly for me, pimega is enough, but standardization is never bad.