├── AUTHORS ├── COPYING ├── ChangeLog ├── INSTALL ├── Makefile.am ├── NEWS ├── README.markdown ├── bootstrap ├── cccl ├── configure.ac └── exeargs ├── Makefile ├── README.md └── exeargs.cpp /AUTHORS: -------------------------------------------------------------------------------- 1 | cccl was created by: 2 | Geoffrey Wossum 3 | 4 | The following people have contributed to cccl: 5 | Alin Serdean 6 | Geoffrey Wossum 7 | Gurucharan Shetty 8 | Joe Stringer 9 | Remko Tronçon 10 | William S Fulton 11 | 12 | A full list of contributors are available in the Git logs. 13 | -------------------------------------------------------------------------------- /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 | 676 | -------------------------------------------------------------------------------- /ChangeLog: -------------------------------------------------------------------------------- 1 | Version 0.03 2 | - Don't remove '=' in "-DMACRO=value" (William Fulton) 3 | - Discard warnings (-W*) 4 | - Bump version to 0.03 5 | 6 | Version 0.02 7 | - Added documentation on using cccl with autotools 8 | - cccl now processes "-g" option properly 9 | 10 | Version 0.01 11 | - First public release 12 | -------------------------------------------------------------------------------- /INSTALL: -------------------------------------------------------------------------------- 1 | Basic Installation 2 | ================== 3 | 4 | These are generic installation instructions. 5 | 6 | The `configure' shell script attempts to guess correct values for 7 | various system-dependent variables used during compilation. It uses 8 | those values to create a `Makefile' in each directory of the package. 9 | It may also create one or more `.h' files containing system-dependent 10 | definitions. Finally, it creates a shell script `config.status' that 11 | you can run in the future to recreate the current configuration, a file 12 | `config.cache' that saves the results of its tests to speed up 13 | reconfiguring, and a file `config.log' containing compiler output 14 | (useful mainly for debugging `configure'). 15 | 16 | If you need to do unusual things to compile the package, please try 17 | to figure out how `configure' could check whether to do them, and mail 18 | diffs or instructions to the address given in the `README' so they can 19 | be considered for the next release. If at some point `config.cache' 20 | contains results you don't want to keep, you may remove or edit it. 21 | 22 | The file `configure.in' is used to create `configure' by a program 23 | called `autoconf'. You only need `configure.in' if you want to change 24 | it or regenerate `configure' using a newer version of `autoconf'. 25 | 26 | The simplest way to compile this package is: 27 | 28 | 1. `cd' to the directory containing the package's source code and type 29 | `./configure' to configure the package for your system. If you're 30 | using `csh' on an old version of System V, you might need to type 31 | `sh ./configure' instead to prevent `csh' from trying to execute 32 | `configure' itself. 33 | 34 | Running `configure' takes awhile. While running, it prints some 35 | messages telling which features it is checking for. 36 | 37 | 2. Type `make' to compile the package. 38 | 39 | 3. Optionally, type `make check' to run any self-tests that come with 40 | the package. 41 | 42 | 4. Type `make install' to install the programs and any data files and 43 | documentation. 44 | 45 | 5. You can remove the program binaries and object files from the 46 | source code directory by typing `make clean'. To also remove the 47 | files that `configure' created (so you can compile the package for 48 | a different kind of computer), type `make distclean'. There is 49 | also a `make maintainer-clean' target, but that is intended mainly 50 | for the package's developers. If you use it, you may have to get 51 | all sorts of other programs in order to regenerate files that came 52 | with the distribution. 53 | 54 | Compilers and Options 55 | ===================== 56 | 57 | Some systems require unusual options for compilation or linking that 58 | the `configure' script does not know about. You can give `configure' 59 | initial values for variables by setting them in the environment. Using 60 | a Bourne-compatible shell, you can do that on the command line like 61 | this: 62 | CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure 63 | 64 | Or on systems that have the `env' program, you can do it like this: 65 | env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure 66 | 67 | Compiling For Multiple Architectures 68 | ==================================== 69 | 70 | You can compile the package for more than one kind of computer at the 71 | same time, by placing the object files for each architecture in their 72 | own directory. To do this, you must use a version of `make' that 73 | supports the `VPATH' variable, such as GNU `make'. `cd' to the 74 | directory where you want the object files and executables to go and run 75 | the `configure' script. `configure' automatically checks for the 76 | source code in the directory that `configure' is in and in `..'. 77 | 78 | If you have to use a `make' that does not supports the `VPATH' 79 | variable, you have to compile the package for one architecture at a time 80 | in the source code directory. After you have installed the package for 81 | one architecture, use `make distclean' before reconfiguring for another 82 | architecture. 83 | 84 | Installation Names 85 | ================== 86 | 87 | By default, `make install' will install the package's files in 88 | `/usr/local/bin', `/usr/local/man', etc. You can specify an 89 | installation prefix other than `/usr/local' by giving `configure' the 90 | option `--prefix=PATH'. 91 | 92 | You can specify separate installation prefixes for 93 | architecture-specific files and architecture-independent files. If you 94 | give `configure' the option `--exec-prefix=PATH', the package will use 95 | PATH as the prefix for installing programs and libraries. 96 | Documentation and other data files will still use the regular prefix. 97 | 98 | In addition, if you use an unusual directory layout you can give 99 | options like `--bindir=PATH' to specify different values for particular 100 | kinds of files. Run `configure --help' for a list of the directories 101 | you can set and what kinds of files go in them. 102 | 103 | If the package supports it, you can cause programs to be installed 104 | with an extra prefix or suffix on their names by giving `configure' the 105 | option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. 106 | 107 | Optional Features 108 | ================= 109 | 110 | Some packages pay attention to `--enable-FEATURE' options to 111 | `configure', where FEATURE indicates an optional part of the package. 112 | They may also pay attention to `--with-PACKAGE' options, where PACKAGE 113 | is something like `gnu-as' or `x' (for the X Window System). The 114 | `README' should mention any `--enable-' and `--with-' options that the 115 | package recognizes. 116 | 117 | For packages that use the X Window System, `configure' can usually 118 | find the X include and library files automatically, but if it doesn't, 119 | you can use the `configure' options `--x-includes=DIR' and 120 | `--x-libraries=DIR' to specify their locations. 121 | 122 | Specifying the System Type 123 | ========================== 124 | 125 | There may be some features `configure' can not figure out 126 | automatically, but needs to determine by the type of host the package 127 | will run on. Usually `configure' can figure that out, but if it prints 128 | a message saying it can not guess the host type, give it the 129 | `--host=TYPE' option. TYPE can either be a short name for the system 130 | type, such as `sun4', or a canonical name with three fields: 131 | CPU-COMPANY-SYSTEM 132 | 133 | See the file `config.sub' for the possible values of each field. If 134 | `config.sub' isn't included in this package, then this package doesn't 135 | need to know the host type. 136 | 137 | If you are building compiler tools for cross-compiling, you can also 138 | use the `--target=TYPE' option to select the type of system they will 139 | produce code for and the `--build=TYPE' option to select the type of 140 | system on which you are compiling the package. 141 | 142 | Sharing Defaults 143 | ================ 144 | 145 | If you want to set default values for `configure' scripts to share, 146 | you can create a site shell script called `config.site' that gives 147 | default values for variables like `CC', `cache_file', and `prefix'. 148 | `configure' looks for `PREFIX/share/config.site' if it exists, then 149 | `PREFIX/etc/config.site' if it exists. Or, you can set the 150 | `CONFIG_SITE' environment variable to the location of the site script. 151 | A warning: not all `configure' scripts look for a site script. 152 | 153 | Operation Controls 154 | ================== 155 | 156 | `configure' recognizes the following options to control how it 157 | operates. 158 | 159 | `--cache-file=FILE' 160 | Use and save the results of the tests in FILE instead of 161 | `./config.cache'. Set FILE to `/dev/null' to disable caching, for 162 | debugging `configure'. 163 | 164 | `--help' 165 | Print a summary of the options to `configure', and exit. 166 | 167 | `--quiet' 168 | `--silent' 169 | `-q' 170 | Do not print messages saying which checks are being made. To 171 | suppress all normal output, redirect it to `/dev/null' (any error 172 | messages will still be shown). 173 | 174 | `--srcdir=DIR' 175 | Look for the package's source code in directory DIR. Usually 176 | `configure' can determine that directory automatically. 177 | 178 | `--version' 179 | Print the version of Autoconf used to generate the `configure' 180 | script, and exit. 181 | 182 | `configure' also accepts some other, not widely useful, options. 183 | -------------------------------------------------------------------------------- /Makefile.am: -------------------------------------------------------------------------------- 1 | bin_SCRIPTS = cccl 2 | -------------------------------------------------------------------------------- /NEWS: -------------------------------------------------------------------------------- 1 | 09 Aug 2001 2 | * First public release 3 | -------------------------------------------------------------------------------- /README.markdown: -------------------------------------------------------------------------------- 1 | # cccl 2 | Unix cc compiler to Microsoft's cl compiler wrapper at https://github.com/swig/cccl 3 | 4 | ## Introduction 5 | 6 | cccl is a wrapper around Microsoft's cl.exe Visual C++ compiler. It converts 7 | traditional Unix cc command line parameters to their cl.exe equivalents. 8 | 9 | The main use for cccl is for using Unix build processes with the Microsoft 10 | C/C++ compiler. Using cccl in conjunction with ports of Unix utilities, it is 11 | possible to build many Unix packages using MSVC, without modifying the build 12 | process. This is especially useful if you want to use GNU autotools 13 | (autoconf/automake/libtool) with MSVC. 14 | 15 | ### Motivation 16 | 17 | Why would one use a wrapper script to make cl.exe act like gcc, when gcc is 18 | available for Windows? 19 | 20 | There are a few reasons but the primary reason is usually to support 21 | cross-platform projects that need to use autoconf/automake/libtool for the 22 | build process. The obvious thing might be to use gcc on all platforms. But on 23 | Windows, not all third-party libraries work with gcc, some only work with MSVC. 24 | cccl allows one to use the same build process with the MSVC compiler, but with 25 | only minimal changes to the build process. 26 | 27 | Even though it's a somewhat simple approach, the original author, Geoffery 28 | Wossum, wrote the initial version of cccl and released it for others to use as 29 | it saved him a lot of hassle in the build process. 30 | 31 | ### Usage Overview 32 | 33 | cccl assumes cl.exe is in your path. cccl is run the same way that a Unix C or 34 | C++ compiler is used. Below shows usage to compile a simple C program: 35 | 36 | ``` 37 | $ cccl main.c -o runme.exe 38 | main.c 39 | ``` 40 | 41 | By default cccl quietly passes the converted command line options to cl.exe. 42 | These can be displayed by using the `--cccl-verbose` option and can be useful 43 | for analysing compilation problems, for example: 44 | 45 | ``` 46 | $ cccl --cccl-verbose main.c -o runme.exe 47 | cl "/nologo" "main.c" "/Ferunme.exe" 48 | main.c 49 | ``` 50 | 51 | ### Getting Started 52 | 53 | First, you'll want to [install cccl](#installing-cccl). Then, you'll probably 54 | want to learn using [autotools and MSVC](#autotools-and-msvc) together. 55 | 56 | 57 | ## Installing cccl 58 | 59 | ### Quick Overview 60 | 61 | cccl is known to work on Cygwin, MinGW, MinGW-w64 and MSYS2. 62 | 63 | You can either copy the cccl script to somewhere on your system, or you can do 64 | a `./bootstrap && ./configure && make install` from the source if you have a 65 | Unixish enough environment installed. The configure and Makefile don't really 66 | do anything but copy the cccl script, though. 67 | 68 | ### Prerequisites 69 | 70 | cccl uses and hence requires ports of the following Unix utilities: 71 | - bash 72 | - grep 73 | - sed 74 | - tr 75 | - uname 76 | 77 | cccl is a bash shell script which makes use of these utilities. Therefore, you 78 | will need at the very least a Windows versions of these utilities. The easiest 79 | and best source of these (as well as many other Unix tools) has traditionally 80 | been RedHat's [Cygwin](https://cygwin.com/). Other well known Unix-like systems 81 | can also be used - 82 | [MinGW](http://mingw.org/), [MinGW-w64](https://www.mingw-w64.org/), 83 | [MSYS2](https://www.msys2.org/). 84 | 85 | Install one of these and if you are planning on using cccl to build autotools projects, make sure that 86 | you install autoconf, automake and libtool as well. 87 | 88 | ### Installing cccl 89 | 90 | Once you have a working Unix-like environment, you have two options. You 91 | may manually copy the *cccl* file to somewhere in your path, since it's just a 92 | script. Alternatively, you may do the normal Unix 93 | `./bootstrap && ./configure && make && make install` routine. 94 | 95 | ### Setting Up Your Path 96 | 97 | Obviously you'll want *cccl* to be in your path. Since cccl directly invokes 98 | *cl.exe*, you'll need to make sure *cl.exe* is in your path as well. This may have 99 | been done for you during your Visual Studio install. If not, there should be a 100 | file called *vcvars32.bat* or *vcvarsall.bat* which can be run from an MS-DOS 101 | command prompt to set your path. Visual Studio usually installs a menu item to 102 | run a *Visual Studio Command Prompt* and is commonly under the *Visual Studio 103 | Tools* menu. This invokes one of the aforementioned batch files. Refer to the 104 | documentation included with Visual Studio for more details about running the 105 | Visual Studio command line tools. Note that the GNU linker is also called 106 | *link.exe* and is usually present in the Unix-like systems running on Windows, 107 | but this shouldn't be a 108 | problem as cccl does not invoke the linker directly, it relies on *cl.exe* to 109 | invoke the appropriate Microsoft linker. 110 | 111 | ## Autotools and MSVC 112 | 113 | Autotools (autoconf, automake, libtool) and MSVC were never originally made to 114 | work together, but with cccl you can make them become reluctant friends. 115 | 116 | ### configure.ac 117 | 118 | Autoconf requires a file called *configure.ac*, which on legacy projects may 119 | still be called *configure.in*. In order to use autoconf and MSVC, make sure 120 | the following line is in your *configure.ac* file: 121 | ``` 122 | AC_CANONICAL_HOST 123 | ``` 124 | 125 | If your *configure.ac* file contains a reference to `LT_INIT`, add the `[win32-dll]` option: 126 | ``` 127 | LT_INIT [win32-dll] 128 | ``` 129 | 130 | Or if your *configure.ac* file is using the legacy, deprecated equivalent syntax and contains a reference to `AM_PROG_LIBTOOL`, add the 131 | following line *before* `AM_PROG_LIBTOOL`: 132 | ``` 133 | AC_LIBTOOL_WIN32_DLL 134 | ``` 135 | 136 | ### Makefile.am 137 | 138 | Believe it or not, your *Makefile.am* files will probably not require any 139 | changes to work. 140 | 141 | #### Convenience Libraries 142 | 143 | Convenience libraries (noinst .a targets) work fine without any changes. 144 | 145 | #### Executable Targets 146 | 147 | No changes required. However, you may want to create a resource file to add 148 | the explorer icon to the .exe file. 149 | 150 | #### Static Libraries 151 | 152 | Autotools can build static libraries (.lib files) fine. However, you will 153 | probably want the output file to have a different name under Windows (super.lib 154 | vs. libsuper.a). You can accomplish this using some automake conditionals. 155 | 156 | #### Dynamic Link Libraries (*.dll) 157 | 158 | Older versions of the autotools (2.13 and earlier) didn't really support 159 | dynamic link libraries (.dll files) very well. Newer versions of Libtool have 160 | much improved Windows support for supporting dynamic link libraries. 161 | 162 | ### Building Your Projects 163 | 164 | Once you've generated your configure script and Makefiles by running aclocal, 165 | autoheader, autoconf and automake, you're ready to compile. 166 | 167 | Before you run the configure script (from within your Unix-like system, of course), 168 | you'll need to set the compiler and linker environment variables to use cccl. 169 | 170 | ```bash 171 | export CC=cccl 172 | export CXX=cccl 173 | export LD=cccl 174 | ``` 175 | 176 | You may not need to set all these depending on whether your code base is just C 177 | or C++ and how the linker is invoked, but it is safest to set all three to 178 | begin with. 179 | 180 | The options in Visual C++ are numerous and have changed over the years but have 181 | got a bit simpler more recently. Unlike gcc, the default options are not all 182 | that good though and often need tweaking. The good news is that the compiler 183 | will often tell you if you need to add an option, for example if you have C++ 184 | code that uses exceptions (any code that uses the STL uses exceptions), you 185 | should see a warning: 186 | 187 | ``` 188 | foo.cxx(10) : warning C4530: C++ exception handler used, but unwind semantics 189 | are not enabled. Specify /EHsc 190 | ``` 191 | 192 | Modern versions require `/EHsc`, but older versions require `/GX`. Depending 193 | on the version of cl.exe, you may need to add `/GR` to enable run-time type 194 | information (RTTI). Use: 195 | 196 | ```bash 197 | export CXXFLAGS="/EHsc" 198 | ``` 199 | 200 | for new versions or for older versions: 201 | 202 | ```bash 203 | export CXXFLAGS="/GX /GR" 204 | ``` 205 | 206 | The options starting with `/` such as `/EHsc` and `/GX` are unrecognized by 207 | cccl and are therefore passed directly to cl.exe. 208 | 209 | Now, cross your fingers, and `./configure` and `make`. 210 | 211 | The [Automake silent 212 | rules](https://www.gnu.org/software/automake/manual/html_node/Automake-Silent-Rules.html) 213 | can control the verbosity of the output via the `V` variable. When `make V=1` 214 | is used, cccl will display the options passed to cl.exe as if `cccl --cccl-verbose` 215 | was used. 216 | 217 | ## Usage 218 | 219 | cc on Unix serves as a front end to the compiler and the linker. Microsoft's 220 | cl.exe can operate the same but most usage is as a compiler. 221 | 222 | ### Compiling 223 | 224 | Any traditional cc options that cccl does not convert into options for cl.exe 225 | are passed unchanged to cl.exe. So options starting with `-` may or may not 226 | be converted. Any `/` options are expected to be for cl.exe and no attempt 227 | is made to convert them; they are passed directly to cl.exe unmodified. 228 | Further details about option conversions are in the [Options](#options) 229 | section. 230 | 231 | If cccl sees a C++ file with an extension other than .cpp (i.e. .cc, .C, or 232 | .cxx), then cccl will prepend a `/Tp` option to the cl.exe command line to 233 | force cl.exe to process it as a C++ source file. 234 | 235 | ### Linking 236 | 237 | cl.exe interprets all options after `/link` to be linker options. cccl may 238 | convert some options and if necessary pass them as a linker option by adding 239 | them after `/link`. There are a few approaches to passing additional options 240 | to the linker directly. The first is to specify them as you would with cl.exe 241 | where everything after `/link` or `-link` is a linker option: 242 | 243 | ```bash 244 | cccl main.c /W3 /link /LTCG /INCREMENTAL:NO 245 | ``` 246 | 247 | The second approach is to use the cccl option `--cccl-link` which passes just 248 | the single next option to the linker. If using this approach, the above example 249 | can be rewritten as follows: 250 | 251 | ```bash 252 | cccl main.c --cccl-link /LTCG /W3 --cccl-link /INCREMENTAL:NO 253 | ``` 254 | 255 | Note that the first approach requires the compiler option `/W3` to be placed 256 | before `/link`, whereas with the second approach the compiler option `/W3` can 257 | be placed either before, after or as shown above right in between two linker 258 | options. 259 | 260 | Both of the above examples will thus invoke cl.exe as follows: 261 | 262 | ``` 263 | cl main.c /W3 /link /LTCG /INCREMENTAL:NO 264 | ``` 265 | 266 | ### Verbosity 267 | 268 | Visual C++ is unusually verbose for a compiler and displays the names of the 269 | files it is compiling and sometimes "Creating library" and similiar messages. 270 | For example, default output for compiling two or more files is shown below: 271 | 272 | ```bash 273 | $ cccl main.c stuff.c -o runme.exe 274 | main.c 275 | stuff.c 276 | Generating Code... 277 | ``` 278 | 279 | cccl supports the `--cccl-muffle` option which parses the output from cl.exe 280 | and suppresses this extra verbiage. Adding this option to the example results 281 | in silent output like traditional Unix compilers: 282 | 283 | ```bash 284 | $ cccl main.c stuff.c -o runme.exe --cccl-muffle 285 | ``` 286 | 287 | The `--cccl-verbose` option will display exactly how cl.exe is invoked: 288 | 289 | ```bash 290 | $ cccl main.c stuff.c -o runme.exe --cccl-verbose 291 | cl "/nologo" "main.c" "stuff.c" "/Ferunme.exe" 292 | main.c 293 | stuff.c 294 | Generating Code... 295 | ``` 296 | 297 | ### Slashes and Dashes 298 | 299 | All options provided to cccl beginning `/` or `-` will be converted to an appropriate 300 | option beginning with `/` and then passed on to cl.exe. 301 | However in the MinGW/MSYS and MSYS2 based operating systems, `/` options are handled differently 302 | and so cccl will instead convert them to an option beginning with `-`. 303 | 304 | For example, using `--cccl-verbose` to show how cccl converts on most operating systems: 305 | 306 | ```bash 307 | $ cccl --cccl-verbose /EHsc -g runme.cpp -o runme.exe 308 | cl "/nologo" "/EHsc" "/Zi" "runme.cpp" "/Ferunme.exe" 309 | ``` 310 | 311 | But on MSYS or MSYS2 based operating systems: 312 | 313 | ```bash 314 | $ cccl --cccl-verbose /EHsc -g runme.cpp -o runme.exe 315 | cl "-nologo" "-EHsc" "-Zi" "runme.cpp" "-Ferunme.exe" 316 | ``` 317 | 318 | These systems try to convert anything that looks like a path to a Windows equivalent 319 | but only when passing options to a native Windows executable, such as cl.exe. 320 | Absolute paths are problematic as they begin with a leading `/`. 321 | Consider the input file specified with an absolute path in the next example: 322 | 323 | ```bash 324 | $ cccl --cccl-verbose /EHsc -g /tmp/runme.cpp -o runme.exe 325 | cl "-nologo" "-EHsc" "-Zi" "-tmp/runme.cpp" "-Ferunme.exe" 326 | ``` 327 | Note how `/tmp/runme.cpp` is modified to `-tmp/runme.cpp`, which is the default handling 328 | for cccl for unknown 'options' beginning with `/`, even though a path was intended in 329 | this instance. 330 | 331 | One solution is to use `--cccl-slash` which turns off the conversion 332 | of `/` to `-` for unknown 'options': 333 | 334 | ```bash 335 | $ cccl --cccl-verbose --cccl-slash /EHsc -g /tmp/runme.cpp -o runme.exe 336 | cl "-nologo" "/EHsc" "-Zi" "/tmp/runme.cpp" "-Ferunme.exe" 337 | # What the OS passes to cl.exe is 338 | cl "-nologo" "C:/msys64/EHsc" "-Zi" "C:/msys64/tmp/runme.cpp" "-Ferunme.exe" 339 | ``` 340 | 341 | The operating system will then expand `/tmp/runme.cpp` into a Windows path, such as 342 | `C:/msys64/tmp/runme.cpp`. However, the operating system also thinks `/EHsc` 343 | is a path and mistakenly converts it into something like `C:/msys64/EHsc`. 344 | See https://www.msys2.org/docs/filesystem-paths/#automatic-unix-windows-path-conversion 345 | for more details on this system's automatic path conversions. 346 | The recommendation when using `--cccl-slash` is firstly to use `//` where a `/` option was 347 | intended as these are converted back to `/` by the operating system and secondly 348 | use a single leading `/` only for values that really are absolute paths. 349 | So correct usage would then be: 350 | 351 | ```bash 352 | $ cccl --cccl-verbose --cccl-slash //EHsc -g /tmp/runme.cpp -o runme.exe 353 | cl "-nologo" "//EHsc" "-Zi" "/tmp/runme.cpp" "-Ferunme.exe" 354 | # What the OS passes to cl.exe is 355 | cl "-nologo" "/EHsc" "-Zi" "C:/msys64/tmp/runme.cpp" "-Ferunme.exe" 356 | ``` 357 | 358 | MSYS2 provides a way to exclude `/` conversion via an environment variable. 359 | Please read their docs; below is another approach that could be used: 360 | 361 | ```bash 362 | $ MSYS2_ARG_CONV_EXCL="/EHsc" cccl --cccl-verbose --cccl-slash /EHsc -g /tmp/runme.cpp -o runme.exe 363 | cl "-nologo" "/EHsc" "-Zi" "/tmp/runme.cpp" "-Ferunme.exe" 364 | # What the OS passes to cl.exe is 365 | cl "-nologo" "/EHsc" "-Zi" "C:/msys64/tmp/runme.cpp" "-Ferunme.exe" 366 | ``` 367 | 368 | This operating system's conversion of absolute paths is very hit and miss, 369 | consider a small tweak specifying the output file with an absolute path: 370 | 371 | ```bash 372 | $ cccl --cccl-verbose --cccl-slash //EHsc -g /tmp/runme.cpp -o /tmp/runme.exe 373 | cl "-nologo" "//EHsc" "-Zi" "/tmp/runme.cpp" "-Fe/tmp/runme.exe" 374 | # What the OS passes to cl.exe is 375 | cl "-nologo" "/EHsc" "-Zi" "C:/msys64/tmp/runme.cpp" "-Fe/tmp/runme.exe" 376 | ``` 377 | 378 | The operating system does not convert the path to runme.exe. 379 | 380 | The general recommendation for appropriate path conversion is to look at all the 381 | operating system's tools. 382 | In this case `cygpath` is a great tool to do the correct conversion as follows: 383 | 384 | ```bash 385 | $ cccl --cccl-verbose /EHsc -g $(cygpath -m /tmp/runme.cpp) -o $(cygpath -m /tmp/runme.exe) 386 | cl "-nologo" "-EHsc" "-Zi" "C:/msys64/tmp/runme.cpp" "-FeC:/msys64/tmp/runme.exe" 387 | ``` 388 | Another wise choice is to use relative paths with forward slashes instead of absolute paths 389 | as these are nearly always compatible on both Unix and Windows. 390 | 391 | ### Environment 392 | 393 | cccl supports the `CCCL_OPTIONS` environment variable. The contents of the 394 | environment variable are treated as additional command line options to cccl. 395 | This can be handy for adding additional options or tweaking the verbosity 396 | options without changing the build system. For example: 397 | 398 | ```bash 399 | $ export CCCL_OPTIONS="--cccl-muffle --cccl-verbose /W3" 400 | $ cccl -O2 main.c 401 | cl "/nologo" "/W3" "/O2" "main.c" 402 | ``` 403 | 404 | and assuming `CCCL_OPTIONS` is not set, then the above is the same as: 405 | 406 | ```bash 407 | $ cccl --cccl-muffle --cccl-verbose /W3 -O2 main.c 408 | cl "/nologo" "/W3" "/O2" "main.c" 409 | ``` 410 | 411 | There is one notable difference using `CCCL_OPTIONS` compare to using actual options and 412 | that is the handling of spaces within options, for example `-I"My Headers"`. For this to 413 | work, you must pass it as a real cccl command line option and `CCCL_OPTIONS` can't be used. 414 | 415 | ### Options 416 | 417 | The following Unix compiler cc/gcc options are understood by cccl: 418 | 419 | - **-ansi** Converts to cl.exe's **/Za** 420 | - **-c** Converts to cl.exe's **/C** 421 | - **-dumpmachine** Target machine information based on info in copyright banner 422 | - **-dumpversion** Version of cl.exe based on info in copyright banner 423 | - **-g**[0-9] Converts to cl.exe's **/Zi** 424 | - **-O0** Converts to cl.exe's **/Ot** optimization option 425 | - **-Lpath** Converts to linker option **/LIBPATH:_path_** 426 | - **-llibrary** Converts to **lib_library_.lib** (except **-link**) 427 | - **-m386** Converts to cl.exe's **/G3** 428 | - **-m486** Converts to cl.exe's **/G4** 429 | - **-mpentium** Converts to cl.exe's **/G5** 430 | - **-mpentiumpro** Converts to cl.exe's **/G6** 431 | - **-o** is converted to **/Fo** for object files and **/Fe** for executables and dlls 432 | - **-pedantic** Removed/ignored, cl.exe does not support any equivalent 433 | - **-std=_standard_** Converts to cl.exe' **/std:_standard_** for **c++14**, **gnu++14**, **c11**, **gnu11** and later **standard**, otherwise removed/ignored 434 | - **-Wl,(,)** Options are passed to the linker 435 | - **-Werror** Converts to cl.exe's **/WX** 436 | - **-W** Remaining warnings removed/ignored, please provide **/W** options for warning control 437 | - **-fno-strict-aliasing** Removed/ignored 438 | - **-isystem** Converted to **/I** 439 | - **-include** Converted to **/FI** 440 | - **-MT** Due to conflict with cl.exe's **/MT** option, there is no support and cccl exits 441 | - **-mno-cygwin** Removed/ignored 442 | - **-rpath** Removed/ignored 443 | - **-shared** Converts to cl.exe's **/LD** or **/LDd** if -g is used 444 | - **\*.(cc|cxx|C)** C++ source file is passed using **/Tp** 445 | 446 | The following are cccl specific options: 447 | 448 | - **--help** Displays cccl help 449 | - **--cccl-link _OPTION_** Passes the option, _OPTION_, as a linker option 450 | - **--cccl-muffle** Removes cl.exe's verbiage (file names being compiled etc) 451 | from being displayed 452 | - **--cccl-slash** Do not convert unknown options starting with **/** to **-** 453 | - **--cccl-verbose** Displays how cl.exe is invoked 454 | - **--cccl-version** Displays cccl's version string 455 | 456 | The following are Visual C++ options 457 | 458 | - **-link** All remaining options are passed on as linker options 459 | - **/link** All remaining options are passed on as linker options 460 | 461 | All other `-` options are passed untouched to cl.exe. All `/` options are 462 | passed unmodified to cl.exe. All other non-options (file/path names) are 463 | also passed on unmodified. 464 | 465 | ## History 466 | 467 | ### Version 0.01 468 | 469 | Geoffrey Wossum (gwossum@acm.org) first wrote cccl as a Bourne shell script and 470 | released it under the GPL license at [http://cccl.sf.net](http://cccl.sf.net) 471 | on 9 August 2001. The original cccl SourceForge project page is located at 472 | [http://sf.net/projects/cccl](http://sf.net/projects/cccl). 473 | 474 | ### Version 0.03 475 | 476 | This version contained a few patches and was released in January 2003 and was 477 | the last version released on Sourceforge. 478 | 479 | ### 2003 to 2015 480 | 481 | The original was forked a few times. The known public forks are: 482 | 483 | * SWIFT http://swift.im/git/swift in the autoconf/cccl directory which was 484 | subsequently deleted. 485 | * Open vSwitch 486 | https://github.com/openvswitch/ovs/commits/master/build-aux/cccl which 487 | built on top of the SWIFT fork. 488 | * BalaBit which is described in a blog titled [Compiling autoconf/make projects under msvc](https://folti.blogs.balabit.com/2009/08/compiling-autoconfmake-projects-under-msvc-part-one/). 489 | The BalaBit fork is a lot more complex than the others and performance is consequently somewhat slower. 490 | The Git repo is at git://git.balabit.hu/folti/cccl.git. 491 | 492 | ### Version 1.0 493 | 494 | William Fulton had been using cccl with some unpublished modifications for 495 | testing and building [SWIG](http://www.swig.org) releases for many years. 496 | In 2015, these were made public and merged with the Open vSwitch fork and 497 | released on Github at https://github.com/swig/cccl under the newer GPL 498 | version 3 license. 499 | 500 | The documentation was also converted to Markdown format and brought up to date. 501 | 502 | #### New Features 503 | 504 | The main improvements in version 1.0 over the original cccl release 0.03 are: 505 | 506 | * Support for compiling and linking in a single step works with a mix of C, C++ 507 | and object files as inputs. 508 | * Support for spaces in paths, such as include paths and spaces in file names. 509 | * Support for creating dynamic link libraries (dlls). 510 | * Support for running under MinGW. 511 | * Adding control of output verbosity. 512 | * Simpler setup configuration by avoiding using link.exe directly, which 513 | previously may have incorrectly invoked the GNU linker. 514 | 515 | ### Version 1.1 (22 Aug 2019) 516 | 517 | * Convert -dll to /LD to achieve compatibility with libtool. 518 | * Ignore -rpath option. 519 | * Previously -Wl options were ignored, now they are passed to the Microsoft 520 | linker. 521 | 522 | ### Version 1.2 (24 Apr 2021) 523 | 524 | * Support -link option the same as /link. 525 | * Add conversion for -std option. 526 | 527 | ### Version 1.3 (18 Nov 2022) 528 | 529 | * Add support for space after -I and -L options. 530 | * Documentation updates. 531 | 532 | ### Version 1.4 (26 Mar 2025) 533 | 534 | * #20 Fix detection of MSYS/MSYS2 operating system. 535 | * #19 Fix --cccl-muffle to handle non-text output. 536 | * #10 Add --cccl-slash option for better path handling on MYS/MSYS2. 537 | * #15 Add support for -dumpmachine and -dumpversion. 538 | * #17 Improved -std option handling. 539 | * Add support for -include. 540 | * Add support for -Werror. 541 | 542 | ### Future 543 | 544 | The move to Github at https://github.com/swig/cccl is hoped to inject some life 545 | into the project on a modern open source platform as the Sourceforge project 546 | had been defunct for 12 years. 547 | 548 | The goal is for cccl to remain simple and lightweight so that the performance 549 | degradation added by the wrapper is kept small. Pull requests from users for 550 | bug fixes and improvements that meet these goals are encouraged. 551 | 552 | ## See Also 553 | 554 | * [msvcc.sh](https://github.com/libffi/libffi/blob/master/msvcc.sh) 555 | * [wgcc](https://sourceforge.net/projects/interix-wgcc/) is another cccl like 556 | tool for Interix but was superceded by 557 | [parity](https://github.com/mduft/parity). 558 | 559 | -------------------------------------------------------------------------------- /bootstrap: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | # bootstrap 3 | # prepares a freshly checked out autotools project to be compiled 4 | 5 | aclocal $ACLOCAL_FLAGS \ 6 | && autoconf \ 7 | && automake --add-missing --copy 8 | -------------------------------------------------------------------------------- /cccl: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # cccl 4 | # Wrapper around MS's cl.exe to make it act more like Unix cc 5 | # 6 | # Copyright (C) 2000-2025 by contributors listed in the AUTHORS file. 7 | # 8 | # This program is free software: you can redistribute it and/or modify 9 | # it under the terms of the GNU General Public License as published by 10 | # the Free Software Foundation, either version 3 of the License, or 11 | # (at your option) any later version. 12 | # 13 | # This program is distributed in the hope that it will be useful, 14 | # but WITHOUT ANY WARRANTY; without even the implied warranty of 15 | # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 16 | # GNU General Public License for more details. 17 | # 18 | # You should have received a copy of the GNU General Public License 19 | # along with this program. If not, see . 20 | 21 | 22 | usage() 23 | { 24 | cat <&1)) 63 | arch="$(echo ${cl_output_parts[8]} | tr "[:upper:]" "[:lower:]")" 64 | output="pc-windows-msvc" 65 | 66 | case $arch in 67 | x64) 68 | output="x86_64-$output" 69 | ;; 70 | 71 | # "file" command, with "libmagic", shows "Intel 80386" for gcc/clang/msvc, use i686 like on gcc/clang 72 | x86) 73 | output="i686-$output" 74 | ;; 75 | 76 | # Output triplet same as gcc and clang on ARMv8 77 | arm64) 78 | output="aarch64-$output" 79 | ;; 80 | 81 | # Output triplet same as gcc and clang on ARMv7 82 | arm) 83 | output="arm-$output" 84 | ;; 85 | 86 | *) 87 | output="unknown-$output" 88 | ;; 89 | esac 90 | 91 | echo $output 92 | exit 0 93 | ;; 94 | 95 | -dumpversion) 96 | cl_output_parts=($($prog 2>&1)) 97 | cl_version="$(echo ${cl_output_parts[6]} | tr "[:upper:]" "[:lower:]")" 98 | echo $cl_version 99 | exit 0 100 | ;; 101 | esac 102 | done 103 | 104 | processargs() 105 | { 106 | ### Run through every option and convert it to the proper MS one 107 | while test $# -gt 0; do 108 | case "$1" in 109 | -D*) optarg= ;; 110 | -*=*) optarg=`echo "$1" | sed 's/[-_a-zA-Z0-9]*=//'` ;; 111 | *) optarg= ;; 112 | esac 113 | gotparam=1 114 | 115 | case "$1" in 116 | --help) 117 | usage 118 | exit 0 119 | ;; 120 | 121 | --cccl-link) 122 | # One single option for the linker 123 | shift 124 | case "$1" in 125 | /*) 126 | linkopt+=("${slash_slash}${1:1}") 127 | ;; 128 | 129 | *) 130 | linkopt+=("$1") 131 | ;; 132 | esac 133 | ;; 134 | 135 | --cccl-muffle) 136 | # Remove the unnecessary junk that the compiler outputs to stdout 137 | muffle=1 138 | ;; 139 | 140 | --cccl-slash) 141 | slash_slash="/" 142 | ;; 143 | 144 | --cccl-verbose) 145 | verbose=1 146 | ;; 147 | 148 | --version) 149 | cat < 2 | 3 | /** Simply display the arguments passed in to the executable */ 4 | int main(int argc, char* argv[]) { 5 | std::cout << "exeargs"; 6 | for (int i=1; i