build-process

I have an issue with the generation of makefiles stage of CMake being slow which is similar to this unanswered question: CMake is slow to generate makefiles My project is made up of a top level CMakeLists.txt file which uses add_subdirectory() to add various subprojects for individual library and executable components. For a given component, the CMakeLists.txt file contains something like: add_library(mylib SHARED sourceFile1.cpp sourceFile2.cpp ... ) I can build just the contents of that directory using: make mylib If I modify the CMakeLists.txt file in the sub-directory (which I've been

My question had been addressed in this thread , but the explanation is not clear. I have this build definition in one of my pom.xml files: <build> <finalName>${my.project}</finalName> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>2.0</version> <configuration> <source>1.6</source> <target>1.6</target> </configuration> </plugin> </plugins> <extensions> <extension> <groupId>org.kuali.maven.wagons</groupId> <artifactId>maven-s3-wagon</artifactId> <version>1.1.19</version> </extension> </extensions> <resources> <resource>

When should I include PDB files for a production release? Should I use the Optimize code flag and how would that affect the information I get from an exception? If there is a noticeable performance benefit I would want to use the optimizations but if not I'd rather have accurate debugging info. What is typically done for a production app? When you want to see source filenames and line numbers in your stacktraces, generate PDBs using the pdb-only option. Optimization is separate from PDB generation, i.e. you can optimize and generate PDBs without a performance hit. From the C# Language

We have developed a software system using ActiveX/COM (VB6) technology from microsoft. In the last year, i get more and more interested in automated build processes and SCM at a whole. I intensively searched big parts of the web for information about best practices how to do scm with COM based software systems. The "problem" with COM is, that a referencing component holds the reference by an unique interface id. When you recompile the referenced component, the id may change and the reference isn't valid any more. The main problem here is, that the iid is compiled into the binary. So when i don

I remember reading an article or post somewhere years ago that suggested including a resource file in a project by referencing the .rc file instead of an already compiled .res file so that the resource is built as part of the project's build process. I have a glyphs.rc file that I currently compile using the command brcc32 glyphs.rc. In my project file I then have the statement {$R Glyphs.res}. I'd like to simplify this by changing it to something like {$R Glyphs.rc} but am unsure of the syntax. When I try using {$R Glyphs.rc} I get an error ` [DCC Error] E2161 Error: RLINK32: Unsupported

When building a C# application with Visual Studio 2008, is it possible to set a different output filename per configuration? e.g. MyApp_Debug.exe MyApp_Release.exe I tried a post-build step to rename the file by appending the current configuration, but that seems a scrappy approach. Plus it meant that Visual Studio could no longer find the file when pressing F5 to start debugging. You can achieve this by editing your project file by hand. Locate the <AssemblyName> node and add a conditional attribute to it: <AssemblyName Condition="'$(Configuration)'=='Debug'">MyApp_Debug.exe</AssemblyName>