tde-devs@chat.jabb.im < 2021/11/30 >
[01:14]michelec2 has joined
[07:12]michelec2 has left
[08:31]cethyel has joined
[08:45]cethyel: @Python stuff, I have remove everything not out of considerations but because I knew I can't complete It, I don't know Python beyond the few hours reading about It. python-tqt and python-trinity aren't independent builds, everything is tied to sip4-tqt and I don't want to change anything in It. Looking at 3 modules at the same time (with theirs cmake conv counterparts ) is too much complexity. I don't want to bother myself with that.
[09:36]Slávek has left
[09:37]Slávek has joined
[09:55]cethyel has left
[14:38]michelec2 has joined
[14:38]michelec2: Hi Greg
[14:39]michelec2: no prob. we can focus on cmake conversion first. we can look at renaming later.
[14:40]Slávek: For the pythom modules there will be the first complex step to determine how to integrate cmake building with the principle of building python modules :(
[14:43]Slávek: https://martinopilia.com/posts/2018/09/15/building-python-extension.html#building-with-cmake
[14:43]tde-bot: Page title: Building a Python C extension module with CMake
[14:45]Slávek: In this moment I do not know whether it will be sufficient to use cmake building or whether the cmake building must be integrated into the python way of building modules.
[14:46]michelec2: that's another good point
[14:46]michelec2: didn't think of that
[15:35]michelec2 has left

tde-devs@chat.jabb.im < 2021/11/30 >