...
This section discusses the modules available for μC/POP3c, and how they all fit together. A Windows®-based development platform is assumed. The directories and files make references to typical Windows-type directory structures. However, since μC/POP3c is available in source form, it can also be used with any ANSI-C compatible compiler/linker and any Operating System.
Below is a summary of all directories and files involved in the µC/POP3c module
...
\Micrium\Software\uC-POP3cThis is the main directory for µC/POP3c.
\Micrium\Software\uC-POP3c\DocThis directory contains all µC/POP3c documentation files, including this user’s manual.
\Micrium\Software\uC-POP3c\Cfg\TemplateThis directory contains a template of µC/POP3c configuration.
\Micrium\Software\uC-POP3c\SourceThis directory contains the µC/POP3c source code. This protocol is implemented in two OS independent files:
pop3-c.c
pop3-c.h
Note that the ‘-c’ after ‘pop3’ stands for client and thus contains ‘client’ side code.
Required modules
...
. The ‘<- Cfg’ on the far right indicates that these files are typically copied into the application (i.e., project) directory and edited based on project requirements. The ‘<- Public API’ on the far right indicates that where are located the public API which should be used by the application.
| Code Block |
|---|
\Micrium
\Software
\uC-POP3c
\Cfg
\Template
\pop3-c_cfg.h <- Cfg
\Source
\pop3-c.c
\pop3-c.h <- Public API |
\Micrium
Contains all software components and projects provided by Micrium.
\Software
This sub-directory contains all software components and projects.
\uC-POP3c
This is the main µC/POP3c directory.
Source code
\Source
This is the directory that contains all the CPU and RTOS independent source code files,