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
CMake is a meta build tool and thus is platform independent. As of today Myriad is tied to Eclipse and Autotools and therefore quite Unix centric. CMake support several build chain such as Unix Autotools (Makefiles), Visual Studio Projects, Xcode Projects, Sublime Projects, Eclipse Projects, and many more. Furthermore CMake is far easier to maintain than standard makefiles.
The text was updated successfully, but these errors were encountered:
The architecture I envision would be to have one repository containing all myriad code. That is the all the runtime code as well as the tests and the examples. Furthermore it might be a good idea for myriad to be a standalone application that reads an XML specification and outputs data (satisfying the spec). Hence what is now the toolkit (a collection of header files/ virtual classes and templates) should become a full fledged library plus a myriad executable.
Following is a sketch of the new design.
Built artifacts are:
myriad-dev: the library and header files,
myriad: the runtime and generic executable that accepts arbitrary XML specs and generates data, sequential or parallel depending on the given parameters,
myriad-examples: collection of XML specs in connection with README files that describe the data model,
myriad-tests: Unit - and integration tests for myriad, myriad-dev and myriad-examples.
CMake is a meta build tool and thus is platform independent. As of today Myriad is tied to Eclipse and Autotools and therefore quite Unix centric. CMake support several build chain such as Unix Autotools (Makefiles), Visual Studio Projects, Xcode Projects, Sublime Projects, Eclipse Projects, and many more. Furthermore CMake is far easier to maintain than standard makefiles.
The text was updated successfully, but these errors were encountered: