Using Keil µVision 5 MDK-ARM: Difference between revisions
Appearance
No edit summary |
|||
| Line 1: | Line 1: | ||
This article will describe the necessary steps to successfully integrate the µGFX library into an existing Keil µVision 5 project. | This article will describe the necessary steps to successfully integrate the µGFX library into an existing Keil µVision 5 project. | ||
== | == Structure == | ||
Sadly Keil µVision doesn't really support a way of defining variables. Therefore, the µGFX library directory needs to be somewhere near the project directory. It seems to be a good solution to have a project structure like this: | Sadly Keil µVision doesn't really support a way of defining variables. Therefore, the µGFX library directory needs to be somewhere near the project directory. It seems to be a good solution to have a project structure like this: | ||
<pre> | |||
< | |||
. | . | ||
├── Project 1 | ├── Project 1 | ||
| Line 10: | Line 9: | ||
├── Project 3 | ├── Project 3 | ||
└── ugfx | └── ugfx | ||
</ | </pre> | ||
Revision as of 19:30, 8 December 2015
This article will describe the necessary steps to successfully integrate the µGFX library into an existing Keil µVision 5 project.
Structure
Sadly Keil µVision doesn't really support a way of defining variables. Therefore, the µGFX library directory needs to be somewhere near the project directory. It seems to be a good solution to have a project structure like this:
. ├── Project 1 ├── Project 2 ├── Project 3 └── ugfx