You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 22, 2021. It is now read-only.
Currently every Plane implementation requires a different way of embedding custom PlaneApp-based sources into its toolchain. For example:
ios-bridge has the APP-INFO.h file that describes where the PlaneApp source files are placed relative to the Xcode project
sdl-cpp requires a specific launch class and also relies on relative paths to the PlaneApp source files
Although some of these constraints might be unavoidable, it would be nice to have a consistent way of packaging and launching custom Plane-based applications.
The text was updated successfully, but these errors were encountered:
fwcd
changed the title
Add a consistent mechanism to package application that build upon Plane
Add a consistent mechanism to package applications that build upon Plane
Apr 9, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently every Plane implementation requires a different way of embedding custom PlaneApp-based sources into its toolchain. For example:
Although some of these constraints might be unavoidable, it would be nice to have a consistent way of packaging and launching custom Plane-based applications.
The text was updated successfully, but these errors were encountered: