fireplusteam

@SolaWing , on a file change xCode starts a build of a file with regards to dependencies of this file. If it requires some modules rebuilt first, it would rebuild...

@yaroslavyaroslav , in our case, it would not be working. @SolaWing , I use 2'd approaches and it's the best. I trigger to rebuild the whole project as it's the...

XCBuildService is working like a service, it like accepts the request and triggers some build actions. But it's not easy to implement this and it's something that can be achieved...

@wojciech-kulik , also in my extension I just cancel an indexing build when a user wants to run it's own, so it's always only one build in a single time,...

also we have an option like dry run in XCBBuildService, it's private and it only generates dependencies and compile flags without actually compiling the sources, it's private and useless if...

I believe running background build is not something that we want to be a part of xcode build server as there can be additional difficulties with passing all that required...

xcode sends specific request to XCBBuildServer to retrieve the index data for a specific file, it's very similar like to build a single file. I wrote a proxy for XCBBuildSever...

it's simple to recreate You need to install `pyinstaller` on a mac then unarchive the Archive.zip, you need to build python file like a binary ``` pyinstaller --onefile XCBBuildService.py ```...

I did it without disabling SIP

@wojciech-kulik , anyway Xcode starts a build to get indexes with the parameter ``` continueBuildingAfterErrors = True ``` to mimic this you can use **xcodebuild -jobs 4** or **-jobs 2**...