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.
Follow up for #2598
It's not necessary to generate a dSYM file if you use
build = FALSE
.The problem with
build = TRUE
is that if you're not generating dSYM files, the linker inserts paths to object files that contain the DWARF debug info and these paths are pointing to dangling temporary locations:The workaround implemented in the linked PR is to generate a dSYM file that contains the DWARF info. But this debug info itself points to source files in the dangling temporary directory, forcing the user to remap these files in the debugger, which is quite cumbersome.
With
build = FALSE
the package is installed directly from source so the recorded paths to object files are correct:There is no need to generate a dSYM file in that case. The only advantage of that file is that you are allowed to delete the object files in the source repo and still preserve full debug information but in practice I think most of us keep their
src
directory dirty.Generating these files gets in the way of various dev workflows since they are not ignored by default so it's better not to have to deal with those. For instance I saw that NOTE during check: