build-process

问题 I'm trying to automate the build process for engineering group. As part of that automation, I'm trying to get to a point where the act of applying a specific tag that adheres to a pattern will kick off an automated process that will do the following: Check out source code Create a build script from a template Build the project I'm pretty certain I could do this with a post-hook in subversion, but I'm trying to figure out a way to do this with something other than a subversion hook. Would it

问题 We have a recurring problem at my company with build breaks in our Flex projects. The problem primarily occurs because the build that the developers do on their local machines is fundamentally different from the build that occurs on the build machine. The devs are building the projects using FlexBuilder/eclipse and the build machine is using the command line compilers. Inevitably, the {projectname}-config.xml and/or the batch file that runs the build get out of sync with the project files

问题 I have been struggling trying to figure out how to conditionally include Flex libraries in an ant build based on a property that is set on the command line. I have tried a number of approaches with the <condition/> task, but so far have not gotten it to work. Here is where I am currently. I have an init target that includes condition tasks like this: <condition property="automation.libs" value="automation.qtp"> <equals arg1="${automation}" arg2="qtp" casesensitive="false" trim="true"/> <

问题 I have a library which supports a #define to control how it's built. However the library can be used by multiple EXE projects which want different versions. Can I make the app/EXE project set the #define to be used by the library when built, or set it in the solution? The only other option I can think of is creating a separate build-configuration on the library project but that would quickly get out of control. That's common for e.g unicode/non-unicode builds but then you'd end up multiplying

问题 I've done a lot of projects and a lot of different build systems and CI tools. Most recently, I've been exposed to the occasionally challenging task of adding to an autotools based environment for a reasonably sized C++ application. While I love the ease of use for the end user, I'm not so fond of dealing with m4 and all of the auto* tools from the developer side. I'm working on a reasonably large side project in my spare time and have decided that I'd like to take CMake for a test drive.

问题 In our bower.json we have this dependency: "ourpackage": "git+https://xxx.visualstudio.com/DefaultCollection/_git/ourpackage#1.2.3" I'm using alternate credentials and this works fine on my machine. When I run this on Visual Studio Team Services it fails as it doesn't have my credentials. I don't want to add my personal alternate credentials to the bower.json file. Another solution would be to just add the files to our project without using bower. Is there another solution to this? 回答1: I ran

问题 It appears that, in the transition between the Android 1.1 sdk and 1.5, Google radically changed how ant scripts using AAPT can build Android projects. Previously they support args allowing developers to specify source, res, asset, and a manifest for a particular build. Now, they seem to allow developers to specify only a single folder containing everything. While I could rewrite all our build scripts to work in this new way, I rather like our current system (as it doesn't require more hours

问题 our PWA lives here: https://m.quemesa.com and we also have native apps with the same codebase. However, we are not targeting the Cordova Browser platform (because it does not seem to be officially supported and I can’t see what benefit it adds) so we have to add slightly different code for our PWA compared to our native app builds. For example, In the PWA, we use the pure Google Analytics solution which requires 2 lines of javascript in the index.html. For our native builds, we use the

问题 There is a command line argument '/logger' for msbuild that allows you to specify a custom implemented logger when building. (https://msdn.microsoft.com/en-us/library/ms171471.aspx) msbuild.exe /? ... /logger: Use this logger to log events from MSBuild. To specify multiple loggers, specify each logger separately. The syntax is: [,][;] The syntax is: [.] The syntax is: {[,] | } The are optional, and are passed to the logger exactly as you typed them. (Short form: /l) Examples: /logger

问题 Obviously you can't really run Mac or Linux apps on Windows, but can you compile binaries for those platforms using MSVC++ for example (plugging in additional compilers and tools obviously)? For a serious build system, you don't want one build server per platform so having an automated build server which compiles for all target platforms seems quite a reasonable aim. 回答1: Crosstool-NG seems like your best option for Linux apps; they show that as one of the standard configurations. I do not