So each command line macro (like the 'Compile single file to object file') can now hold different macros depending on the source file extension. 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. The new functionality described in this article aims to remove the above problems and allow for more customization of the build system. This is not only cumbersome (imagine having to do this for 10 or 100 java files) but impractical too. 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). While this provide enough room for customizing the build system's configuration, it clearly didn't allow for some more generic customization. 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). In that dialog you will find the command line macros used to build files.

Look for 'Advanced options' in lower right, it's easy to miss. In case you never had a look in advanced compiler options, you can find them by clicking Settings->Compiler->Other settings. This article will describe those changes and provide a simple but real world example of usage. It sure can!.Ĭode::Blocks has been recently updated so it can be configured to recognize non C/C++ files and act accordingly on them during the build process.

Code::Blocks, unfortunately, can't handle them either. This is done through the use of another program/script that possibly takes an input file and generates one (or more) files based on that input. What about other types of files though? You may want to compile java or python files but, unfortunately, Code::Blocks knows nothing about them.Īnd there's this other case: in real world projects, it's not unusual for some of the files belonging to a project to be auto-generated. This means that when it 'sees' C/C++ files in your project it knows how to compile and link them to generate the resulting binary output. As you may already know, Code::Blocks is designed mainly for C/C++ development.

Codeblocks compiler not building