Code Integration - Xcode and GitLab: Difference between revisions
From blinkenwiki
Blinkenjim (talk | contribs) No edit summary |
Blinkenjim (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
'''Check in the first local version.''' | '''Check in the first local version.''' | ||
<ol> | |||
<li> If more that one local copy of the codebase exists, and it’s not clear which one should be “the” version, create multiple local sibling directories. | |||
* Example: m404-a, m404-b, etc. | |||
<li> Create a private project on GitLab | |||
#* Example: m404 | #* Example: m404 | ||
# In Xcode, create a new project with the same name. | # In Xcode, create a new project with the same name. |
Revision as of 01:43, 13 June 2021
Check in the first local version.
- If more that one local copy of the codebase exists, and it’s not clear which one should be “the” version, create multiple local sibling directories.
- Example: m404-a, m404-b, etc.
- Create a private project on GitLab
- Example: m404
- In Xcode, create a new project with the same name.
- Cross-platform/Empty
- Product Name: m404
- In same folder as m404-a, etc.
- Create git repository
- Link the new Xcode project to the GitLab project
- git remote add origin git@gitlab.com:jimthompson/m404.git
- get push -u origin —all
- Build up the Xcode project:
- Copy code from first sibling directory (e.g. m404-a) into Xcode directory, making new subdirectories to organize, and rename code as necessary
mkdir m404/arduino cp m404-a/M404SD01.ino m404/arduino/m404-demo.ino
- - Add each new file into the Xcode project (File -> Add Files to “m404”)