| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* Use CMAKE_CURRENT_LIST_DIR to learn the path of the currently running
file to determine location of NanoPB.
* Simplifies use in other projects.
|
|
Treat the source directory as immutable. Copy the generator directory
which previously generated files in-tree to the build directory and
then generate files.
Many emerging continuous integration build systems test builds across
multiple versions of dependencies protobuf and python versions in
particular. The previous source tree builds resulted in stale files
from the last build breaking the current build. By placing the build
files in the build directory, the build system automatically removes
stale files (removes output build directory) and regenerates them as
necessary.
|
|
* Use the system python binary and make sure the generator works with
both instead.
|
|
Do not assume that Python has already been found by CMake. Fix value of
CMake variable PYTHON_EXECUTABLE if Python 3 was found. Change minimum
supported Python version to 2.6.
This fixes a bug introduced by this commit:
d8d3b75e2e3b348d016f48cebc1be764061975d2
|
|
1) Search explicitly for python2.7
In systems where python3 is default or in build cases where the user has
already searched for and found python3 in CMake, store the python3
executable and search for python2.7.
2) Generate nanopb core protobuf files with CMake
Generate python output files used in turn by the nanopb generator
script. This removes the requirement of manually calling 'make' in the
nanopb/generator/proto directory.
3) Use nanopb options file if it exists
Look for nanopb options file and use in protobuf source and header
generation if it exists. The options file must have the same name and
path as the proto file, excluding the extension.
|
|
|
|
Renamed READMEs to README.txt to be more friendly for Windows users.
|
Kyle Manna
Oliver Lee
Petteri Aimonen