-
Notifications
You must be signed in to change notification settings - Fork 222
Build process explained
Maxime Vincent edited this page Jan 5, 2016
·
11 revisions
The official build process for picoTCP is a Makefile. This section will explain how this works, how modules are enabled or disabled, how a specific compiler or architecture is chosen.
make
Defaults to the GNU compiler tools (gcc, as, ld, ranlib ...)
This will result in a library, found in $PREFIX/lib, called libpicotcp.a
CROSS_COMPILE=arm-none-eabi make
Defaults to the GNU compiler tools (gcc, as, ld, ranlib ...)
tbd
CROSS_COMPILE=arm-none-eabi ARCH=cortex-m3 make
ARCH has to be define in ...
IPV4=0 make
Modules can be found in the Makefile.
tbd
Questions or remarks? Please contact us!
[email protected] | picotcp.altran.be | Twitter | Facebook
Getting Started
- Setting up the environment
- Testing
- Configuring and compiling
- Running picoTCP on Linux - Deprecated (see setting up)
- Running picoTCP on Windows
Porting
- Build process explained
- Porting the build to another compiler or IDE
- Porting picoTCP to your favorite embedded target
- Porting picoTCP to your favorite Operating System
- Example device driver
Development