![]() ![]() Look for "Advanced options" in lower right, it's easy to miss. In that dialog you will find the command line macros used to build files. ![]() For example, each file belonging to the project, that had its compile flag on, would be compiled with the macro named "Compile single file to object file" ( "$compiler $options $includes -c $file -o $object", for the curious). ![]() While this provide enough room for customizing the build system's configuration, it clearly didn't allow for some more generic customization. If you wanted to include in your project and compile a java file, you would have to set a custom build command for that particular file, only for that file (right-click file in tree and choose properties). This is not only cumbersome (imagine having to do this for 10 or 100 java files) but impractical too. The new functionality described in this article aims to remove the above problems and allow for more customization of the build system. Goto to Settings -> Compiler -> Global compiler settings -> Other settings and click on Advanced options, you will get this dialog:įor starters, the command line macros are now paired with a list of source file extensions. So each command line macro (like the "Compile single file to object file") can now hold different macros depending on the source file extension. #Codeblocks compiler only compiling one file how to#. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |