Hello,
I just installed uVision3 and am trying to get familiar with using it. I have an existing project that I have set up using both the ARM ADS 1.2 IDE as well as the Microsoft Visual Studio 2003 IDE. In each of these cases the project workspace can be set up to mimic the directory structure of the source files on the disk. When setting up such a project in an IDE I normally first create all of the folders and sub-folders, then add the source files as appropriate. So, in uVision3 I tried to do the same but immediately ran into a problem. For a new project, in the "Project Workspace" it automatically creates a top-level folder named "Target 1". First, how do I rename this to a meaningful name of my choosing? Next, I tried to create some groups and arrange them to match the directory structure of the files on my disk. However, it appears that groups can only exist at the same level and cannot be placed within another group. Hopefully this is due to my lack of knowledge of the IDE rather than a severe shortcoming of the IDE itself (otherwise, there's no point in even having groups at all). How do I make a group a member of another group? I'm not adverse to using a binary editor to tewak the files created by uVision3 if necessary. Thanks for your help.
Ray
http://www.keil.com/support/man/docs/uv3/uv3_ca_projtargfilegr.htm
Reinhard,
Thank you very much for your quick reply. Unless I'm still missing something, I interpret the information on the link you gave to mean that yes, the target name can be changed to any desired sequence of acceptable characters, but no, groups cannot be set up to contain other groups - they can only contain files. Thus, the Project Workspace cannot be set up to represent the same "directory tree" structure that the files are arranged in on the hard disk itself. Maybe this convenience will be available in a future revision.
Thanks, Ray
"groups cannot be set up to contain other groups"
Correct - they can't.
Ray; I may be missing something in your post but I believe you can set up your project much like the file structure 'picture' in the project workspace. First you can have multiple targets. These targets contain the same groups in each target. You can assign different compiler/linker actions by file or by group within a given target. A group name and a file name in the project workspace is just an entry in the .uv2 project directory. These entries can contain full path names to your source files. While it seems more convenient to me to have all the source files in the top project directory there is no reason that you can't have sub-directories in the main project directory for you source files. When you add a source file to a group, you just have to browse to the source file to include the full path name. The project workspace will still display the fake file folders under each group. For example, the Include files and Lib files are in totally separate directories but directly addressable from the project workspace. Hope I did not just spread muddy waters in this post. Bradford