esp-idf/examples/network/sta2eth/main/idf_component.yml

## IDF Component Manager Manifest File
dependencies:
  espressif/esp_tinyusb:
    version: "^1.3.0"
    rules:
      - if: "idf_version >=4.4"
      - if: "target in [esp32s2, esp32s3]"
  dns_server:
    path: ${IDF_PATH}/examples/protocols/http_server/captive_portal/components/dns_server
  ethernet_init:
    path: ${IDF_PATH}/examples/ethernet/basic/components/ethernet_init

  idf: "^5.0"
Examples/network: Add Ethernet iface to sta-2-wired bridge * adds description about that it's not a bridge, but more like an 1:1 forwarder on L2 * add and describe mac spoofing for Ethernet interface * describe virtual networking for USB-NCM interface 2023-06-01 16:44:11 -04:00			`## IDF Component Manager Manifest File`
			`dependencies:`
			`espressif/esp_tinyusb:`
			`version: "^1.3.0"`
			`rules:`
			`- if: "idf_version >=4.4"`
			`- if: "target in [esp32s2, esp32s3]"`
feat(examples): add local components via idf_component.yml Specifying all the dependencies (managed and local) in the manifest makes it easier for users to see every component the example depends on. 2023-08-04 09:00:15 -04:00			`dns_server:`
			`path: ${IDF_PATH}/examples/protocols/http_server/captive_portal/components/dns_server`
			`ethernet_init:`
			`path: ${IDF_PATH}/examples/ethernet/basic/components/ethernet_init`
Examples/network: Add Ethernet iface to sta-2-wired bridge * adds description about that it's not a bridge, but more like an 1:1 forwarder on L2 * add and describe mac spoofing for Ethernet interface * describe virtual networking for USB-NCM interface 2023-06-01 16:44:11 -04:00
			`idf: "^5.0"`