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
YES PLZ. This would make managing applications that leverage Open Frameworks, but perhaps do not use an OFBaseApp, GLUT etc, but leverage certain features, GL contexts and other functionality much easier. Re-mapping the relationship of OpenFrameworks to projects would be super handy IMO. Having a Framework Version -> (Project A, Project B) mapping makes SVN repos, project management a real pain in the butt IMO. Moving to (Project A -> Framework version), (Project B -> Framework Version), while possibly increasing binary size (or having redundant library versions), allows project paths, project management, code management and dependency isolation to be rooted on a per project basis, rather than globally to a set of projects.
Would be useful for other projects which might use OF internally.
We would ship an xcode project which would compile and build a .framework.
When we add 64 bit support we could have a 32bit and 64bit target .
The text was updated successfully, but these errors were encountered: