| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
The changes here had a test looping 5 times with a 1 second wait trying to finish
in a 5 second window. That's a little too close for flakiness. Increased time out to
10 seconds.
|
| | |
|
| |
|
| |
It wasn't being used anywhere.
|
| |
|
| |
Move to NSProcessInfo where appropriate.
|
| |
|
| |
These have been useless since macOS 10.5.
|
| |
|
| |
It has been obsolete since 10.5.
|
| |
|
| |
Use NSJSONSerialization instead.
|
| |
|
| |
The URLArgument categories should be replaced with usages of NSURLComponents and NSURLItems.
|
| |
|
| |
These were functions that dealt with Aliases.
|
| |
|
| |
This check is very flaky from OS version to OS version and whether or not you are running under the debugger.
|
| |
|
|
| |
This functionality is no longer supported on OS X.
Use a LaunchAgent, XPCService or the ServiceManagement APIs instead.
|
| | |
|
| |
|
|
|
|
|
| |
This gets GTMSignalHandler working with libdispatch, and also marks it
as deprecated because it is probably easier just to write your own
version to call a block instead of the method invocation here.
This also makes the tests run again which hasn't been happening for
a long time AFAICT.
|
| | |
|
| |
|
|
|
| |
There was a race between the thread being finished and
isFinished/isExecuting reporting correctly.
There may have also been a locking issue on older single processor phones.
|
| |
|
| |
It should all be replaced with XCTestExpectations.
|
| | |
|
| |
|
|
| |
There were quotes around the test harness path in the project that was making
it so Xcode couldn't find it to run it.
|
| |
|
|
|
| |
This was causing errors when building with Xcode 10 and XCTest.
XCTest defines a bunch of macros starting with _[A-Z] that were
setting off the error when building for the Mac.
|
| | |
|
| | |
|
| | |
|
Thomas Van Lenten
Elly Fong-Jones
dmaclach