Update README.md with new interface (#11)

Update README.md with new interface description.

Author: nradakovic

MODULE.bazel

@@ -13,7 +13,7 @@
 
 module(
     name = "score_bazel_cpp_toolchains",
-    version = "0.1.0",
+    version = "0.2.0",
     compatibility_level = 0,
 )
 

README.md

@@ -26,26 +26,27 @@ This repository is structured and versioned as a Bazel module and is intended to
 
 ```bash
 .
-├── bazel
-│   ├── extentions/              # Module extensions for GCC/QCC toolchains
-│   └── rules/                   # Bazel rule implementations for toolchains
 │
-├── configurations                # Shared and compiler-specific configuration flags
-│   ├── common/
-│   ├── gcc/
-│   └── qcc/
+├── extentions                   # Module extensions for GCC/QCC toolchains
+│   ├── BUILD
+│   └── gcc.bzl
+│
+├── rules                        # Bazel rule implementations for toolchains
+│   ├── BUILD
+│   └── gcc.bzl
 │
 ├── packages                     # Toolchain package descriptors (no binaries)
 │   ├── linux/                   # Linux toolchain versions (GCC only)
 │   ├── qnx/                     # QNX SDP/QCC toolchain metadata
 │   └── version_matrix.bzl       # Supported toolchain version definitions
 │
-├── templates                    # Templates for BUILD and cc_toolchain_config.bzl
-│   ├── common/
-│   ├── gcc/
-│   └── qcc/
+├── templates                    # Templates for toolchain definition and configuration
+│   ├── linux/
+│   ├── qnx/
+│   ├── BUILD
+│   └── BUILD.template
 │
-├── tests                        # Functional tests for toolchain validation
+├── examples                     # Functional examples for toolchain validation
 │
 ├── docs                         # Sphinx documentation sources
 │
@@ -64,9 +65,9 @@ This repository is structured and versioned as a Bazel module and is intended to
 This repository does not contain compiler binaries. </br>
 Instead:
 - Toolchain **packages** describe how to fetch compiler binaries via `http_archive` or internal artifact storage.
-- Toolchain **configurations** describe how Bazel should use the binaries.
+- Toolchain **templates** describe how Bazel should use the binaries.
 - Toolchain **rules** and **extensions** generate and register toolchains.
-- Toolchain **tests** validate the toolchains.
+- Toolchain **examples** validate the toolchains.
 - This separation provides:
     - Hermetic configurations
     - Full reproducibility
@@ -87,39 +88,40 @@ gcc.use(
     version = "12.2.0",
     use_default_package = True,
 )
-use_repo("score_gcc_toolchain", "score_gcc_toolchain_pkg")
+use_repo(gcc, "score_gcc_toolchain")
 ```
 
 ### QCC Example (QNX ARM64)
 
 ```starlark
-bazel_dep(name = "score_cpp_toolchains", version = "0.1.0")
-use_extension("@score_cpp_toolchains//bazel/extentions:gcc.bzl", "qcc")
-qcc.use(
+bazel_dep(name = "score_cpp_toolchains", version = "0.2.0")
+use_extension("@score_cpp_toolchains//bazel/extentions:gcc.bzl", "gcc")
+gcc.use(
+    target_os = "qnx",
     target_cpu = "arm64",
     sdp_version = "8.0.0",
+    version = "12.2.0",
     use_default_package = True,
 )
-use_repo("score_qcc_toolchain", "score_qcc_toolchain_pkg")
+use_repo(gcc, "score_gcc_qnx_toolchain")
 ```
 
 The registration of toolchains is done by adding command line option `--extra_toolchains=@<toolchain_repo>//:toolchain_name`
 In case above this would be:
 ```bash
 --extra_toolchains=@score_gcc_toolchain//:x86_64-linux-gcc-12.2.0
---extra_toolchains=@score_qcc_toolchain//:x86_64-linux-qcc-12.2.0
+--extra_toolchains=@score_gcc_qnx_toolchain//:x86_64-linux-sdp-8.0.0
 ```
 
 > NOTE: In case that more than one toolchain needs to be defined, the registration must be protected via config flags otherwise</br>
 the first toolchain that matches constraints will be selected by toolchain resolutions.
 
 ## Configuration Flags
 
-Shared flag sets live under:
+Shared flag sets live under: 
 
-- `configurations/common/flags.bzl`
-- `configurations/gcc/flags.bzl`
-- `configurations/qcc/flags.bzl`
+- [linux](templates/linux/cc_toolchain_flags.bzl.template)
+- [qnx](templates/qnx/cc_toolchain_config.bzl.template)
 
 These define:
 
@@ -136,6 +138,8 @@ Templates define how toolchain files are generated:
 
 - `BUILD.template`
 - `cc_toolchain_config.bzl.template`
+- `cc_gcov_wrapper.template`
+- `cc_toolchain_flags.bzl.template`
 
 These templates simplify adding:
 
@@ -152,12 +156,11 @@ Testing is part of the **integration gate pipeline**.
 Example cover:
 
 - Simple compilation ( [examples/main.cpp](./examples/main.cpp))
-- pthread linking ([examples/main_pthread.cpp](./examples/main_pthread.cpp))
 - Toolchain registration behavior ([examples/.bazelrc](./examples/.bazelrc))
 
 # Documentation
 
-Documentation uses **Sphinx** and lives in `docs/`.
+Documentation uses **Sphinx** and lives in `docs/`. (Not yet prepared!)
 
 # Adding New Toolchain Versions
 

examples/MODULE.bazel

@@ -42,7 +42,7 @@ bazel_dep(name = "rules_cc", version = "0.2.14")
 # *******************************************************************************
 bazel_dep(
     name = "score_bazel_cpp_toolchains",
-    version = "0.1.0",
+    version = "0.2.0",
 )
 local_path_override(
     module_name = "score_bazel_cpp_toolchains",