Hello, For me, it's still not clear why the include files (.h) are treated in such a cumbersome way in the uVision2 Project philosophy. When you have a project and you create a group -for instance- called 'Header files' then you have to specify that those files are Text documents to be able to add it to your project. The file types in the file open dialog box do not contain something separate for .h files, whereas this is the case for e.g. .c, .a* and .src files. Could someone explain me why is this? Wouldn't it be more logic, user-friendly and convenient if the .h-files would be treated the same way as .c- or .a51-files? Rgds, Geert
Note that all the headers used by a source file also appear in the project list, nested under that source file. Click the + box, and then double-click the .h file just as you'd double-click a .c file to open it. It's still not one global list of all headers, but you need not open up the .c file to open up a header file. My pet peeve in this area is that the uVision file add files dialog lets you choose "*.a" files, while the default extension for the A51 assembler is, well, .a51. uVision doesn't automatically recognize its own assember extension. C'est le code.
""*.a" files, while the default extension for the A51 assembler is, well, .a51. uVision doesn't automatically recognize its own assember extension." I thought the default was *.a* - which does recognise .a51??!!