Create project structure with build tools

[nicklafarge]

We need a basic structure for the project including the folder hierarchy and the associated build tools (CMAKE)

[rjpower4]

Maybe something along these lines:

.
├── CMakeLists.txt
├── cmake/
├── docs/
├── lib/
│   ├── CMakeLists.txt
│   ├── forest
│   │   ├── CMakeLists.txt
│   │   ├── include/
|   |   |   └── forest/
│   │   └── src/
│   │   └── test/
│   │       └── CMakeLists.txt
│   └── pyforest/
│       ├── CMakeLists.txt
│       └── src/
│       └── test/
│       └── pyforest/
|           ├── *.cpp 
|           └── __init__.py
├── test
└── third_party
    └── CMakeLists.txt

Thoughts? Not super sure about how to organize the python stuff.

[nicklafarge]

Looks good. I'll trust your judgement on the C++ side. A couple thoughts/questions:

• What do you think about a top-level examples/ folder to collect some sample scripts? (not quite sure how to incorporate matlab in here)
• I'm not sure pyforest will need a src directory. I imagine that we have pybind take care of all the python definitions (in pyforest/pyforest/*.cpp), so the only .py files would be either examples scripts (see above) or unit tests.
• Where do you foresee pybind11 to fit into this? Are we going to handle that with git submodules? How about the cspice header files we eventually pull from NAIF?

.
├── CMakeLists.txt
├── cmake/
├── docs/
├── examples/
│   ├── pyforest/
│   ├── matlab/
├── lib/
│   ├── CMakeLists.txt
│   ├── forest
│   │   ├── CMakeLists.txt
│   │   ├── include/
|   |   |   └── forest/
│   │   └── src/
│   │   └── test/
│   │       └── CMakeLists.txt
│   └── pyforest/
│       ├── CMakeLists.txt
│       └── test/
│       └── pyforest/
|           ├── *.cpp 
|           └── __init__.py
├── test
└── third_party
    └── CMakeLists.txt

[rjpower4]

We'll pull in pybind11 with a CMake FetchContent directive, so there's no issue there. An examples directory makes sense to me, we'll probably want to subdivide by language.

One thing, what does the user story look like in relation to installing the python directory, @nicklafarge?

[nicklafarge]

One thing, what does the user story look like in relation to installing the python directory, @nicklafarge?

I'm not sure what you mean by "installing the python directory"?