![]() The CMakeLists must remain the ‘single source of truth’ if we want to allow this kind of usage. We expect that most users of the CMake support will use it for functionality that simply doesn’t (and can’t) exist in the Projucer: stuff like linking against other CMake targets or writing helper functions to configure multiple targets with minimal boilerplate. The new standalone CMake support behaves in exactly the same way: when using CMake, the project CMakeLists are now the ‘single source of truth’ for project configuration, and CMake generates Xcode/VS projects which may get overwritten when reconfiguring the project. Users know that when making changes inside the Projucer, any changes to the generated project files (Xcode projects, VS projects, makefiles etc.) will be overwritten. Any changes to the build settings should happen inside the Projucer, so that the settings are propagated to all the exporters as appropriate. ![]() Currently, the Projucer is designed to act as the ‘single source of truth’ for JUCE project setup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |