Automatically increase build number doesn't increment logically
Original Reporter info from Mantis: seier
-
Reporter name: Christian Blackburn
Original Reporter info from Mantis: seier
- Reporter name: Christian Blackburn
Description:
The increase build number setting doesn't mimic Visual Basic 6. Now I get this isn't VB 6, but hey they did it right and so should Lazarus. Basically, let's say I last compiled 0.25.0.24 and I've gotten enough working right that I'm ready to release it as 0.26.0.0. I'd like to be able to go into the compiler options and ask for 0.26.0.0, but once I compile, I'll wind up with 0.26.0.1. This is because the "Automatically increase build number" doesn't pay any attention to the version of last compiled program.
Additional information:
A simple workaround would be to allow -1 in the build number field if and only if Automatically increase build number is enabled. That way when it adds one to the build number it would compile to 0. However, looking at the current version of compiled application and seeing if it's lower than the version the project settings require would be my preference.
Mantis conversion info:
- Mantis ID: 16878
- Version: 0.9.28
- Fixed in version: 0.9.31 (SVN)
- Fixed in revision: 29282 (#c808e259)
- Monitored by: » seier (Christian Blackburn)
- Target version: 1.0.0
- LazTarget: 1.0