| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
`NSData-bytes` returns a `const void *`. Cast it to a `const char *`
before trying to use with a `%s` format specifier.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Don't try to use more bytes then there are in the string.
|
| |
|
|
|
|
|
| |
Apparently earlier compilers took our `const structs` and put them into const
data for us so their lifetime was effectively equivalent to `static`. Some
change/optimization in 11.4.1 has moved to that not being the case. Explicitly
make the data structures `static`.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Hasn't really been maintained, Chromium was one of the main users, and they
stopped using it a while ago, they only use a few things now:
https://chromium.googlesource.com/chromium/src/+/master/third_party/google_toolbox_for_mac/BUILD.gn
It also never was in the pod file, meaning less folks were likely to use it.
|
| | |
|
| |
|
|
| |
The string parameters in NSAssertionHandler's -handleFailureInFunction:… method are declared nonnull, but converting __PRETTY_FUNCTION__ and __FILE__ to NSString (via +[NSString stringWithUTF8String:] returns nullable, leading to warnings.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Fixes the auto-generated interface methods for the desired methods. The deprecated methods were causing conflicts in the generated interface of the newer methods that would add a zero-length tuple parameter.
Example of fix for encode:error:
Interface Before:
open func encode(_ data: Data!, error: ()) throws -> String
Interface After:
open func encode(_ data: Data!) throws -> String
|
| | |
|
| | |
|
| |
|
|
|
| |
Also cleanup references to SenTest (no longer supported)
Document differences between gTest and how GTMGoogleTestRunner executes tests.
|
| | |
|
| |
|
|
|
|
| |
XCTAssertAsserts is for testing if NSAssert or NSParameterAssert is called.
It is a no-op if NS_BLOCK_ASSERTIONS is defined.
Update project to match "Xcode" standard with regards to having assertions off in release.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This change makes GTMLocalizer use NSAccessibility when building for 10.10+
deployment targets.
I tested this change by:
1) Hacking the GTM Xcode project to build with a 10.10 deployment target, and
ignoring the other deprecated API uses;
2) Patching this GTM into the chromium tree (which does target 10.10) and
ensuring that it still builds
|
| | |
|
| | |
|
| |
|
| |
Utilities for relatively common desire to know the launch time of an app, or the boot time of a device.
|
| |
|
| |
Release should work now (fingers crossed)
|
| |
|
|
| |
Target configs needed to be set to static library so that stripping occurred correctly.
Unittest config was set as well.
|
| |
|
|
| |
standard for macOS or iOS. (#225)
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Looking at what has changed since the last release:
https://github.com/google/google-toolbox-for-mac/compare/v2.1.4...master
There are two small fixes, but the rest is removing a few unused things and
the majority is marking things as deprecated that the System Frameworks now
provide. So bumping the minor version so folks can control when they adopt
this if they so wish.
|
| | |
|
| |
|
|
|
| |
Let the library build cleaning in the modes folks should migrate, their code
will still get the warning using things.
|
| |
|
|
|
| |
'gcc' hasn't really be used in a while on the mac, and odds are neither
is getting any real use.
|
| |
|
|
|
|
| |
The helpers not mess with names, so this was actually testing Apple's
API, which does seem to have bugs/race conditions, so stop paying
attention to it.
|
| | |
|
| |
|
|
|
| |
The changes here focus on SDK specific or architecture specific
settings where we should just be going with the Xcode defaults for
the version of Xcode being used to build.
|
| |
|
|
|
|
|
|
| |
Made an assumption about how runloops worked in all versions of iOS.
Appears it was wrong in 32 bit versions on single processor.
Runloop executes all input from an input source in a single burst
which caused a test to fail.
(iOS 8.4 on iPhone4s simulator)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pick off the selector natively handled first. NSProxy's base (on my
current OS atleast) will attempt to forward things, and the fact
that the LightWeight proxy then eats the forward where there is no
target objc seems to confuse things.
This all makes the unittests fail when run in release mode, so it
just generally seems safer to reorder this.
The footnote, is NSProxy really defines a class method for this, but
since LightweightProxy doesn't have a fixed class to check with, it
can't really provide that method.
|
| |
|
| |
The block must execute before the test completes.
|
| |
|
|
|
|
|
|
|
| |
- Create shared scheme to use.
- Let Xcode (9.4.1) update the project files and add some warnings.
- Remove -finalize (GC days are gone)
- Add some more pragmas to compile cleanly.
- The iOS targets had a mix of 7.0 and 8.0 min versions, so make them
all 8.
|
| | |
|
| |
|
| |
Apple has deprecated ServiceManagment as of macOS 10.10 and iOS 8.0.
|
| |
|
| |
Tests and code all build and run with no warnings.
|
| |
|
| |
You should use libdispatch with a DISPATCH_SOURCE_TYPE_VNODE source.
|
Benjamin Barenblat
Thomas Van Lenten
Nicholas Tsoi-A-Sue
dmaclach
David Phillip Oster
Michael Wyman
Stefan Miller
Sundeep
Konstantin Varlamov
Elly Fong-Jones