JD Gadina
JD Gadina
Not yet. For now you'll also need to generate the «old» code coverage format, using the following settings in the Xcode build settings: * Generate Test Coverage Files (`GCC_GENERATE_TEST_COVERAGE_FILES`) *...
Not really sure about proxies... Have you tried with the `--verbose` flag? Also, you can try with `--dry-run`.
You can see a working example in the unit test file: https://github.com/macmade/dlib/blob/master/Unit-Tests/Tests.cpp Relevant part is: ``` #include extern int hv_vcpu_run( unsigned int cpu ); extern int hv_vm_foobar( uint64_t flags );...
Thanks a lot for the feedback. I’ll fix that ; )
This project has warnings-as-errors turned on. Switch the build setting and the warnings are just that - only warnings. This is correct behavior.
The project indeed has warnings-as-errors enabled. Disabling this is not a valid solution. Treating warnings as errors can be a requirement on some projects. At least provide a way to...
Since there is a -warn-concurrency flag, please provide a -no-warn-concurrency or -disable-warn-concurrency so we can use them on specific files while keeping warning as errors on.
I do get a warning when linking the ARM binary: Ignoring file libswiftAppKit.dylib, building for macOS-arm64 but attempting to link with file built for macOS-x86_64
> I can confirm that it still happens with Xcode 15.0. I got alerted after receiving a negative review for my App Store app after publishing an update built with...
I’ll see what I can do