openframeworks / openframeworks/projectGenerator

Special use cases (Xcode) – Add .app, custom build phase, Objective-C++ sources

Open
#171 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
90
Forks
79
Avg merge
2d 9h
Merged PRs (30d)
5

Description

Hello everybody,

I'm working on an addon with some special use cases for the PG. Right now I'm working on macOS (Xcode) side, and I would like to know if I can do the following in the addon_config.mk:

  1. I would like to add an .app bundle to the Xcode project and also add it to the Copy Files Build Phase with the Frameworks directory as destination. It's exactly what happens when you add a Framework to ADDON_FRAMEWORKS. Sadly I it doesn't work when I add the .app bundle with ADDON_FRAMEWORKS.

  2. I would like to add a custom Run Script build phase.

  3. The addon uses sources which contain C++ and Objective-C code. In Xcode you have to declare the source file as Objective-C++ to compile correctly. Is there a way to tell the PG to declare a .cpp as Objective-C++ source file. I've already tired ADDON_OBJC_SOURCES which didn't work. (Changing the extension might lead to problems on the VS side of things)

If PG isn't able to do those things does anybody have a quick idea how to simply automate those steps, preferably without running another script?

Thanks a lot.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how addon_config.mk entries such as ADDON_FRAMEWORKS and ADDON_OBJC_SOURCES are consumed for Xcode generation. Compare the handling of .app bundles, Copy Files and Run Script build phases, and Objective-C++ source classification, while checking that changes do not break the Visual Studio path. Done means all three requested Xcode behaviors are supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, macos, objective-c
Domain
build-system, desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.