Getting started may be the most challenging part of every new library. This guide is describing how to start with the library quickly and effectively
Library is primarly hosted on Github.
You can get it with:
Downloading latest release from releases area on Github
masterbranch for latest stable version
developbranch for latest development
Clone from Github¶
This is used when you do not have yet local copy on your machine.
Open console and navigate to path in the system to clone repository to. Use command
Clone repository with one of available
git clone --recurse-submodules https://github.com/MaJerle/lwowcommand to clone entire repository, including submodules
git clone --recurse-submodules --branch develop https://github.com/MaJerle/lwowto clone development branch, including submodules
git clone --recurse-submodules --branch master https://github.com/MaJerle/lwowto clone latest stable branch, including submodules
examplesdirectory and run favourite example
Update cloned to latest version¶
Open console and navigate to path in the system where your resources repository is. Use command
git pull origin master --recurse-submodulescommand to pull latest changes and to fetch latest changes from submodules on
git pull origin develop --recurse-submodulescommand to pull latest changes and to fetch latest changes from submodules on
git submodule foreach git pull origin masterto update & merge all submodules
This is preferred option to use when you want to evaluate library and run prepared examples. Repository consists of multiple submodules which can be automatically downloaded when cloning and pulling changes from root repository.
Add library to project¶
At this point it is assumed that you have successfully download library, either cloned it or from releases page. Next step is to add the library to the project, by means of source files to compiler inputs and header files in search path
lwowfolder to your project, it contains library files
lwow/src/includefolder to include path of your toolchain. This is where C/C++ compiler can find the files during compilation process. Usually using
Add source files from
lwow/src/folder to toolchain build. These files are built by C/C++ compiler
lwow/src/include/lwow/lwow_opts_template.hto project folder and rename it to
Build the project
Configuration file is used to overwrite default settings defined for the essential use case.
Library comes with template config file, which can be modified according to needs.
and it should be copied (or simply renamed in-place) and named
Default configuration template file location:
File must be renamed to
lwow_opts.h first and then copied to the project directory where compiler
include paths have access to it by using
List of configuration options are available in the Configuration section. If any option is about to be modified, it should be done in configuration file
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
/** * \file lwow_opts_template.h * \brief LwOW application configuration */ /* * Copyright (c) 2020 Tilen MAJERLE * * Permission is hereby granted, free of charge, to any person * obtaining a copy of this software and associated documentation * files (the "Software"), to deal in the Software without restriction, * including without limitation the rights to use, copy, modify, merge, * publish, distribute, sublicense, and/or sell copies of the Software, * and to permit persons to whom the Software is furnished to do so, * subject to the following conditions: * * The above copyright notice and this permission notice shall be * included in all copies or substantial portions of the Software. * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES * OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE * AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT * HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, * WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR * OTHER DEALINGS IN THE SOFTWARE. * * This file is part of LwOW - Lightweight onewire library. * * Author: Tilen MAJERLE <firstname.lastname@example.org> * Version: v3.0.1 */ #ifndef LWOW_HDR_OPTS_H #define LWOW_HDR_OPTS_H /* Rename this file to "lwow_opts.h" for your application */ /* * Open "include/lwow/lwow_opt.h" and * copy & replace here settings you want to change values */ #endif /* LWOW_HDR_OPTS_H */
If you prefer to avoid using configuration file, application must define
a global symbol
LWOW_IGNORE_USER_OPTS, visible across entire application.
This can be achieved with
-D compiler option.