µC/HTTPs
The following are the steps to follow to include µC/HTTPs into your project:
http-s_cfg.h
filehttp-s_instance_secure.c/.h
filesModule Configuration” for a detailed explanation of each configuration variables.
Instance Configuration” for more details). If your application requires a secured HTTP server instance, the http-s_instance_secure_cfg.c/.h
pair of files should be used as template instead.
The configuration files includes with µC/HTTPs are templates and must be modified according to your application specific needs and constrains.
/Micrium/Software/uC-HTTPs/Source
folder. The OS port’s files must also be added to your project. The ports for uC/OS-II and uC/OS-III are located inside the /Micrium/Software/uC-HTTPs/OS
folder.
uC-TCPIP/FS
folder. Therefore, the 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-V4 file system is already included in this folder. If a file system other than µC/FS is used, a port template is available inside the uC-TCPIP/FS/Template
folder 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 http-s_fs_static.c/.h
must be include to your project. They are located inside the Micrium/Software/uC-HTTPs/FS/Static
folder. Furthermore, The configuration file template http-s_fs_static_cfg.h
must be copied in your application directory. This configuration file can be retrieve inside the Micrium/Software/uC-HTTPs/FS/Static/Cfg/Template
folder.
/Micrium/Software/uC-HTTPs/
/Micrium/Software/uC-TCPIP-V2/
Since uC/HTTPs requires the use of others modules (µC/LIB, µC/CPU, RTOS, file system), the path leading to the source code of those modules must also be included in your compiler include paths. Please refer to the user manual of each module for details on the path to add.