Skip to content

Instantly share code, notes, and snippets.

View iggym's full-sized avatar
🎯
😄

Iggy iggym

🎯
😄
View GitHub Profile
@iggym
iggym / steps-github-project.txt
Last active June 17, 2022 03:42
Steps to create a public github project to share
Steps to create a github project to share
================================================================================
1. Create your software project locally
2. Create a github repo using web UI (Without README, License and .gitignore)
3. Open a terminal In your local project
cd /<your project>
git init
Add a .gitignore file (see notes below)
@iggym
iggym / Xcode-Gitignore-files.txt
Last active February 26, 2022 23:40
Xcode Gitignore files
Below are multiple .gitignore files for use with Xcode/Objective-C projects
##########################################
# OS X
.DS_Store
# Xcode
build/
*.pbxuser
!default.pbxuser
@iggym
iggym / .gitignore
Created January 2, 2014 20:05 — forked from adamgit/.gitignore
#########################
# .gitignore file for Xcode4 / OS X Source projects
#
# Version 2.0
# For latest version, see: http://stackoverflow.com/questions/49478/git-ignore-file-for-xcode-projects
#
# 2013 updates:
# - fixed the broken "save personal Schemes"
#
# NB: if you are storing "built" products, this WILL NOT WORK,
@iggym
iggym / .gitignore
Created January 2, 2014 18:57 — forked from adamgit/.gitignore
#########################
# .gitignore file for Xcode4 / OS X Source projects
#
# Version 2.0
# For latest version, see: http://stackoverflow.com/questions/49478/git-ignore-file-for-xcode-projects
#
# 2013 updates:
# - fixed the broken "save personal Schemes"
#
# NB: if you are storing "built" products, this WILL NOT WORK,
@iggym
iggym / .gitignore
Created January 2, 2014 18:47 — forked from adamgit/.gitignore
#########################
# .gitignore file for Xcode4 / OS X Source projects
#
# Version 2.0
# For latest version, see: http://stackoverflow.com/questions/49478/git-ignore-file-for-xcode-projects
#
# 2013 updates:
# - fixed the broken "save personal Schemes"
#
# NB: if you are storing "built" products, this WILL NOT WORK,
@iggym
iggym / .gitignore
Created January 2, 2014 18:14 — forked from mmorey/.gitignore
#########################
# .gitignore file for Xcode5
#
# NB: if you are storing "built" products, this WILL NOT WORK,
# and you should use a different .gitignore (or none at all)
# This file is for SOURCE projects, where there are many extra
# files that we want to exclude
#
# For updates, see: http://stackoverflow.com/questions/49478/git-ignore-file-for-xcode-projects
# and https://gist.github.com/adamgit/3786883
@iggym
iggym / CVS-SVN-Tags-Branches.txt
Last active December 31, 2015 21:19
CVS/SVN Tags and Branches ...
Trunk
The trunk contains the most current code. It is sometimes the exact code that is running in production. There's only one trunk in your repository, take care of it. You shouldn't use trunk to fix bugs or create new features.
===The trunk is only used to create branches, tags and releases.===
Branch
Branches are a copy of the trunk. These branches are created independently and can be used to add, modify or delete features to the current code and to fix bugs. There two (2) types of branches you can create Feature Branches and Bug Fix Branches.
Feature Branches
The Feature branch is mainly use to add, modify or delete feature to your current code.
Bug Fix Branches
@iggym
iggym / xcodebuild-xcrun-xcodeselect.sh
Last active December 31, 2015 06:58
xcodebuild-xcrun-xcodeselect
#xcodebuild, xcrun, xcode-select
What Is xcodebuild?
-Command line access to Xcode IDE
-Works with projects and workspaces
-Batch operations
Build
Archive
Query
The Build log strutcure has Targets-Command-Message
@iggym
iggym / XCTest-Assertions.m
Created December 12, 2013 22:06
XCTest Assertions
//XCTest supports the following assertions.
XCTFail (format…)
XCTAssertNil (a1, format…)
XCTAssertNotNil (a1, format…)
XCTAssert (a1, format…)
XCTAssertTrue (a1, format…)
XCTAssertFalse (a1, format…)
XCTAssertEqualObjects (a1, a2, format…)
XCTAssertEquals (a1, a2, format…)
#/usr/bin/env python
import lldb
# Put _this_ file into ~/Library/lldb/thread_return.py
# Put the following line into ~/.lldbinit
# command script import ~/Library/lldb/thread_return.py
def __lldb_init_module(debugger, internal_dict):
debugger.HandleCommand('command script add -f thread_return.thread_return thread_return')