The crate in the example has no C or C++ code, yet but a
c_cpp_properties.json is generated. cpptools starts as soon as the file
exists, and ${workspaceFolder}/** recursively reaches the whole workdir
through the oe-workdir link, plus rootfs-dbg/usr/src/debug/**
(including kernel sources).Why is this needed at all? I'm not very rusty. But I would assume that with Yocto C/C++ libraries linked by Rust binaries should go into separate packages rather than building the C/C++ code bundled. That would then mean that ide-sdk would generate either a Cargo or a C/C++ configuration for the IDE without a need for mixed setups. If there is a need for bundled C/C++ setups this should probably come with test coverage and therefore also with a example using this features. Regards, Adrian
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#248848): https://lists.openembedded.org/g/openembedded-core/message/248848 Mute This Topic: https://lists.openembedded.org/mt/121938789/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
