Could anyone suggest the best Build Tools for use in the build process when building a blackberry application.
Is it just the creation of an ANT project, does that cope with signing etc?
Is there a better tool out there? I'd prefer a lightweight Windows solution.
I normally use Automated Build Studio -- it can build ANT and it can also compile Java.
I don't know of any serious alternative to bb-ant-tools.
Related
We are using the Google Test framework (version 1.7) for unit tests in C++ project (with Visual Studio 2012 and TFS 2012). By using GoogleTestRunner for VS2012 I am able to discover the tests written in Google Test within Visual Studio and run them. So far so good :)
Now I would like to run the tests with my CI build I have set up on our TFS. Therefore I have installed the GoogleTestRunner on my build server for the user that runs our build. If I run the build (and tests) on the build server directly in Visual Studio it works - but when the build is triggered by the TFS build definition I displays the following message in the log:
No test found. Make sure that installed test discoverers & executors,
platform & framework version settings are appropriate and try again.
Any suggestion what I am missing?
Is this working for anybody at all?
Your help is highly appreciated!
Christoph
I have been able to sort it out myself :)
There is a guide showing how to get it running for NUnit. Just follow that guide and adopt it to the GoogleTestRunner:
http://bartwullems.blogspot.de/2012/10/tfs-2012-build-configure-nunit-to-run.html
I extracted the DLLs from the GoogleTestRunner.vsix file with 7zip (I assume any other Zip program would work as well). I checked in all DLLs I found there (as described in the mentioned guide) - don't know if really all DLLs are needed.
I am new to Plugin development and hence facing this issue.
I have 2 plugin projects and both the projects are part of a feature project. I want to set up an ANT build which could build the feature project and publish it to an URL or File system.
Here is the scenario:
Plugin Project A isDependentOn -> Plugin Project B.
For both these project, I wrote build files which builds them properly.
Now I created a Feature project and included both these plugins into it. However I am not able to correctly write the ANT build file or may be I am not sure of the complete process.
Any help would be greatly appreciated.
Thanks in advance. Cheers !!!
Its better use Maven with Tycho to build eclipse features and plugins in headless mode.
Refer the link Eclipse Tycho and Using Tycho
Does Android Studio support Ant builds?
I want to run a before-compilation Ant target.
Android Studio is new, so it seems possible it's not supported in favor of Gradle.
[EDIT]
So it seems that Studio isn't meant to fully support Ant builds (see comments)
It worked fine for me until now, but I suppose there are specific configuration were it won't work as well.
InteliJ IDEA 13 EAP has all Studio features and supports Ant.
I would also like to point out that Gradle also support pre-build tasks, so you might want to consider switching to Gradle.
For those who will go will make that choice, you can generate a Gradle buil from your Eclipse project (Note : I haven't tested it, but it should take you less than minutes to try it out and see if it works for your project).
[ORIGINAL REPLY]
Android Studio definitively supports Ant builds. I have been using it on my company's project and it works fine.
But you are right that it strongly recommend Gradle, making it the default compiler for all new project created with Android Studio (but you could actually switch back to Ant).
Finally, as JoeHz pointed out, Android Studio is based on the open source version of IntelliJ, so you can also go download this version (which is currently much more stable than Android Studio).
Android Studio is based on Intellij IDEA which certainly supports Ant. It can also read the Android Studio project file.
If you can deal with the two Android Studio features that currently aren't in the IDEA 13 EAP yet, you can download that and create an Ant Build.
http://blogs.jetbrains.com/idea/2013/05/intellij-idea-13-early-preview-is-out/
I am currently learning F# and preparing to write my first program. I will be using Visual Studio 10 in Windows 7 to write the code, because the F# support for MonoDevelop is a few versions behind.
My normal day-to-day development environment is Mac Os X 10.7. I have Mono and MonoDevelop installed. After I finish writing my masterpiece, how do I package it for running on Os X? What DLLs do I need to send to other Windows users so that they can run my .exe file? How do they install those DLLs?
In the Java world (where I usually live), I just package my Java code with any dependencies into a monolithic UberJAR that I can send to anyone who has the appropriate version of Java (usually 6) and they can run my code by typing
java -jar MyUberJar.jar
I routinely write code in Scala and include the Scala library, along with any other dependencies.
Is there any easy way to do something similar for .NET, and specifically for F#?
One alternative is to use the --standalone flag to fsc which will statically compile all the DLL's you need into a single large EXE. The people you send it to will still need to install Mono, but there are no other dependencies.
I think this is what most people use:
http://wix.sourceforge.net/
I say "I think" because at work we've got a release team that builds the installer package for us.
I want to know What should be default value for build configuration ? [Debug,Private,or Release] at the time of
1) Running application locally on simulator
2) Generating cod file while actually deploying on device/phone.
Configuration doesn't affect the generated code for BlackBerry projects - it only affects which projects are activated (i.e. that are built when you rebuild your workspace). So go with whatever you want - I usually pick one configuration and stick with it throughout debugging and release.
I would build in debug mode during development, so that you can step through the code. When you go to more formal testing, it would probably make sense to build in release mode, so that you're testing a more realistic build of the code. When you deploy to the device, it's usually best to build in release mode, to make sure you code is optimized to run on the device.
Using build configurations
You can specify several build
configurations for your projects. In
each build configuration, you can
choose projects are active.You can use
this functionality to create a set of
active projects to build with a
BlackBerry Application.
Source:
BlackBerry JDE Plug-in for Eclipse version 1.0 Online Help, Ch. "Building a BlackBerry Application"