Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MacOS/iOS compilation/signing Workflow #763

Open
Xpktro opened this issue Jul 18, 2023 · 0 comments
Open

MacOS/iOS compilation/signing Workflow #763

Xpktro opened this issue Jul 18, 2023 · 0 comments

Comments

@Xpktro
Copy link

Xpktro commented Jul 18, 2023

Hello! I'm starting a new project with JUCE and found FRUT as an awesome alternative to work my way into having a programmatically-building multi-target, fully-ci-buildable project. I, however need some insight on a few things I'm having some trouble understanding.

  1. About jucer_project_begin: It's not clearly indicated in the docs but when provided arguments it would check the current CMakeLists.txt against a valid .jucer file, right? I removed all arguments from jucer_project_begin as I've read once the project has fully transitioned to FRUT, the .jucer file is no longer necessary. My project compiles perfectly but I'm asking for confirmation before deleting my original project file completely.

  2. About macOS + iOS workspace/project generators: Will FRUT always generate separate projects for macOS and iOS? The docs and examples seem to treat them as two separate targets but I'm wondering if a single XCode workspace/project can target iOS and macOS at the same time (if not, I should perform project generation in two separate directories, is this right?).

  3. macOS/iOS code signing/provisioning: Although the project compiles and executes just well, the compiled app needs to be signed (and notarized when releasing) for uploading it to a device for testing. Is there any specific option or configuration for this in FRUT or is it out of scope?

  4. apparent macOS build errorL: Just like FRUT with Mac OS #758 I'm experiencing the same error (compiling on a M1 Ultra Mac Studio with XCode 14.3.1 and cmake version 3.26.4):

PhaseScriptExecution CMake\ PostBuild\ Rules /Users/moises/code/mochika/meteoroid/build/build/Meteoroid_StandalonePlugin.build/Debug/Script-000273173F4342B6690FF32E.sh (in target 'Meteoroid_StandalonePlugin' from project 'Meteoroid')
    cd /Users/moises/code/mochika/meteoroid
    /bin/sh -c /Users/moises/code/mochika/meteoroid/build/build/Meteoroid_StandalonePlugin.build/Debug/Script-000273173F4342B6690FF32E.sh
CMake Error at cmake_install.cmake:52 (file):
  file INSTALL cannot find
  "/Users/moises/code/mochika/meteoroid/build/Debug/Meteoroid": No such file
  or directory.

However the standalone app and plugin are actually generated and works. This might be some bug in FRUT (as /Debug/Meteoroid doesn't exist but /Debug/Meteoroid.app does). I also noticed the generated XCode projects have a default OS target that is causing some warnings, but I don't think this would be causing the error. I'll be happy to provide as much context as needed.

Hopefully this isn't too much for a single issue, but didn't want to spam the project with lots of questions that might be quick to answer :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant