Note: Everything PLATFORM_OVERRIDE-related is currenty outdated. Do not rely on the documentation here!
Edit the build configuration to your needs in `Makefile.conf`, or create a `local.conf` that sets any of the make variables documented in `Makefile.conf`. All the default values for the build configuration variables on each platform are documented in `default.conf`.
Note: Everything Makefile.conf-related is currenty outdated. Do not rely on the documentation here!
If a dependency is not found in your system's default include or library paths, you will have to specify the according paths in a make variable. Typically, this has to be done at least for YML2, libetpan and asn1c.
For an explanation of the mechanics of `PLATFORM_OVERRIDE`, see the inline comments in `Makefile.conf`.
In this guide, the platform-specific configuration will be called `local`.
The installation directory will be a subdirectory of the repository.
This is useful for testing only.
For a more detailed explanation of the mechanics of these build configuration files, and overriding defaults, see the comments in `default.conf`.
~~~
export PLATFORM_OVERRIDE=local
~~~
`./build-config/local.conf`:
Below is a sample `./local.conf` file, for orientation.
Note: Everything PLATFORM_OVERRIDE-related is currenty outdated. Do not rely on the documentation here!
Edit the build configuration to your needs in `Makefile.conf`, or create a `local.conf` that sets any of the make variables documented in `Makefile.conf`. All the default values for the build configuration variables on each platform are documented in `default.conf`.
Note: Everything Makefile.conf-related is currenty outdated. Do not rely on the documentation here!
If a dependency is not found in your system's default include or library paths, you will have to specify the according paths in a make variable. Typically, this has to be done at least for YML2, and libetpan.
For an explanation of the mechanics of `PLATFORM_OVERRIDE`, see the inline comments in `Makefile.conf`.
In this guide, the platform-specific configuration will be called `local`.
The installation directory will be a subdirectory of the repository.
This is useful for testing only.
For a more detailed explanation of the mechanics of these build configuration files, and overriding defaults, see the comments in `default.conf`.
~~~
export PLATFORM_OVERRIDE=local
~~~
`./build-config/local.conf`:
Below is a sample `./local.conf` file, for orientation.