dome_key_event_source_simulator/Makefile, branch master Special function key simulator library for DomeKey Makefile: Add `build-release` target 2018-11-04T15:37:40+00:00 Teddy Wing 2018-11-04T15:37:40+00:00 fafbc6a23408e071d6cbff858e8492b8abab479c Build a release version of the library. To get these recipies, did what I did before for the debug ones. Ran $ xcodebuild -scheme dome_key_event_source_simulator -configuration Release and copy-pasted the result, with these changes: * Removed "sysroot"-related arguments (for Rust integration) * Changed absolute paths to use `${HOME}` * Replaced DerivedData directory path hash with `*` 
Build a release version of the library. To get these recipies, did what
I did before for the debug ones. Ran

    $ xcodebuild -scheme dome_key_event_source_simulator -configuration Release

and copy-pasted the result, with these changes:

* Removed "sysroot"-related arguments (for Rust integration)
* Changed absolute paths to use `${HOME}`
* Replaced DerivedData directory path hash with `*`
Makefile: Move `xcodebuild` steps into Make 2018-10-15T17:58:36+00:00 Teddy Wing 2018-10-15T17:58:36+00:00 c089d8cc157fc4298b0e2bca0f8665f7ffe5a8c7 I needed to remove the `-isysroot` compiler flag in order to get the static library to build in my Rust project without the ld: framework not found ColorSync for architecture x86_64 linker error (which is apparently caused by the fact that I'm building against a 10.13 SDK on a machine running 10.12, since ColorSync exists only on 10.13). Not sure if there's a way to have Xcode not use the `-isysroot` flag and let us continue to build using `xcodebuild`. Just copy-pasted the build output including exported environment variables. I removed machine-specific things like absolute paths to my home directory and the hash after the DerivedData directory. Not very clean, but it seems to work. 
I needed to remove the `-isysroot` compiler flag in order to get the
static library to build in my Rust project without the

    ld: framework not found ColorSync for architecture x86_64

linker error (which is apparently caused by the fact that I'm building
against a 10.13 SDK on a machine running 10.12, since ColorSync exists
only on 10.13).

Not sure if there's a way to have Xcode not use the `-isysroot` flag and
let us continue to build using `xcodebuild`.

Just copy-pasted the build output including exported environment
variables. I removed machine-specific things like absolute paths to my
home directory and the hash after the DerivedData directory.

Not very clean, but it seems to work.
Makefile: Add a `clean` target 2018-10-15T17:31:56+00:00 Teddy Wing 2018-10-15T17:31:56+00:00 051a9afdad6a004053bbfc1adf25b9d28b67c31f 






Makefile: Rebuild when Objective-C sources change
2018-10-14T14:12:08+00:00

Teddy Wing

2018-10-14T14:11:19+00:00

8b0eea58989b3f4f103cfae7438d16724c0354e8

Makes the edit-compile cycle faster.





Makes the edit-compile cycle faster.







Makefile: Use a more generic Mac OS SDK
2018-10-14T14:03:26+00:00

Teddy Wing

2018-10-14T14:03:26+00:00

a2e2c1fdd1b6448dc4e97e8bb41c31a52d96cf6b

Instead of hard-coding the 10.13 SDK.





Instead of hard-coding the 10.13 SDK.







Add a C test file to test linking and the lib function
2018-10-14T13:59:42+00:00

Teddy Wing

2018-10-14T13:59:42+00:00

e7778b010ef5d4221665cc6ad8955efb1ccf9e21

Once I got linking working, this confirms that the key simulator
function actually works.

Beef up the Makefile to enable us to properly link the Objective-C
library.





Once I got linking working, this confirms that the key simulator
function actually works.

Beef up the Makefile to enable us to properly link the Objective-C
library.







Add Makefile
2018-10-14T00:54:51+00:00

Teddy Wing

2018-10-14T00:54:51+00:00

0f509e12d9ce3930ae600e0eacc2d683686272f4

Basic development build rule.





Basic development build rule.