packaging

[arturbac]

@ follow up https://www.reddit.com/r/cpp/comments/1bazg7i/comment/kuigok7/?context=3

[arturbac]

"If having a kate plugin working in kdevelop is easy then that's great. But if not, their opinion might be helpful for you to decide what approach to take "
I will make conditional compilation of 2 plugins one for kdevelop one for kate, with some conditionaly build changes for both plugins in one class code, It should be simple

[arturbac]

I managed to share as static lib plugin code already for both Kate and Kdevelop, I need 2-3 days to polish kate plugin, refactor kdevelop ConfigPage to shared for both and only sub classed for kdevelop as kdevelop ConfigPage uses ktexteditor ConfigPage as base class

[arturbac]

Are You not familiar with cmake presets and workflows ?
Aproach with manual cmake configuration and building by hand is a very deprecated approach, should be avoided

git clone https://github.com/arturbac/kdevcxx_with_ai.git
# cd to top level source directory
cd kdevcxx_with_ai 
cmake --workflow --preset="clang-release"
ls -1 build/clang-release/bin/
kdevcxx_with_ai.so*

I You really need to split into 2 phases and do this manually

cmake --preset="clang-release"
cmake --build --preset="clang-release" --target kdevcxx_with_ai

[arturbac]

@Petross404 Kate plugin is implemented too, soon after making documentation will make release