build-process

It appears the Gradle zipAlign task isn't working for me, not sure what I'm doing wrong. I've tried including the zipAlign task, and not including it, but it doesn't seem to make a difference. My gradle scripts spit out a "release" build, but it's never zipAligned according to the developer console when I try to upload my .apk. Here's my build script: buildscript { repositories { mavenCentral() } dependencies { classpath 'com.android.tools.build:gradle:0.4.2' } } apply plugin: 'android' dependencies { compile project(':facebook-android-sdk-3.0.1:facebook') compile project(':google-play

I am new to CMake and would like to ask if somebody can help in the following problem. I have C++ source and header files in their respective folders and now, I want to make a CMake text file that recursively searches for them. Currently, I am doing it in this way: CMAKE_MINIMUM_REQUIRED(VERSION 2.8) PROJECT(CarDetectorDAISY) file(GLOB_RECURSE SRCS *.cpp) file(GLOB_RECURSE HDRS *.h) ADD_EXECUTABLE(stereo_framework ${SRCS} ${HDRS}) TARGET_LINK_LIBRARIES(stereo_framework) This creates my CarDetectorDAISY.sln solution file and when I try to build it, it shows an error that header files are not

I have a lot of Java source code that requires custom pre-processing. I'd like rid of it but that's not feasible right now so I'm stuck with it. Given that I have an unfortunate problem that shouldn't have existed in the first place, how do I solve it using maven? (For the full story, I'm replacing a python-based build system with a maven one, so one improvement at a time please. Fixing the non-standard source code is harder, and will come later.) Is it possible using any existing Maven plugins to actually alter the source files during compile time? (Obviously leaving the original, unprocessed

When defining sequential build steps I use the depends attribute of the target element. I have recently seen an ant file, where the build sequence was defined by antcall elements inside the targets. To illustrate : <target name="a" depends="b"> ...</target> vs <target name="a"> <antcall target="b"/> ...</target> Is there a real difference between the two approaches? Is one of them preferable? The main difference between both approaches is that targets in depends are always executed, while targets in antcall are executed only if the containing target is. A clarifying example: <target name="a"

We have several independent builds (each independent build is a multi-project build). The main build scripts become quite big as we have a set of common tasks reused by subprojects as well as there is a lot of repeation between indepedent builds. What we are looking for is: A way to split main build file into smaller files A way to reuse some parts of the build in other independent builds What is the best way to achieve that in Gradle? Adam Murdoch Gradle 0.9 allows you to import a build script from another build script. Have a look at: Configuring the project using an external build script .

I am trying to delete files in my $(TargetDir) within visual studio before building a project. How do you have to format command line to get around this problem I am getting below? Try cd $(TargetDir) del *.tif As jvenema pointed out, your $(TargetDir) is expanding into a path containing spaces in the folder names which is breaking the delete command. I ended up using rd /s /q "$(TargetDir)" to clean out the directory. As far as I know it is working. Try adding quotes around the directory. You have to write del "$(TargetDir)*.tif" because of spaces in directory path. Old question but a couple

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. Since I'm just starting out, I'm obviously planning on digging through the documentation, FAQ, wikis, etc.

If A references assembly B 1.1 and C, and C references B 1.2, how do you avoid assembly conflicts? I nievely assumed C's references would be encapsulated away and would not cause any problems, but it appears all the dll's are copied to the bin, which is where the problem occurs. I understand the two ways around this are to use the GAC or assembly bindings? The GAC doesn't seem like the best approach to me, as I don't like assuming dlls will be there, I prefer to reference dlls from a lib directory in my solution. Where as assembly bindings don't seem robust to me, what if one version of the

I have some documentation written in OpenOffice, and I would like to include some of it as PDF files in the final build deliveries. I would like to do this with the automated build script. Is there a way to create a PDF file from OpenOffice with a command line command? OscarRyz Art of Solving has also a very good API to perform the conversion in Java. It is a little slow but it is simple enough. This is how I use it: File inputFile = new File("C:\\oreyes\\hola.doc"); File outputFile = new File("C:\\oreyes\\hola.pdf"); OpenOfficeConnection connection = new SocketOpenOfficeConnection(8100); try