Page 1 of 1

An idea for automating my builds...

Posted: Wed Jan 11, 2006 4:15 pm
by wolbrink
Previously I mentioned that I'd like a way to automatically specify the Product Version via miabuild.exe. (I really hate having manual steps in my build process, and this is the only one!)

But now, I'd like to slightly change my request. I noticed that I can specify compiler variables via miabuild. In light of this, and to provide the ultimate in flexibility, I'd like the ability to specify any project option (which is editable with a text box) with the use of a compiler variable.

For example, let's say I were to add a compiler variable called: BUILD_VER. I'd like to be able to put #BUILD_VER# as the Product Version in the "Project Options" dialog.

This would:
1. Solve my problem, allowing me fully automated builds.
2. Require no changes to miabuild.
3. Provide for future automation that I can't think of. :D

--Troy

Posted: Wed Jan 11, 2006 10:44 pm
by scott
I'll second that suggestion. We need it for the exact same reason in fact, but I can see the potential in the flexibility of the broad use of compiler options.

Posted: Thu Jan 12, 2006 9:01 pm
by MichaelNesmith
This feature has been added into the latest update.

Posted: Mon Jan 16, 2006 4:25 pm
by wolbrink
Thank you! :D

Posted: Tue Jan 17, 2006 1:03 am
by casic
The new feature is great! Thanks a lot!

Would it be possible to set the product version also to the built setup-exe? (I work mainly with the product version to automate processes, f.e. automated upload...).

Thanks,

Markus

Posted: Tue Jan 17, 2006 7:52 am
by MichaelNesmith
Hi Markus

This is indeed possible - just use compiler variables for that version field also :)

Posted: Tue Jan 17, 2006 8:58 am
by casic
Sorry, I meant:

I currently use a compiler var to set the version. When the setup was built and I look at the properties of the generated setup.exe only the file version is set. Would it be possible to set also the product version (and maybe the product name, f.e. to $TITLE$)?

Thank you,

Markus

Posted: Tue Jan 17, 2006 9:08 am
by MichaelNesmith
Oh, I am sorry I misunderstood. Currently those fields are not set during builds - I'll pass your recommendation to the product team!

Posted: Wed Jan 18, 2006 7:20 pm
by stampy
I've installed the 5.0.1 update and find that I can substitute a compiler variable in my Output/Custom Folder and it builds where I would expect it. However, when I "compile" it, I get the error: "Unable to create directory". If I change the path back to a hardcoded value, it compiles ok.

Also when I substituted the Output filename with a compiler variable I can't debug the setup: "Please make a debug build of your project..." and I have already built with the "debug" checkbox selected.

A bug perhaps? Or am I making substitutions where I shouldn't be?

Thanks!

Posted: Wed Jan 18, 2006 9:16 pm
by MichaelNesmith
I believe both issues you have reported here are limitations in the substitution mechanism. I'd recommend not using compiler variables until everything is tested and working properly to avoid these issues.