Vscode-cmake-tools: No public API?

[Rettgp]

Is there a timeline on when public API will be added back in? It appears that the activate() is no longer returning anything and there is a TODO in there.

Thanks and keep up the awesome work!

[vector-of-bool]

Yeah, the API will still be up-in-the-air until multi-root lands, since that can change everything about how the extension works. I'm planning to finish up multi-root for 1.2.0. I'm not sure how much longer after to get an API.

[gotschmarcel]

I would also vote for adding a public API to query compile flags. Basically something similar to the CppConfigProvider for the integration into vscode-cpp-tools. This would allow many extensions to improve their experience when using them together with CMake, because many of them have to be configured manually which is really painful.

Thanks and keep up the good work 🙂!

[MathiasMagnus]

Yes, hooking in the LaTeX extension would be nice if I build my docs with CMake.

[c-born]

I just spent a couple of days trying to work out why nothing I did would get me access to the extension API, eventually went to the source and found the TODO dating back to 13 May 2018.
Is multi-root in now? Is it's implementation stopping turning the API export back on, or is it because the API is expected to change dramatically? And given the time involved before the API is updated, how hard is it to turn on now and try for as much backwards compatibility as possible at a (much?) later date when the changes come in?

[Deerenaros]

2k20 is coming, TODO still here. v1.2.3

Are there any plans for the subject?

[Deerenaros]

Here I created PR but one failed on macOS (?) build. I have no such env to test and fail looks like something strange with startDebuging or C/C++ extension. I can't find the root of the problem.

[bobbrow]

Something changed with startDebugging in VS Code without our knowledge. I disabled the test for now. We haven't decided on when the API will be re-enabled yet, but it will be sometime after the multi-root support (in PR now) goes in.

[Deerenaros]

Thank you for reply. There is one issue i'd caught a little later: api.ts
now should be different while Kit class using here. But i defenitly do not
want to do that becouse at work we chose another way. I will happy if this
little PR would be helpfull.

Happy new year)

[bobbrow]

Thanks. I think when we do re-enable the API we'll do it similar to how we did it for cpptools. e.g. create a NPM module for it so that you can pull it in via package.json instead of copying api.ts into your extensions.

[Deerenaros]

Yeah, sounds good. Except solutions when we have no full internet access
due to company politics or technical issues. I realized that vscode cannot
socks5 at all. But anyway I can gather bundle and install them with npm
from "sources".

вт, 31 дек. 2019 г., 19:53 Bob Brown [e-mail]:

Thanks. I think when we do re-enable the API we'll do it similar to how we
did it for cpptools. e.g. create a NPM module for it so that you can pull
it in via package.json instead of copying api.ts into your extensions.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-cmake-tools/issues/494?email_source=notifications&email_token=AAL7BP6AIKN3D3FOKLPY7Y3Q3N2KJA5CNFSM4FMAOWVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH4N6GA#issuecomment-569958168,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAL7BPZKS6CSBQOJX3HGNX3Q3N2KJANCNFSM4FMAOWVA
.

[tritao]

Any update on this? Would be great to gain access to the public API.

[bobbrow]

Please add your 👍 to the first comment in the issue if this is important to you. With very limited resources available to work on this, that helps us prioritize what we work on next. Thanks!