xcbeautify
xcbeautify copied to clipboard
Support for generation of compilation database
Hi 👋
Would be nice to support the generation of compilation databases. Xcpretty seems to support this already: https://github.com/xcpretty/xcpretty#reporters
Thanks!
@acecilia would you like to generate an HTML report from your compilation?
Mmm what do you mean? Sorry, I dont understand the question
At the time of writing, my goal was to generate a compilation database to pass to swiftlint. After looking into it, I end up writing a script to manually generate it
@acecilia would you mind sharing the scripts that you ended using to create the compilation database? thanks!
See some examples here: https://github.com/acecilia/swift-compilation-database
xcpretty supports generation of compile_commands.json files using the following flag: -r json-compilation-database
Currently, xcbeautify doesn't support this reporter:
The value 'json-compilation-database' is invalid for '--report
The compilation database can be used by clangd for code completion when working outside of XCode on a Mac C++ project. This is a great feature from xcpretty but now the xcpretty project is unsupported.
+1 for compilation database.
Parsing the output of xcodebuild to generate a compilation database is fraught with peril. Use -gen-cdb-fragment-path
instead. See https://gist.github.com/T1T4N/f4d63a44476eb5c7046cc561cb8c7f77 for guidance.
+1 on this.
The compilation database is required for SonarScanner to scan projects correctly.
Hola 👋,
We want to inform you that the issue has been marked as stale. This means that there hasn't been any activity or updates on it for quite some time, and it's possible that it may no longer be relevant or actionable. If you still believe that this issue is valid and requires attention, please provide an update or any additional information that can help us address it. Otherwise, we may consider closing it in the near future. Thank you for your understanding.
Hola 👋,
We want to inform you that we have decided to close this stale issue as there hasn't been any activity or response regarding it after marking it as stale.
We understand that circumstances may have changed or priorities may have shifted, and that's completely understandable. If you still believe that this issue needs to be addressed, please feel free to reopen it and provide any necessary updates or additional information.
We appreciate your understanding and look forward to your continued contributions to the project.
Thank you.