...
This section describes all the steps required to build a DNScDHCPc-based application. The instructions provided in this section are not intended for any particular toolchain, but instead are described in a generic way that can be adapted to any toolchain.
The best way to start building a DNSc DHCPc-based project is to start from an existing µC/TCP-IP project.
...
The first step before including the µC/DNSc HTTPs is to have a working project with the µC/TCP-IP. As previously mentioned, Micriµm may offer starting example with µC/OS-III kernels and µC/TCP-IP and even with µC/DNSc HTTPs for many evalboards.
If no project that include µC/TCP-IP is available, you should follow the µC/TCP-IP - Getting Started Guide to start with to ensure to have a working TCP/IP project before starting integrating µC/DNScproject which use fix IP address before installing µC/HTTPs. Then you can follow the following steps to build and run your a first µC/DNSc HTTPs sample application.
Including Additional Modules to the Project
Once you have a working project with your RTOS and µC/TCP-IP additional modules are needed by the Micriµm DNC client HTTP server that are not necessarily already included in your project. Therefore, be sure to add µC/CPU, µC/LIB and µC/Common to TCP-IP to your project.
Refer to the following manuals for further information about MIcrium modules:.
...
Optional module
Including µC/
...
HTTPs Source Code
Include the following files in your project tree from the µC/DNSc HTTPs source code distribution, as indicated in Figure - µC/DNSc HTTPs Source Code.
As indicated in the Figure - µC/DNSc HTTPs Source Code, all all the files in the Source folder must be added to your project tree. File under the folder Cmd can be added if µC/Shell is already included in your project. Furthermore, http-s_os.c file of the selected RTOS must be added as well as the generic http-s_os.h file that can be found in the OS folder.
For the file system, µC/HTTPs uses the network file system layer included with µC/TCP-IP located inside the uC-TCPIP/FS folder. Therefore, the header file net_fs.h inside this folder must be include to your project, no matter what file system your HTTP server is using.
If a conventional file system is used, the port should be located also inside the uC-TCPIP/FS folder. A port for the µC/FS file system is already included in this folder. If a file system other than µC/FS is used, a port template is available inside to be customize according to your file system.
If the Static file system is used, the port for this file system is located inside uC/HTTPs. Therefore, the source files under the folder name Static must be include to your project. Furthermore, The static file system configuration file must be copied in your application directory. This configuration file can be retrieve inside the folder Cfg (i.e Micrium/Software/uC-HTTPs/FS/Static/Cfg/Template).
Compiler settings
Finally, add the following include paths to your project’s C compiler settings:
\Micrium\Software\uC-DNScHTTPs
\Micrium\Software\uC-TCPIP
\Micrium\Software\uC-<OS-Version>Copying and Modifying Template Files
...