Merge branch 'main' of https://github.com/modz2014/WinToMacApps

Author: DevX-Cipher

README.md

@@ -1,42 +1,45 @@
-# Build macOS Apps on Windows (CLI + GUI + Qt)
+# 🧰 Cross-Compile macOS Apps on Windows — C, Objective-C, Qt, Cocoa (No Mac Needed)
 
-**Cross-compile real macOS executables (C, Objective-C, Qt, Cocoa GUI) using Clang, CMake, and Ninja on Windows.**
+![Platform: Windows](https://img.shields.io/badge/platform-Windows-blue)
+![Builds macOS Apps](https://img.shields.io/badge/builds-macOS-brightgreen)
+![License: MIT (Non-Commercial)](https://img.shields.io/badge/license-MIT--NC-yellow)
 
-No Mac needed to build — just to run.
+Build native macOS applications — including Cocoa and Qt-based GUI apps — **entirely on Windows**, using Clang, CMake, and Ninja.
 
----
+✅ **No Mac required to build.** Just transfer and run the output on a real Mac.
 
-## What This Is
+---
 
-This project is a Windows-based toolchain setup that lets you **build native macOS applications** — including **Cocoa- and Qt-based GUI apps** — using Clang and the macOS SDK.
+## ✨ Features
 
-- Compile Objective-C, C, and Qt source files on Windows  
-- Use CMake + Ninja (recommended) or optional standalone scripts  
-- Build Mach-O binaries that run on real macOS  
-- Includes working Cocoa and Qt GUI examples
+- Build real macOS `.app` and CLI binaries from Windows
+- Full support for C, Objective-C, and Qt (QtWidgets)
+- Cocoa GUI support (AppDelegate, XIB-style)
+- Works with CMake + Ninja or Visual Studio
+- **Automatically detects macOS SDK from `SDK/` folder**
+- Includes working examples: CLI, Cocoa, and Qt GUI
+- No VM or Hackintosh required
 
 ---
 
-## Requirements
+## 📦 Overview
 
->  **Note:** This setup is intended for **static Qt builds**. If you're using dynamic Qt builds, you will need to manually handle Qt plugins, frameworks, and runtime paths (`@rpath`).
+This project provides a cross-compilation toolchain that allows you to build native **macOS** executables — including GUI apps — from a **Windows** system. It supports:
 
-To get started, you'll need:
-
-- [LLVM/Clang for Windows](https://releases.llvm.org/)
-- [Ninja build system](https://github.com/ninja-build/ninja/releases)
-- [CMake (v3.10+)](https://cmake.org/download/)
-- [macOS SDK](https://github.com/phracker/MacOSX-SDKs/releases/tag/11.3)
-- [QtMacos-SDK](https://github.com/LongSoft/qt-6-static-universal-macos)
-- [Qt Example on GitHub](https://github.com/pyinstxtractor/Pyextract/tree/PyInstaller-Archive-Viewer)
+- Clang + macOS SDK
+- Objective-C, C, and C++ (Qt)
+- Cocoa GUI (with AppDelegate)
+- Qt Widgets-based GUI
 
 ---
 
-## Project Structure
+## 📁 Project Structure
 
 ```
 MacCross/
 ├── CMakeLists.txt
+├── SDK/
+│   └── MacOSX14.5.sdk/             # <--- Place SDK here
 ├── C-Example/
 │   └── hello.c
 ├── ObjC-Example/
@@ -46,28 +49,28 @@ MacCross/
 ├── Qt-Example/
 │   ├── main.cpp
 ├── macosx-toolchain.cmake
-├── build-Qt.bat           # Legacy/manual build script (Qt – optional)
-├── build/                 # Created during build
+├── build-Qt.bat                    # Optional manual script
+├── build/
 ```
 
 ---
 
-## Environment Variables (Required for Static Qt Builds)
+## 🔧 Requirements
 
-Before running the build (CMake or manual), set the following environment variables if you're using Qt:
-Example setup:
-```cmd
-set QT_DIR=F:\Qt\6.7.3\macos
-set QT_FRAMEWORKS=%QT_DIR%\lib
-set MACOSX_SDK_PATH=F:\MacOs-Stuff\MacOSX14.5.sdk
-set MACOSX_DEPLOYMENT_TARGET=11.0
-```
+- [LLVM/Clang for Windows](https://releases.llvm.org/)
+- [Ninja build system](https://github.com/ninja-build/ninja/releases)
+- [CMake (v3.10+)](https://cmake.org/download/)
+- [macOS SDK](https://github.com/phracker/MacOSX-SDKs/releases/tag/11.3) (place in `SDK/` folder)
+- [QtMacos-SDK](https://github.com/LongSoft/qt-6-static-universal-macos)
+- [Qt Example on GitHub](https://github.com/pyinstxtractor/Pyextract/tree/PyInstaller-Archive-Viewer)
 
 ---
 
-## How to Use
+## 🛠️ How to Build
 
-### Option 1: Build with CMake + Ninja (Recommended)
+You can build using either CMake + Ninja (CLI) or Visual Studio (GUI). Both methods work with this project.
+
+### 🔧 Option 1: CMake + Ninja (Recommended for automation or scripting)
 
 ```bash
 mkdir build
@@ -76,62 +79,79 @@ cmake -G Ninja -DCMAKE_TOOLCHAIN_FILE=../macosx-toolchain.cmake ..
 cmake --build .
 ```
 
-### Option 2: Manual Build Scripts (Optional / Legacy)
+### 🖥️ Option 2: Visual Studio (Recommended for GUI users)
+
+1. Open **Visual Studio**
+2. Select **"Open a local folder"**
+3. Choose the project root (where `CMakeLists.txt` is located)
+4. When prompted, select a **CMake configuration** (e.g., `x64-Release`)
+5. Visual Studio will detect the CMake project and automatically configure it
+6. Ensure `macosx-toolchain.cmake` is being used:
+   - Go to **CMake Settings** or `CMakePresets.json`
+   - Set the toolchain file path under `CMake toolchain file`
+7. Build via **Build > Build All**
+
+> ✅ Make sure the toolchain file is set, or builds will fail.
+
+---
+
+## 📌 Environment Variables (Static Qt Builds Only)
 
-These scripts are provided for reference or alternative workflows. You must ensure the environment variables are properly set before running them.
+If you're using Qt (especially static builds), set the following environment variables before building:
 
 ```cmd
-build-Objc.bat   :: for Cocoa apps
-build-Qt.bat     :: for Qt apps
+set QT_DIR=F:\Qt\6.7.3\macos
+set QT_FRAMEWORKS=%QT_DIR%\lib
 ```
 
+> ✅ MACOSX_SDK_PATH and MACOSX_DEPLOYMENT_TARGET are automatically handled by the toolchain (SDK is detected from the SDK/ folder, deployment target is set to 11.0 by default).
+
 ---
 
-## Verifying the Output
+## ✅ Verifying the Output
 
-Transfer the output files to a Mac and run:
+Transfer the built binaries to a Mac and run:
 
-```sh
-hello       # From C-Example
-ObjCExample # From Cocoa app
-QtExample   # From Qt app
+```bash
+./hello         # From C-Example
+./ObjCExample   # From Cocoa app
+./QtExample     # From Qt app
 ```
 
-Expected CLI output:
+Expected output:
 
 ```
 Hello, world!
 ```
 
-> Note: Apps built this way are unsigned.
+> ⚠️ Note: Binaries are unsigned. You may need to bypass Gatekeeper to run them.
 
 ---
 
-## Why Use This?
+## 📚 Examples Included
 
-- Build macOS-native apps without a Mac
-- Automate macOS builds from a Windows development environment
-- Learn Apple toolchain internals and cross-compilation techniques
+- ✅ CLI C Hello World
+- ✅ Cocoa GUI App (Objective-C + AppDelegate)
+- ✅ Qt Widgets GUI App
 
----
+> Want Swift support? Coming soon.
 
-## Examples Included
+---
 
-- C "Hello, World"
-- Cocoa GUI App (Objective-C + AppDelegate)
-- Qt GUI App (QtWidgets-based)
+## 📜 License & Legal Note
 
-> Want Swift? Coming soon.
+This project is licensed under the MIT License (with a non-commercial use clause).  
+See the LICENSE file for more details.
 
 ---
 
-## License & Legal Note
+## 💬 Feedback
 
-This project is licensed under the **MIT License** (with a non-commercial use clause).  
-See the [LICENSE](./LICENSE) file for more details.
+If you found this project helpful, please open an issue with suggestions or improvements.  
+Contributions are welcome — feel free to submit a pull request!
 
 ---
 
-## Feedback?
+## 🔍 Keywords
 
-If you found this project helpful, please feel free to share your thoughts by opening an issue with suggestions or improvements. Contributions are always welcome — feel free to submit a pull request!
+macOS cross-compile • build macOS apps on Windows • Cocoa from Windows • Qt macOS SDK Windows • Clang CMake macOS • create macOS .app without Xcode • Ninja toolchain • Objective-C on Windows