• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 21 subscribers
  • Views 3506 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

what's the function of .Opt file?

zhen li

anyone familiarize UV2 project should know there must be one *.Opt file for each project.
who can tell me what's the function of this file? I guess Opt indicate "options", is it right? if it's right, then what kind of options? compile and link options?

Parents
  • 0 in reply to Drew Davis

    "It is important to have a clean distinction between build information and individual, local IDE configuration for version control..."

    That is exactly how I came upon this!

    I was wondering why my projects kept defaulting back to 40MHz! :-(

    Having previously posted that the .opt was purely local IDE configuration (I might even have been told that by Keil), I thought I should add the update.

    "Also, when you version control your project, you typically will have read-only project files, and read-only files make uVision complain with a Yes/No modal dialog every time you change projects, which gets to be annoying."

    Indeed it does!

    I have complained here before about uVision's cavalier attitute when it comes to saving Project files. :-(

Reply
  • 0 in reply to Drew Davis

    "It is important to have a clean distinction between build information and individual, local IDE configuration for version control..."

    That is exactly how I came upon this!

    I was wondering why my projects kept defaulting back to 40MHz! :-(

    Having previously posted that the .opt was purely local IDE configuration (I might even have been told that by Keil), I thought I should add the update.

    "Also, when you version control your project, you typically will have read-only project files, and read-only files make uVision complain with a Yes/No modal dialog every time you change projects, which gets to be annoying."

    Indeed it does!

    I have complained here before about uVision's cavalier attitute when it comes to saving Project files. :-(

Children
  • 0 in reply to Andy Neil

    Since I am still using old version 3.x of uVision, I ran into this problem. I asked Keil/Arm. Unfortunately, I was told by the person who picked up my question that it is too old and he can't find information of it.

    If you save this file in version control, it can be very annoying because every time you save a file in the IDE or do any configuration change and press the save button, this file will be changed - and most of the time the changes should be ignored.

    By looking at the line details, you can tell the first 3 numbers are subdirectory, file id, type type. 

    There is one benefit of having the IDE generating this file - you can use it to verify if your IDE has all the configuration setup correct or not. So my practice is: I save this file in my version control. Every time I commit changes, I do a quick scan to see if everything is correct. However, I do not modify this file. If anything is wrong, I go back to the IDE to fix it.