├── .gitignore ├── .gitmodules ├── CMakeLists.txt ├── COPYING ├── COPYING.LESSER ├── README.md ├── USAGE.md ├── mbs-cmake.cmake ├── mbs.yml └── modules ├── libmbs ├── include │ └── mbs │ │ ├── ApplicationModule.h │ │ ├── LibraryModule.h │ │ ├── MbsException.h │ │ ├── MbsProject.h │ │ └── Module.h └── source │ ├── ApplicationModule.cpp │ ├── LibraryModule.cpp │ ├── MbsProject.cpp │ └── Module.cpp └── mbs └── source └── main.cpp /.gitignore: -------------------------------------------------------------------------------- 1 | /.idea 2 | /cmake-build-debug 3 | -------------------------------------------------------------------------------- /.gitmodules: -------------------------------------------------------------------------------- 1 | [submodule "yaml-cpp"] 2 | path = yaml-cpp 3 | url = https://github.com/jbeder/yaml-cpp.git 4 | -------------------------------------------------------------------------------- /CMakeLists.txt: -------------------------------------------------------------------------------- 1 | cmake_minimum_required(VERSION 3.5) 2 | project(mbs) 3 | 4 | set(CMAKE_CXX_STANDARD 17) 5 | 6 | add_subdirectory(yaml-cpp) 7 | include_directories(yaml-cpp/include) 8 | 9 | include(mbs-cmake.cmake) 10 | target_link_libraries(module-libmbs-static yaml-cpp stdc++fs) -------------------------------------------------------------------------------- /COPYING: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /COPYING.LESSER: -------------------------------------------------------------------------------- 1 | GNU LESSER GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | 9 | This version of the GNU Lesser General Public License incorporates 10 | the terms and conditions of version 3 of the GNU General Public 11 | License, supplemented by the additional permissions listed below. 12 | 13 | 0. Additional Definitions. 14 | 15 | As used herein, "this License" refers to version 3 of the GNU Lesser 16 | General Public License, and the "GNU GPL" refers to version 3 of the GNU 17 | General Public License. 18 | 19 | "The Library" refers to a covered work governed by this License, 20 | other than an Application or a Combined Work as defined below. 21 | 22 | An "Application" is any work that makes use of an interface provided 23 | by the Library, but which is not otherwise based on the Library. 24 | Defining a subclass of a class defined by the Library is deemed a mode 25 | of using an interface provided by the Library. 26 | 27 | A "Combined Work" is a work produced by combining or linking an 28 | Application with the Library. The particular version of the Library 29 | with which the Combined Work was made is also called the "Linked 30 | Version". 31 | 32 | The "Minimal Corresponding Source" for a Combined Work means the 33 | Corresponding Source for the Combined Work, excluding any source code 34 | for portions of the Combined Work that, considered in isolation, are 35 | based on the Application, and not on the Linked Version. 36 | 37 | The "Corresponding Application Code" for a Combined Work means the 38 | object code and/or source code for the Application, including any data 39 | and utility programs needed for reproducing the Combined Work from the 40 | Application, but excluding the System Libraries of the Combined Work. 41 | 42 | 1. Exception to Section 3 of the GNU GPL. 43 | 44 | You may convey a covered work under sections 3 and 4 of this License 45 | without being bound by section 3 of the GNU GPL. 46 | 47 | 2. Conveying Modified Versions. 48 | 49 | If you modify a copy of the Library, and, in your modifications, a 50 | facility refers to a function or data to be supplied by an Application 51 | that uses the facility (other than as an argument passed when the 52 | facility is invoked), then you may convey a copy of the modified 53 | version: 54 | 55 | a) under this License, provided that you make a good faith effort to 56 | ensure that, in the event an Application does not supply the 57 | function or data, the facility still operates, and performs 58 | whatever part of its purpose remains meaningful, or 59 | 60 | b) under the GNU GPL, with none of the additional permissions of 61 | this License applicable to that copy. 62 | 63 | 3. Object Code Incorporating Material from Library Header Files. 64 | 65 | The object code form of an Application may incorporate material from 66 | a header file that is part of the Library. You may convey such object 67 | code under terms of your choice, provided that, if the incorporated 68 | material is not limited to numerical parameters, data structure 69 | layouts and accessors, or small macros, inline functions and templates 70 | (ten or fewer lines in length), you do both of the following: 71 | 72 | a) Give prominent notice with each copy of the object code that the 73 | Library is used in it and that the Library and its use are 74 | covered by this License. 75 | 76 | b) Accompany the object code with a copy of the GNU GPL and this license 77 | document. 78 | 79 | 4. Combined Works. 80 | 81 | You may convey a Combined Work under terms of your choice that, 82 | taken together, effectively do not restrict modification of the 83 | portions of the Library contained in the Combined Work and reverse 84 | engineering for debugging such modifications, if you also do each of 85 | the following: 86 | 87 | a) Give prominent notice with each copy of the Combined Work that 88 | the Library is used in it and that the Library and its use are 89 | covered by this License. 90 | 91 | b) Accompany the Combined Work with a copy of the GNU GPL and this license 92 | document. 93 | 94 | c) For a Combined Work that displays copyright notices during 95 | execution, include the copyright notice for the Library among 96 | these notices, as well as a reference directing the user to the 97 | copies of the GNU GPL and this license document. 98 | 99 | d) Do one of the following: 100 | 101 | 0) Convey the Minimal Corresponding Source under the terms of this 102 | License, and the Corresponding Application Code in a form 103 | suitable for, and under terms that permit, the user to 104 | recombine or relink the Application with a modified version of 105 | the Linked Version to produce a modified Combined Work, in the 106 | manner specified by section 6 of the GNU GPL for conveying 107 | Corresponding Source. 108 | 109 | 1) Use a suitable shared library mechanism for linking with the 110 | Library. A suitable mechanism is one that (a) uses at run time 111 | a copy of the Library already present on the user's computer 112 | system, and (b) will operate properly with a modified version 113 | of the Library that is interface-compatible with the Linked 114 | Version. 115 | 116 | e) Provide Installation Information, but only if you would otherwise 117 | be required to provide such information under section 6 of the 118 | GNU GPL, and only to the extent that such information is 119 | necessary to install and execute a modified version of the 120 | Combined Work produced by recombining or relinking the 121 | Application with a modified version of the Linked Version. (If 122 | you use option 4d0, the Installation Information must accompany 123 | the Minimal Corresponding Source and Corresponding Application 124 | Code. If you use option 4d1, you must provide the Installation 125 | Information in the manner specified by section 6 of the GNU GPL 126 | for conveying Corresponding Source.) 127 | 128 | 5. Combined Libraries. 129 | 130 | You may place library facilities that are a work based on the 131 | Library side by side in a single library together with other library 132 | facilities that are not Applications and are not covered by this 133 | License, and convey such a combined library under terms of your 134 | choice, if you do both of the following: 135 | 136 | a) Accompany the combined library with a copy of the same work based 137 | on the Library, uncombined with any other library facilities, 138 | conveyed under the terms of this License. 139 | 140 | b) Give prominent notice with the combined library that part of it 141 | is a work based on the Library, and explaining where to find the 142 | accompanying uncombined form of the same work. 143 | 144 | 6. Revised Versions of the GNU Lesser General Public License. 145 | 146 | The Free Software Foundation may publish revised and/or new versions 147 | of the GNU Lesser General Public License from time to time. Such new 148 | versions will be similar in spirit to the present version, but may 149 | differ in detail to address new problems or concerns. 150 | 151 | Each version is given a distinguishing version number. If the 152 | Library as you received it specifies that a certain numbered version 153 | of the GNU Lesser General Public License "or any later version" 154 | applies to it, you have the option of following the terms and 155 | conditions either of that published version or of any later version 156 | published by the Free Software Foundation. If the Library as you 157 | received it does not specify a version number of the GNU Lesser 158 | General Public License, you may choose any version of the GNU Lesser 159 | General Public License ever published by the Free Software Foundation. 160 | 161 | If the Library as you received it specifies that a proxy can decide 162 | whether future versions of the GNU Lesser General Public License shall 163 | apply, that proxy's public statement of acceptance of any version is 164 | permanent authorization for you to choose that version for the 165 | Library. 166 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | Modular Build System 2 | ==================== 3 | 4 | Overview 5 | -------- 6 | Cmake, while a very useful tool, has some flaws. Namely, it requires a very verbose specification of the build 7 | configuration. While this allows for significant control of what is happening, it is often more work to setup for 8 | complex projects. This is where Modular Build System, or MBS, is useful. MBS allows the developer to group their code 9 | into modules. Each module contains cpp and h files, is either a library or executable binary, and can depend on other 10 | modules. When a module depends on another, the headers of the latter module are available to the former, and the former 11 | will be linked with the latter (if the former is a library, then linking the former also links the latter, transitively). 12 | The developer can then run MBS to convert the module specification in YAML to cmake code, that can then be included in 13 | a cmake project. This allows the high-level specification of MBS to be easily used with the low-level details of cmake, 14 | while simultaneously taking advantage of cmake's support for many different build environments. 15 | 16 | Usage 17 | ----- 18 | The next section gives instructions for getting MBS on your system. Documentation on how to use MBS once it's intalled is available in [USAGE.md](https://github.com/john01dav/mbs/blob/master/USAGE.md), in the root of the project. 19 | 20 | Building 21 | -------- 22 | In MBS, the modules are specified in a mbs.yml file that then needs to be converted to a cmake file to be included in a 23 | cmake project to build. Because, presumably, the users of MBS won't have it installed until they can build it, the cmake 24 | representation is tracked in version control, to allow MBS to be built without already having MBS installed. Other 25 | projects using MBS should not do this, and instead should .gitignore (or otherwise) the cmake output from MBS. Because 26 | MBS includes the cmake file in version control, all that is necessary to build MBS is a recursive clone then a standard 27 | cmake build procedure: 28 | 29 | ```shell 30 | git clone --recurse-submodules https://github.com/john01dav/mbs.git 31 | mkdir mbs/build -p 32 | cd mbs/build 33 | cmake .. -DCMAKE_BUILD_TYPE=Release 34 | make -j8 35 | ``` 36 | 37 | All of MBS's dependencies are included in the repository via git submodules, or are in the C++17 standard library. A 38 | compiler with C++17 (namely, the filesystem library) support is required to build MBS. The provided cmake files for 39 | building MBS are only tested with GCC and Clang on Linux, however they should work for all other GCC-compatible 40 | compilers. The CMakeLists.txt file may need to be changed to support non-GCC-compatible compilers (ie. MSVC), however 41 | the code should be compatible with all C++17 compliant compilers. 42 | 43 | Installation on Arch Linux 44 | ------------ 45 | MBS is available in the Arch Linux User Repository (aur) under the name 46 | [mbs-git](https://aur.archlinux.org/packages/mbs-git/). This AUR package is maintained by a third party and unofficial 47 | with respect to both Arch Linux and MBS, and neither makes any claims regarding its veracity or lack of malicious code. 48 | -------------------------------------------------------------------------------- /USAGE.md: -------------------------------------------------------------------------------- 1 | Modular Build System Usage Tutorial 2 | =================================== 3 | 4 | Overview 5 | -------- 6 | An MBS project is made up of modules, or conceptual groups of code containing C and C++ source files and headers. Each 7 | module is either a library or executable binary. A library can be shared, static, or both. Each module also has 8 | zero or more dependencies, which will be linked to the module. If an application module depends on a library module, and 9 | that library module depends on another library module, then the application module is able to use the second library 10 | module and will be linked to it. 11 | 12 | Becuase CMake has many useful features, mostly it's fairly comprehensive multi-platform library system and its ability to work well with a variety of IDEs and backend build systems (ie. Ninja, Make, CLion, make), MBS is built on top of CMake. That is, MBS generates CMake scripts that then integrate with CMake scripts that you provide allowing both modular and conceptual definitions of what is in your project and full compatability with the well-established world of Cmake. For this reason, it is important to read this entire document to understand how to use MBS -- I have gotten questions before that would have been fixed by reading especiall the last section on how to use MBS with CMake. 13 | 14 | Directory Structure 15 | ------------------- 16 | A typical MBS project's directory structure looks similar to the following: 17 | 18 | example-project 19 | ├── build 20 | | ├ … 21 | ├── CMakeLists.txt 22 | ├── mbs.yml 23 | └── modules 24 | ├── module1 25 | │   ├── include 26 | │   │   ├── a.h 27 | │   │   └── b.h 28 | │   └── source 29 | │   ├── a.cpp 30 | │   └── b.cpp 31 | └── module2 32 | ├── include 33 | │   └── c.h 34 | └── source 35 | ├── c.cpp 36 | └── main.cpp 37 | 38 | As can be seen above, each module exists in the modules directory, and each module has an include and source folder. In 39 | addition to the modules folder, there is an mbs.yml file that specifies information about the project that can't be 40 | represented purely in the filesystem, such as the type of each module and what depends on what. The build folder, with 41 | its contents not shown, contains cmake's project files. The CMakeLists.txt contains the cmake code that is not generated 42 | by MBS, and is instead supplied by the user. 43 | 44 | mbs.yml File 45 | ------------ 46 | As was stated previously, each MBS project contains a single mbs.yml file. This file, as the name suggests, is in YAML 47 | format. It contains the information that MBS needs to build a cmake project specification. The mbs.yml for building MBS 48 | itself is the following: 49 | 50 | mbs-format-version: 0 51 | modules: 52 | libmbs: 53 | type: library 54 | library-type: static 55 | mbs: 56 | type: application 57 | dependencies: 58 | - libmbs-static 59 | 60 | Although the order of the nodes in mbs.yml is irrelevant, the order above is used for convenience while explaining. The 61 | first setting in this file is `mbs-format-version`. This property specifies the minimum MBS format version necessary to 62 | parse the file. The format version is different from the MBS version, and starts at 0 and increments by one with each 63 | format change. New versions of MBS may or may not increment the value, but no single new version will ever increment it 64 | by more than one. MBS will refuse to process the mbs.yml file if the version is greater than the version supported by 65 | the running MBS binary. 66 | 67 | Net, there is the modules node. In the modules node, there is a sub-node for each module. The name of each sub-node is 68 | the name of the module it represents. Each module must specify, at minimum, it's type. The two valid options for type 69 | are `application` and `library`. If the `application` type is selected, no further properties are required. If the 70 | `library` type is selected, then the `library-type` property must be set to either `static`, `dynamic`, or `both`. The 71 | `dependencies` property is a list, and optionally provides a list of library modules upon which the module it is located 72 | in depends. Each item in this list takes the form `-static` or `-dynamic`. It is undefined 73 | behaviour to list a module that does not exist, or to ask for a library type that does not exist for the specified 74 | module. Specifying a library here will make that library's includes available to the module it is specified in, and, if 75 | the module it is specified in is an application, link to that module, or if it is a library then link to any application 76 | using that library. This property can *only* be used with *MBS modules that are libraries* it will *not* work with 77 | system libraries, CMake libraries defined outside of the mbs.yml file, or anything else that isn't a module of type 78 | library in the same mbs.yml file. It is considered undefined behavior to use it in any other way. 79 | 80 | Using MBS With Cmake 81 | -------------------- 82 | To use MBS at all, and especially to unlock its most powerful features, it must be used with cmake. To facilitate this, 83 | run the `mbs ` to generate an mbs.cmake file. The mbs.cmake file contains cmake commands that will 84 | create cmake targets for each module in the mbs.yml. Those targets will consist of the correct source files, include the 85 | correct directories for any module dependencies, and modules that depend on other modules to the latter modules. It will 86 | *not*, however, do anything for libraries specified outside of MBS. For example, to use SFML, you must use CMake's 87 | standard find_package tool, or some other Cmake-compatible library linking tool. To facilitate this, mbs will create one 88 | or more cmake targets for each module. The exact targets created depend on the type of the module. An application module 89 | will create exactly one target of the form `module-`. For example, the `mbs` module in MBS's own mbs.yml 90 | creates the cmake target `module-mbs`. A library type module will create either one or two targets of the form 91 | `module--`. For example, the `libmbs` module in MBS's mbs.yml will create the 92 | cmake .target `module-libmbs-static`. To link to system libraries, one can then call target_link_libraries, and other 93 | target-specific or unspecific commands as normal. For example, to link to SFML in a hypothetical project, a 94 | CMakeLists.txt similar to the following can be used: 95 | 96 | cmake_minimum_required(VERSION 3.5) 97 | project(examplesfmlproject) 98 | 99 | set(CMAKE_CXX_STANDARD 11) 100 | 101 | include(mbs.cmake) 102 | 103 | find_package(SFML REQUIRED COMPONENTS window) 104 | target_link_libraries(module-main sfml-window) 105 | -------------------------------------------------------------------------------- /mbs-cmake.cmake: -------------------------------------------------------------------------------- 1 | #This file was generated by the Modular Build System (mbs), available at https://github.com/john01dav/mbs 2 | #It is not for human modification. To add source files to this project, add them in the appropriate 3 | #directory then re-run mbs. 4 | set(MBS_MODULE_libmbs_FILES 5 | ./modules/libmbs/include/mbs/MbsProject.h 6 | ./modules/libmbs/include/mbs/LibraryModule.h 7 | ./modules/libmbs/include/mbs/Module.h 8 | ./modules/libmbs/include/mbs/MbsException.h 9 | ./modules/libmbs/include/mbs/ApplicationModule.h 10 | ./modules/libmbs/source/MbsProject.cpp 11 | ./modules/libmbs/source/ApplicationModule.cpp 12 | ./modules/libmbs/source/LibraryModule.cpp 13 | ./modules/libmbs/source/Module.cpp 14 | ) 15 | add_library(module-libmbs-static STATIC ${MBS_MODULE_libmbs_FILES}) 16 | target_include_directories(module-libmbs-static PRIVATE modules/libmbs/include) 17 | set_target_properties(module-libmbs-static PROPERTIES OUTPUT_NAME libmbs) 18 | 19 | set(MBS_MODULE_mbs_FILES 20 | ./modules/mbs/source/main.cpp 21 | ) 22 | add_executable(module-mbs ${MBS_MODULE_mbs_FILES}) 23 | target_include_directories(module-mbs PRIVATE modules/mbs/include) 24 | target_include_directories(module-mbs PRIVATE modules/libmbs/include) 25 | set_target_properties(module-mbs PROPERTIES OUTPUT_NAME mbs) 26 | 27 | target_link_libraries(module-mbs module-libmbs-static) 28 | -------------------------------------------------------------------------------- /mbs.yml: -------------------------------------------------------------------------------- 1 | mbs-format-version: 1 #format versions are incremented as a simple integer 2 | modules: #each node in the modules map represents a module 3 | libmbs: #the name of the module; creates a cmake target of module- with output file being simply <.so/.dll/.exe/etc.> 4 | type: library #valid module types are library and application 5 | library-type: static #this entry only has meaning to the library module type, options are both, static, dynamic. The cmake target for library types is -static, -dynamic, or both depending on the value of this entry 6 | mbs: 7 | type: application 8 | dependencies: #optional node; lists the modules of library type that this module will be linked to in -static/-dynamic format 9 | - libmbs-static -------------------------------------------------------------------------------- /modules/libmbs/include/mbs/ApplicationModule.h: -------------------------------------------------------------------------------- 1 | #pragma once 2 | 3 | #include "Module.h" 4 | 5 | namespace mbs{ 6 | class ApplicationModule : public Module{ 7 | public: 8 | ApplicationModule(const std::string &name, const YAML::Node &node) : Module(name, node) {} 9 | 10 | void outputToCmake(std::ostream &out, const MbsProject *moduleData) const override; 11 | void outputLinkingToCmake(std::ostream &out) const override; 12 | 13 | ApplicationModule(const ApplicationModule &) = delete; 14 | ApplicationModule &operator=(const ApplicationModule &) = delete; 15 | }; 16 | } 17 | -------------------------------------------------------------------------------- /modules/libmbs/include/mbs/LibraryModule.h: -------------------------------------------------------------------------------- 1 | #pragma once 2 | 3 | #include 4 | #include 5 | #include 6 | 7 | #include "mbs/Module.h" 8 | 9 | namespace mbs { 10 | class LibraryModule : public Module{ 11 | public: 12 | LibraryModule(const std::string &name, const YAML::Node &node); 13 | 14 | void outputToCmake(std::ostream &out, const MbsProject *moduleData) const override; 15 | void outputLinkingToCmake(std::ostream &out) const override; 16 | 17 | LibraryModule(const LibraryModule &) = delete; 18 | LibraryModule &operator=(const LibraryModule &) = delete; 19 | 20 | private: 21 | bool m_isStatic, m_isDynamic; 22 | 23 | }; 24 | } 25 | -------------------------------------------------------------------------------- /modules/libmbs/include/mbs/MbsException.h: -------------------------------------------------------------------------------- 1 | #pragma once 2 | 3 | #include 4 | #include 5 | 6 | namespace mbs{ 7 | class MbsException : public std::exception{ 8 | public: 9 | MbsException(std::string message) : m_message(std::move(message)) {} 10 | const char *what() const noexcept override { return m_message.c_str(); } 11 | private: 12 | std::string m_message; 13 | 14 | }; 15 | } 16 | 17 | 18 | -------------------------------------------------------------------------------- /modules/libmbs/include/mbs/MbsProject.h: -------------------------------------------------------------------------------- 1 | #pragma once 2 | 3 | #include 4 | #include 5 | 6 | #include "mbs/Module.h" 7 | 8 | namespace mbs{ 9 | constexpr unsigned MIN_MBS_FORMAT_VERSION = 1; 10 | constexpr unsigned MAX_MBS_FORMAT_VERSION = 2; 11 | 12 | class MbsProject{ 13 | public: 14 | MbsProject(const std::string &mbsFile); 15 | ~MbsProject(); 16 | 17 | void outputToCmake(const std::string &cmakeFile); 18 | const Module *getModule(const std::string &name) const; 19 | 20 | MbsProject(const MbsProject&) = delete; 21 | MbsProject &operator=(const MbsProject&) = delete; 22 | 23 | private: 24 | std::vector m_modules; 25 | 26 | inline void verifyFormatVersion(const YAML::Node &rootNode); 27 | inline void loadModules(const YAML::Node &rootNode); 28 | }; 29 | }; -------------------------------------------------------------------------------- /modules/libmbs/include/mbs/Module.h: -------------------------------------------------------------------------------- 1 | #pragma once 2 | 3 | #include 4 | #include 5 | #include 6 | #include 7 | #include 8 | 9 | namespace mbs{ 10 | 11 | class MbsProject; 12 | 13 | class Module{ 14 | public: 15 | virtual ~Module(){} 16 | 17 | const std::string &name() const noexcept { return m_name; } 18 | const std::vector &dependencies() const noexcept { return m_dependencies; } 19 | 20 | virtual void outputToCmake(std::ostream &out, const MbsProject *moduleData) const = 0; 21 | virtual void outputLinkingToCmake(std::ostream &out) const = 0; 22 | 23 | static Module* loadModule(YAML::const_iterator module); 24 | 25 | Module(const Module &) = delete; 26 | Module &operator=(const Module&) = delete; 27 | 28 | protected: 29 | Module(const std::string &name, const YAML::Node &node); 30 | 31 | void outputFileList(std::ostream &out) const; 32 | void outputIncludeList(std::ostream &out, const std::string &targetName, const MbsProject *moduleData) const; 33 | 34 | private: 35 | std::string m_name; 36 | std::filesystem::path m_modulePath; 37 | std::vector m_dependencies; 38 | std::vector m_headers; 39 | std::vector m_sourceFiles; 40 | 41 | static void loadFileList(std::vector *vector, const std::filesystem::path &path); 42 | static void printPathInSourceSet(const std::filesystem::path &path, std::ostream &out); 43 | static std::pair parseDependencyDeclaration(const std::string &dependencyDeclaration); 44 | void buildDependencyList(std::set *dependencies, const MbsProject *moduleData, const Module *module) const; 45 | }; 46 | } 47 | -------------------------------------------------------------------------------- /modules/libmbs/source/ApplicationModule.cpp: -------------------------------------------------------------------------------- 1 | #include "mbs/ApplicationModule.h" 2 | 3 | using namespace mbs; 4 | 5 | void ApplicationModule::outputToCmake(std::ostream &out, const MbsProject *moduleData) const { 6 | outputFileList(out); 7 | out << "add_executable(module-" << name() << " ${MBS_MODULE_" << name() << "_FILES})" << std::endl; 8 | outputIncludeList(out, "module-" + name(), moduleData); 9 | out << "set_target_properties(module-" << name() << " PROPERTIES OUTPUT_NAME " << name() << ")" << std::endl; 10 | } 11 | 12 | void ApplicationModule::outputLinkingToCmake(std::ostream &out) const { 13 | for(const std::string &dependency : dependencies()){ 14 | out << "target_link_libraries(module-" << name() << " module-" << dependency << ")" << std::endl; 15 | } 16 | } 17 | -------------------------------------------------------------------------------- /modules/libmbs/source/LibraryModule.cpp: -------------------------------------------------------------------------------- 1 | #include "mbs/LibraryModule.h" 2 | 3 | #include "mbs/MbsException.h" 4 | 5 | using namespace mbs; 6 | 7 | LibraryModule::LibraryModule(const std::string &name, const YAML::Node &node) : Module(name, node) { 8 | if(!node["library-type"]) throw MbsException("The library-type property is required for modules of type library."); 9 | std::string libraryType = node["library-type"].as(); 10 | 11 | if(libraryType == "static") { 12 | m_isStatic = true; 13 | m_isDynamic = false; 14 | }else if(libraryType == "dynamic"){ 15 | m_isStatic = false; 16 | m_isDynamic = true; 17 | }else if(libraryType == "both"){ 18 | m_isStatic = true; 19 | m_isDynamic = true; 20 | }else{ 21 | throw MbsException("The library-type property must be \"static\". \"dynamic\", or \"both\"."); 22 | } 23 | } 24 | 25 | void LibraryModule::outputToCmake(std::ostream &out, const MbsProject *moduleData) const { 26 | outputFileList(out); 27 | if(m_isStatic){ 28 | out << "add_library(module-" << name() << "-static STATIC ${MBS_MODULE_" << name() << "_FILES})" << std::endl; 29 | outputIncludeList(out, "module-" + name() + "-static", moduleData); 30 | out << "set_target_properties(module-" << name() << "-static PROPERTIES OUTPUT_NAME " << name() << ")" << std::endl; 31 | } 32 | if(m_isDynamic){ 33 | out << "add_library(module-" << name() << "-dynamic SHARED ${MBS_MODULE_" << name() << "_FILES})" << std::endl; 34 | outputIncludeList(out, "module-" + name() + "-dynamic", moduleData); 35 | out << "set_target_properties(module-" << name() << "-dynamic PROPERTIES OUTPUT_NAME " << name() << ")" << std::endl; 36 | } 37 | } 38 | 39 | void LibraryModule::outputLinkingToCmake(std::ostream &out) const { 40 | for(const std::string &dependency : dependencies()){ 41 | if(m_isStatic) out << "target_link_libraries(module-" << name() << "-static module-" << dependency << ")" << std::endl; 42 | if(m_isDynamic) out << "target_link_libraries(module-" << name() << "-dynamic module-" << dependency << ")" << std::endl; 43 | } 44 | } 45 | -------------------------------------------------------------------------------- /modules/libmbs/source/MbsProject.cpp: -------------------------------------------------------------------------------- 1 | #include "mbs/MbsProject.h" 2 | 3 | #include 4 | #include 5 | 6 | #include "mbs/MbsException.h" 7 | #include "mbs/Module.h" 8 | 9 | using namespace mbs; 10 | 11 | MbsProject::MbsProject(const std::string &mbsFile) { 12 | YAML::Node rootNode = YAML::LoadFile(mbsFile); 13 | verifyFormatVersion(rootNode); 14 | loadModules(rootNode); 15 | } 16 | 17 | 18 | MbsProject::~MbsProject() { 19 | for(Module *module : m_modules){ 20 | delete module; 21 | } 22 | } 23 | 24 | void MbsProject::outputToCmake(const std::string &cmakeFile) { 25 | try { 26 | std::ofstream fout; 27 | fout.exceptions(std::ios::failbit | std::ios::badbit); 28 | fout.open(cmakeFile); 29 | 30 | fout << "#This file was generated by the Modular Build System (mbs), available at https://github.com/john01dav/mbs\n" 31 | "#It is not for human modification. To add source files to this project, add them in the appropriate\n" 32 | "#directory then re-run mbs." << std::endl; 33 | 34 | for(Module *module : m_modules){ 35 | module->outputToCmake(fout, this); 36 | fout << std::endl; 37 | } 38 | 39 | for(Module *module : m_modules){ 40 | module->outputLinkingToCmake(fout); 41 | } 42 | 43 | }catch(std::exception &e){ 44 | throw MbsException("Failed to write the cmake file " + cmakeFile + " with reason " + e.what() + "."); 45 | } 46 | } 47 | 48 | const Module* MbsProject::getModule(const std::string &name) const { 49 | for(Module *module : m_modules){ 50 | if(module->name() == name){ 51 | return module; 52 | } 53 | } 54 | return nullptr; 55 | } 56 | 57 | void MbsProject::verifyFormatVersion(const YAML::Node &rootNode) { 58 | if(!rootNode["mbs-format-version"]) throw MbsException("The mbs-format-version property must exist in mbs.yml"); 59 | 60 | unsigned version = rootNode["mbs-format-version"].as(); 61 | 62 | if(version < MIN_MBS_FORMAT_VERSION || version > MAX_MBS_FORMAT_VERSION){ 63 | throw MbsException("The mbs version " + std::to_string(version) + " is not supported by this version of mbs."); 64 | } 65 | } 66 | 67 | void MbsProject::loadModules(const YAML::Node &rootNode) { 68 | if(!rootNode["modules"]) throw MbsException("The modules node must exist."); 69 | 70 | const YAML::Node moduleNode = rootNode["modules"]; 71 | 72 | if(!moduleNode.IsMap()) throw MbsException("The modules node must be a map"); 73 | 74 | for(YAML::const_iterator it=moduleNode.begin();it!=moduleNode.end();++it){ 75 | m_modules.push_back(Module::loadModule(it)); 76 | } 77 | } -------------------------------------------------------------------------------- /modules/libmbs/source/Module.cpp: -------------------------------------------------------------------------------- 1 | #include "mbs/Module.h" 2 | 3 | #include 4 | #include 5 | #include 6 | #include 7 | 8 | #include "mbs/MbsException.h" 9 | #include "mbs/ApplicationModule.h" 10 | #include "mbs/LibraryModule.h" 11 | #include "mbs/MbsProject.h" 12 | 13 | using namespace mbs; 14 | 15 | Module* Module::loadModule(YAML::const_iterator module) { 16 | std::string name = module->first.as(); 17 | YAML::Node node = module->second; 18 | 19 | if(!node["type"]) throw MbsException("The module " + name + " does not have a type property."); 20 | 21 | std::string type = node["type"].as(); 22 | 23 | if(type == "library"){ 24 | return new LibraryModule(name, node); 25 | }else if(type == "application"){ 26 | return new ApplicationModule(name, node); 27 | }else{ 28 | throw MbsException("Unknown module type \"" + type + "\" in module " + name + "."); 29 | } 30 | } 31 | 32 | Module::Module(const std::string &name, const YAML::Node &node) 33 | : m_name(name), m_modulePath(std::filesystem::path("./modules") / std::filesystem::path(name)) 34 | { 35 | std::filesystem::path includePath = m_modulePath / std::filesystem::path("include"); 36 | std::filesystem::path sourcePath = m_modulePath / std::filesystem::path("source"); 37 | loadFileList(&m_headers, includePath); 38 | loadFileList(&m_sourceFiles, sourcePath); 39 | 40 | if(node["dependencies"]){ 41 | const YAML::Node dependenciesNode = node["dependencies"]; 42 | if(!dependenciesNode.IsSequence()) throw MbsException("The dependencies node of the module " + name + " is not a sequence."); 43 | for(YAML::const_iterator it=dependenciesNode.begin();it!=dependenciesNode.end();++it){ 44 | m_dependencies.push_back(it->as()); 45 | } 46 | } 47 | } 48 | 49 | void Module::loadFileList(std::vector *vector, const std::filesystem::path &path) { 50 | for(const std::filesystem::directory_entry &entry : std::filesystem::recursive_directory_iterator(path)){ 51 | if(entry.is_regular_file()){ 52 | vector->push_back(entry.path()); 53 | } 54 | } 55 | } 56 | 57 | void Module::outputFileList(std::ostream &out) const { 58 | out << "set(MBS_MODULE_" << m_name << "_FILES" << std::endl; 59 | 60 | std::for_each(m_headers.begin(), m_headers.end(), std::bind(&Module::printPathInSourceSet, std::placeholders::_1, std::ref(out))); 61 | std::for_each(m_sourceFiles.begin(), m_sourceFiles.end(), std::bind(&Module::printPathInSourceSet, std::placeholders::_1, std::ref(out))); 62 | 63 | out << ")" << std::endl; 64 | } 65 | 66 | void Module::outputIncludeList(std::ostream &out, const std::string &targetName, const MbsProject *moduleData) const { 67 | out << "target_include_directories(" << targetName << " PRIVATE modules/" << m_name << "/include)" << std::endl; 68 | 69 | std::set dependencies; 70 | buildDependencyList(&dependencies, moduleData, this); 71 | for(const std::string &dependency : dependencies){ 72 | out << "target_include_directories(" << targetName << " PRIVATE modules/" << dependency << "/include)" << std::endl; 73 | } 74 | } 75 | 76 | void Module::printPathInSourceSet(const std::filesystem::path &path, std::ostream &out) { 77 | out << " " << path.string() << std::endl; 78 | } 79 | 80 | std::pair Module::parseDependencyDeclaration(const std::string &dependencyDeclaration) { 81 | auto it = std::find(dependencyDeclaration.rbegin(), dependencyDeclaration.rend(), '-').base()-1; 82 | std::string moduleName(dependencyDeclaration.begin(), it); 83 | std::string dependencyType(it+1,dependencyDeclaration.end()); 84 | 85 | if(dependencyType != "static" && dependencyType != "dynamic"){ 86 | throw MbsException("Improper library type specification: " + dependencyType); 87 | } 88 | 89 | return {moduleName, dependencyType}; 90 | } 91 | 92 | void Module::buildDependencyList(std::set *dependencies, const MbsProject *moduleData, const mbs::Module *module) const { 93 | for(const std::string &dependencyName : module->m_dependencies){ 94 | auto parsedDependencyDeclaration = parseDependencyDeclaration(dependencyName); 95 | if(dependencies->count(parsedDependencyDeclaration.first) == 0){ //if this is the first time that this module is being processed in this context 96 | dependencies->insert(parsedDependencyDeclaration.first); 97 | const Module *dependency = moduleData->getModule(parsedDependencyDeclaration.first); 98 | if(dependency == nullptr) throw MbsException("Unknown module " + parsedDependencyDeclaration.first + " listed as dependency."); 99 | if(dependency != this) { //allow for circular dependencies 100 | buildDependencyList(dependencies, moduleData, dependency); 101 | } 102 | } 103 | } 104 | } -------------------------------------------------------------------------------- /modules/mbs/source/main.cpp: -------------------------------------------------------------------------------- 1 | #include 2 | 3 | #include 4 | #include 5 | 6 | int main(int argc, char *argv[]){ 7 | if(argc != 3){ 8 | std::cerr << "Usage: " << argv[0] << " " << std::endl; 9 | return -1; 10 | } 11 | 12 | try{ 13 | mbs::MbsProject project(argv[1]); 14 | project.outputToCmake(argv[2]); 15 | }catch(mbs::MbsException &e){ 16 | std::cerr << "Failed to process mbs project: " << e.what() << std::endl; 17 | return -1; 18 | } 19 | 20 | return 0; 21 | } --------------------------------------------------------------------------------