Version 1.3 Released

RudeBuild version 1.3 has just been released. This release adds a wealth of under-the-hood features and improvements (some based on a gracious contribution and inspiration from user Loon Chew; thanks!):

  • Full support for files that are marked as “excluded from build” in Visual Studio, even if they are only marked as such for certain configurations or platforms.
  • RudeBuild now parses the configuration manager data out of the solution files and thus knows how to correctly build solutions with projects where the project configuration names don’t match the solution configuration names. In other words, RudeBuild should now build the project just like you would expect it to 🙂
  • There is a new solution setting that makes RudeBuild automatically specify the /bigobj compiler switch for generated projects. This is useful if you are using large unity files.
  • Support for precompiled header files that reside in a different folder from the project.
  • For Visual Studio 2010 and later projects, RudeBuild now correctly reads and writes out the <ProjectName> tag so that the $(ProjectName) macro works as expected.
  • The installer underwent some reliability fixes. In particular, the custom installation step that copies the RudeBuild.AddIn file to <MyDocuments>\Visual Studio 20??\Addins now correctly runs as the installing user instead of under a computer system account, which allows it to find the MyDocuments folder even if it is located on a user-specific network folder or has special user-specific permissions.
  • After a build, RudeBuild attempts to remove the RudeBuild_XXX.sln from Visual Studio’s most recently used file list.
  • For projects that contain both .c and .cpp files, RudeBuild now makes sure to never include them in the same unity file. Instead, the .c files get merged into a .c unity file, and similarly the .cpp files get merged into a .cpp unity file. This is because Visual Studio uses the file extension to determine whether to do a C or a C++ compile, and there are slight differences between the two.
  • Visual Studio 2012 support.

You can download the latest installer from the SourceForge project page located here

I have some more plans to make RudeBuild more user friendly, in particular when it comes to excluding files from the unity build or making certain files mutually exclusive, i.e. they shouldn’t end up in the same unity file. Stay tuned!