Geek Answers Handbook

The most efficient way to make 22 different builds

I am nearing completion of my first relatively simple Xcode project (custom installer), and I need to make 22 builds. Yes, it was not a typo! Each assembly distinguishes between PRODUCT_NAME, the source file in the Resources folder, and a variable indicating whether the software is a trial version or not.

From what I read so far, duplicating an existing target seems to be a way to do this when there are only a few assemblies, but is this still true for 22? It seems like an awful lot of work. What I had in mind was a way to change PRODUCT_NAME, the source files that were copied to the Resources folder, and the trial mode of boolean. But I'm stuck.

thanks

+5
source share
4 answers

My gut answer is that 22 different assemblies that differ in only one source file are wrong ...

Could the problem turn around? Include all 22 different versions of your application in one assembly and put 22 different key / license files in the .app folder, each of which unlocks one of the 22 versions.

+2
source

, , - . NSLocalizedString, (.. , ). , , .strings -.

, , .strings . .

+2

, , script, .xcodeproj sed, .

+1

, CMake .

Scripts can certainly be executed, but as soon as the project grows to a significant number of files, or if you find that you are changing the number of assemblies, changing the script can become hairy. CMake allows you to organize these scripts, so it’s at least a little easier to make modifications in the future.

+1
source

More articles:


All Articles