Comments on: Multi platform build in 3 easy steps

By: Mike

Mike — Fri, 09 Nov 2007 17:19:09 +0000

That actually solves the problem for me in a far less complicated way than I had been considering. For one thing it would allow me to still promote the files. Thanks – Mike

By: Rob

Rob — Fri, 09 Nov 2007 15:05:34 +0000

Without digging deeper into your specific environment, one method comes to mind on how you can create platform specific files for your builds that use the same filename so you don’t have to create additional complex logic in your build scripts.

Element links allow you to create “aliases” to your files. Elements are like symlinks, except they 100% managed in AccuRev. An element link can be created to point to whatever platform you are compiling on.

For example, let’s say you have 3 config files named config.win, config.unix, config.mac in the config directory. You can then create an element link called config.ini that would point to the .win in the windows stream, .unix in the unix stream, and .mac in the mac stream.

This allows you to manage all the config files in one place and then use pointers in the applicable streams.

Again, not sure this is how your environment is setup, but I’d be happy to drill down further with you.

Regards,
Rob

By: Mike

Mike — Fri, 09 Nov 2007 00:08:23 +0000

I like it. Is there a sensible way to handle environment specific files that are sprinkled throughout the tree and intermingled in the same folders with files that are promoted? We have this situation between qa, stage and prod.

Thanks – Mike