> If you don't find that build number, you can always use the creation date of > your .prc file:
Actually, it looks like that won't work for me. The creation date of the .prc is actually the date it was copied to the device, not the date it was compiled, right? With users installing at all different times, it would be difficult to track. You would think there would be a way to do it from CodeWarrior. Anybody have any other iteas?
CW has no built-in build number support. Some people have done plugins to add that kind of thing; here's a few useful threads:
http://news.palmos.com/read/messages?id=149466#149466 http://news.palmos.com/read/messages?id=147596#147596 http://news.palmos.com/read/messages?id=137925#137925
I personally like the idea of using an external build script that rewrites a .RCP or .R file that you use for official builds, invoking the IDE to build the project using the cmdide.exe driver.
http://news.palmos.com/read/messages?id=101059#101059
-- Ben Combee, DTS technical lead, PalmSource, Inc. "Combee on Palm OS" weblog: http://palmos.combee.net/ Palm OS Dev Fourm Archives: http://news.palmos.com/read/all_forums/
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
