Skip to main content
AI Assist is now on Stack Overflow. Start a chat to get instant answers from across the network. Sign up to save and share your chats.

Return to Question

typo fixes
Source Link
edit approved Dec 16, 2014 at 16:10
shim
edit approved Dec 16, 2014 at 16:10
shim
  • 10.3k
  • 13
  • 79
  • 121

Seperate Separate Xcode Project

We have 3 apps that we maintain, that all use the same menu controller and Core Data model. In addition, one of the apps uses several views and controllers from one of the apps. It's getting to the point that we need to find some way to seperateseparate into different projects to prevent painful Xcode project merges. Right now all the code is mixed in together and each app has its own target in one Xcode project.

Is there any way we can seperateseparate the project easily into different projects that have AppA, AppB, and AppC where AppB and AppC depend on AppA?

Seperate Xcode Project

We have 3 apps that we maintain, that all use the same menu controller and Core Data model. In addition, one of the apps uses several views and controllers from one of the apps. It's getting to the point that we need to find some way to seperate into different projects to prevent painful Xcode project merges. Right now all the code is mixed in together and each app has its own target in one Xcode project.

Is there any way we can seperate the project easily into different projects that have AppA, AppB, and AppC where AppB and AppC depend on AppA?

Separate Xcode Project

We have 3 apps that we maintain, that all use the same menu controller and Core Data model. In addition, one of the apps uses several views and controllers from one of the apps. It's getting to the point that we need to find some way to separate into different projects to prevent painful Xcode project merges. Right now all the code is mixed in together and each app has its own target in one Xcode project.

Is there any way we can separate the project easily into different projects that have AppA, AppB, and AppC where AppB and AppC depend on AppA?

improve detail on the problem
Source Link
Jadar
Jadar
  • 1.7k
  • 1
  • 13
  • 25

We have 3 apps that we maintain, that all use the same menu controller and Core Data model. In addition, one of the apps uses several views and controllers from one of the apps. It's getting to the point that we need to find some way to seperate into different projects to prevent painful Xcode project merges. Right now all the code is mixed in together and whatevereach app is built is based off what source files are on a certainhas its own target in one Xcode project.

Is there any way we can seperate the project easily into different projects that have AppA, AppB, and AppC where AppB and AppC depend on AppA?

We have 3 apps that we maintain, that all use the same menu controller and Core Data model. In addition, one of the apps uses several views and controllers from one of the apps. It's getting to the point that we need to find some way to seperate into different projects to prevent painful Xcode project merges. Right now all the code is mixed in together and whatever app is built is based off what source files are on a certain target.

Is there any way we can seperate the project easily into AppA, AppB, and AppC where AppB and AppC depend on AppA?

We have 3 apps that we maintain, that all use the same menu controller and Core Data model. In addition, one of the apps uses several views and controllers from one of the apps. It's getting to the point that we need to find some way to seperate into different projects to prevent painful Xcode project merges. Right now all the code is mixed in together and each app has its own target in one Xcode project.

Is there any way we can seperate the project easily into different projects that have AppA, AppB, and AppC where AppB and AppC depend on AppA?

Source Link
Jadar
Jadar
  • 1.7k
  • 1
  • 13
  • 25

Seperate Xcode Project

We have 3 apps that we maintain, that all use the same menu controller and Core Data model. In addition, one of the apps uses several views and controllers from one of the apps. It's getting to the point that we need to find some way to seperate into different projects to prevent painful Xcode project merges. Right now all the code is mixed in together and whatever app is built is based off what source files are on a certain target.

Is there any way we can seperate the project easily into AppA, AppB, and AppC where AppB and AppC depend on AppA?