# GFlags

### Installation in Ubuntu

```bash
sudo apt install libgflags-dev
```

### Usage in CMake

```bash
# gflags
find_package(GFlags REQUIRED)  # gflags-config.cmake available
include_directories(${GFLAGS_INCLUDE_DIR}) # not DIRS

add_executable (main src/main.cpp)
target_link_libraries (main ${GFLAGS_LIBRARIES})
```

### Tutorial

* [GFlags Documentation](https://gflags.github.io/gflags/) ([CMake section](https://gflags.github.io/gflags/#cmake))
* All DEFINE macros take the same three arguments: the name of the flag, its default value, and a 'help' string that describes its use. The 'help' string is displayed when the user runs the application with the `--help` flag.

```cpp
#include <gflags/gflags.h>
DEFINE_string(config, "./config/default.yaml", "config file path");
int main(int argc, char **argv) {
    google::ParseCommandLineFlags(&argc, &argv, true);
    myslam::VisualOdometry::Ptr vo(new myslam::VisualOdometry(FLAGS_config));
    ...
}

// in visual_odometry.h
VisualOdometry(std::string &config_path);
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.hanzheteng.com/development/google-tools/gflags.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.