build-process

Visual Studio post build events stuck waiting for executable to finish before running app in debug mode

混江龙づ霸主 提交于 2019-11-29 00:38:45
问题 Part of the post build on my project is the execution of a program I wrote for testing the main application. Unfortunately, the post build process in visual studio locks up waiting for the executable to exit. So, i'm stuck closing my test program in order to have the post build process complete and my application run. How do I change this so VS does not wait for the program to return before launching? Thanks. 回答1: I also found that the start trick didn't work and downloading a separate tool

Visual Studio IDE: I want it to make a sound after it compiles so I can get back to work

烈酒焚心 提交于 2019-11-28 20:04:24
Would be a nice thing - do I have to write a script or can't I just tweak the build script to do some task? rjzii Windows already has support for this, go to the Control Panel and open up Sounds and Audio Devices. Under the Sounds tab there is a section for program events. If you scroll down far enough one of the sections will be Microsoft Visual Studio. Then just pick the sound you want to hear for Build Succeeded and Build Failed. You will need to restart Visual Studio after choosing your sounds. StingyJack If you don't want to enable it for every single build, you can make an application

Adding classpath to jetty running in maven integration-test

倾然丶 夕夏残阳落幕 提交于 2019-11-28 19:46:23
I'm trying to set up integration tests for a Maven project that produces a war file. (As seen here http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin/ .) However I the war file requires a bunch of .properties files on the classpath, that I don't want to bundle in the war. Is there a way (preferably through plugin configuration) to add a folder to the classpath used by jetty? I Googled this and found http://markmail.org/message/awtqrgxxttra3uxx but this, as far as I can tell, does not actually work at all. The .properties files are not found. This should be possible using the

How to Increment Version Number via Gulp Task?

一世执手 提交于 2019-11-28 19:33:47
I would like to replace a string indicating version number in a javascript file ( myConstantsFile.js ), with another string. So, for example, my version number looks like this: "01.11.15", written like this in myConstantsFile.js with other constants: .constant('productVersion', '1.11.15'); Right now, my task looks like this: gulp.task('increment-version', function(){ gulp.src(['./somedir/myConstantsFile.js']) .pipe(replace(/'productVersion', '(.*)'/g, '99.99.99')) .pipe(gulp.dest('./somedir/')); }); As you can see, I am using a constant, not running incrementation code , which would look like

Maven - How to build multiple Independent Maven projects from one project

余生颓废 提交于 2019-11-28 19:15:50
I have 3 maven projects WebComponents DataComponents ServiceComponents When i build each of the projects i have to go into each folder and run mvn clean install on each of the projects. I have looked into multi module projects and most of the resources i see suggest that i have to make a change to the structure of my existing projects. Is it possible to have a new project that will build each of the independent projects without me having to make any changes to anything in the existing project including their individual pom files? I can probably achieve this by writing a simple batch file that

Is continuous integration worth it for small projects?

醉酒当歌 提交于 2019-11-28 18:47:04
I've been pushing for continuous integration at my company since I joined 5 months ago, but having seen the type of applications we work on I'm starting to think that it might not be worth the effort of setting up each and every project for continuous integration. If you work in a development department where the average project takes 2-3 weeks and once it's deployed you seldom if ever have to worry about it, is continuous integration worth the hassle of setting it up? Probably depends on your process. If you have unit tests that cover your code, then continuous integration is worth every bit.

Overriding a default option(…) value in CMake from a parent CMakeLists.txt

我是研究僧i 提交于 2019-11-28 18:32:09
I am trying to include several third-party libraries in my source tree with minimal changes to their build system for ease of upgrading. They all use CMake, as do I, so in my own CMakeLists.txt I can use add_subdirectory(extern/foo) for libfoo. But the foo CMakeLists.txt compiles a test harness, builds documentation, a shared library which I don't need, and so on. The libfoo authors had the foresight to control these via options - option(FOO_BUILD_SHARED "Build libfoo shared library" ON) for example - which means I can set them via the CMake command line. But I would like to make that off by

Sharing build artifacts between jobs in Hudson

ぃ、小莉子 提交于 2019-11-28 18:13:20
I'm trying to set up our build process in hudson. Job 1 will be a super fast (hopefully) continuous integration build job that will be built frequently. Job 2, will be responsible for running a comprehensive test suite, at a regular interval or triggered manually. Job 3 will be responsible for running analysis tools across the codebase (much like Job 2). I tried using the "Advanced Projects Options > use custom workspace" feature so that code compiled in Job 1 can be used in Job 2 and 3. However, it seems that all build artifacts remain inside that Job 1 workspace. I'm I doing this right? Is

Have CMake recursively scan folders?

纵然是瞬间 提交于 2019-11-28 18:11:48
How do I set up CMake to recursively scan a given directory and determine the list of source files? My project is a shared library. I have a folder structure similar to this: / src/ # Source files in an arbitrary tree include/ # Headers, tree mirrors that of the src/ folder examples/ # Executable code examples that link against the library CMakeLists.txt I want CMake to recursively scan src and include and determine the list of source and header files in my project, regardless of the directory structure. I also want to avoid: Polluting the src/ and include/ directories with endless CMakeLists

What strategies have you used to improve build times on large projects?

依然范特西╮ 提交于 2019-11-28 17:55:00
I once worked on a C++ project that took about an hour and a half for a full rebuild. Small edit, build, test cycles took about 5 to 10 minutes. It was an unproductive nightmare. What is the worst build times you ever had to handle? What strategies have you used to improve build times on large projects? Update: How much do you think the language used is to blame for the problem? I think C++ is prone to massive dependencies on large projects, which often means even simple changes to the source code can result in a massive rebuild. Which language do you think copes with large project dependency