release

I'm working on a large game engine that must be ported to Android. All the code is C/C++, so we are porting via the NDK. I've got everything building, but after lots of scouring, I'm still uncertain what the best method is for building Debug vs. Release versions of our .so file. Changing things by hand every time is getting old. Do you have different Application.mk files for each target? Or is there some way to include multiple targets in a single Android.mk file under the jni/ directory? Or perhaps a third option might be to write a standard makefile that sets environment variables that the

I have been developing with objective C and the Cocoa framework for quite some time now. However it is still not absolutely clear to me, when am I supposed to set object references to nil. I know it is recommended to do so right before releasing an object that has a delegate and you should also do so in the viewDidUnload method for retained subviews. But exactly when should this be done and why?. What does it accomplish exactly?. Thank you in advance. -Oscar Say you have a pointer myView defined in your class' interface: @interface MyClass { UIView *myView; } @end Then in your code, at some

I don't really know how to perform deployment from offline development to live webserver correctly in web development. I mostly resort on intuition, but this is more or less what I did until now: I have a web application in python, or php, and I am hosting it on a live webserver. I use an offline development version whose source is under svn. Now, as I develop the offline version, I will perform commits to the svn. When time has come for release, I could either: copy the code from the offline server to a temporary directory on the live webserver, then swap the old codebase with the new one (eg

Let's say I do the following: Open Xcode 7 File | New | Project | Cocoa Touch Framework Create "TestFramework" with the Swift language Create a file Hello.swift with public func hello() { print("Hello") }. From here, I can build a debug build of the framework (inside the Debug-iphoneos folder), but I cannot figure out how to build the release version of the framework (inside Release-iphoneos). I thought Archive might do it, but it doesn't. Pointers please? To get a release build, you need to change your scheme settings: Alternatively, create a new scheme for release builds. Ensure you have a

I distribute software online, and always wonder if there is a proper way to better define version numbers. Let's assume A.B.C.D in the answers. When do you increase each of the components? Do you use any other version number tricks such as D mod 2 == 1 means it is an in house release only? Do you have beta releases with their own version numbers, or do you have beta releases per version number? I'm starting to like the Year.Release[.Build] convention that some apps (e.g. Perforce) use. Basically it just says the year in which you release, and the sequence within that year. So 2008.1 would be

I've got a number of batch processes that run behind the scenes for a Linux/PHP website. They are starting to grow in number and complexity, so I want to bring a small amount of process to bear on them. My source tree has a bunch of cpp files and scripts, organized with development but not deployment in mind. After compiling all the executables, I need to put various scripts and binaries on a cluster of machines. Different machines need different executables, scripts, and config files for their batch processes. I also have a few of tools that I've written that belong on every machine. At the