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.
Hello all: The following is a snippet from my .uv2 project file.
### uVision2 Project, (C) Keil Software ### Do not modify ! Target (Target 1), 0x0002 // Tools: '166/167' Target (RunInRam), 0x0002 // Tools: '166/167' Group (Dave Files) Group (User Files) File 1,1,<.\Ssc.c><Ssc.c> File 1,1,<.\Can1.c><Can1.c> File 1,1,<.\Io.c><Io.c> File 1,1,<.\Main.c><Main.c> File 1,1,<.\Asc0.c><Asc0.c> File 1,2,<S:\boot\Src\Start167.a66><Start167.a66> File 1,1,<S:\boot\Src\GPT2.C><GPT2.C> File 1,1,<S:\boot\Src\CAN2.C><CAN2.C> File 1,1,<S:\boot\Src\RTC.C><RTC.C> File 2,1,<.\utility.c><utility.c> File 2,1,<.\flash.c><flash.c> File 2,1,<.\memtest.c><memtest.c> File 2,1,<.\ramtron.c><ramtron.c> File 2,1,<.\appload.c><appload.c>
uVision2 uses relative paths unless you specifically enter a full path spec. So, be careful when you add files to the project to only use relative path specifications. You can safely edit the .uv2 file to convert the full paths to relative paths. Jon
You can safely edit the .uv2 file to convert the full paths to relative paths. Any hints on editing .UV2 files...?