tde-devs@chat.jabb.im < 2021/12/02 > |
|---|
| [00:42] | michelec2 has joined |
| [01:42] | michelec2 has left |
| [01:43] | michelec2 has joined |
| [03:16] | michelec2 has left |
| [07:47] | blu.256 has left |
| [08:34] | cethyel has joined |
| [08:53] | cethyel: might be wrong, but I believe the Python modules provided with sip4-tqt, python-tqt and python-trinity aren't important since they are just intern cooking to set/get data for python-tqt and python-trinity to build (build time only). cmake-trinity should have a routine to use the sip executable on the modules which holds sip files (python-tqt and python-trinity). Sipgen (create the sip executable) and siplib (create the binding) in sip4-tqt, those are C code, no need for Python here. |
| [09:02] | cethyel: unfortunately I never got the hand on sip use, I don't get how the Python scripts process the sip files to creates *.cpp files. Once those *.cpp files have been created, cmake can take over as usual |
| [09:06] | cethyel: to sum this up, sip4-tqt can be converted to cmake without Python need, cmake does the job, we just have to be careful where the libsip is put, choosing Its final name and the name of the executable. |
| [09:09] | cethyel: python-tqt and python-trinity need a sip routine included in the cmake-trinity module, then cmake can take over. |
| [09:34] | cethyel: I'd say something else, once the *.cpp files have been created, those files can be integral part of their respective modules...as long as no one change anything in the sip files. If someone were to add/remove code in a sip file, then the process to create a new cpp can be triggered by the person who adjusted that sip file. On the packaging side, this should shortcut the processing of those cpp files. Since there hasn't been any changes on those sip files for years, I don't see the need the create cpp files again, again and again.... |
| [09:43] | blu.256 has joined |
| [11:17] | Slávek: SIP is not just a sipgen and a library, but it is also a python module used at runtime. |
| [11:20] | Slávek: You can see that this Python module is loaded at runtime with each individual part generated by sipgen:
https://mirror.git.trinitydesktop.org/gitea/TDE/sip4-tqt/src/branch/master/sipgen/gencode.c#L2242 |
| [11:23] | blu.256 has left |
| [11:38] | cethyel: I think I stand correct since none of the examples in python-tqt and python-trinity import sip as a module. To me the libsip is called as a module for the sip executable then It's role is over. |
| [11:41] | Slávek: PyImport_ImportModule("sip") is equivalent to "import sip" in python scripts => this imports the python module for runtime. |
| [11:48] | cethyel: I never said you're wrong, there's definitely a connection between qtui.so and sip.so. I said the Python modules in sip4-tqt (aka those with a .py extension) should not be needed at run time. But anyhow since I'm not going to make a macro in cmake-trinity to use sip this debate is mostly fruitless. I've already turned the page in the Python stuff. |
| [11:49] | cethyel: t ome the Python stuff is over |
| [11:53] | Slávek: When "from python_tqt import qtui" is used in the python script, the python module "qtui.so" automatically makes import python sip module => therefore, python sip module is used at runtime. |
| [12:04] | cethyel: I do get that, It is the binding. Did I say we could get rid of It, never!. I said for the cmake conversion we can remove the Python modules with .py extension |
| [12:19] | cethyel: https://mirror.git.trinitydesktop.org/gitea/TDE/tdeedu/pulls/15 |
| [12:19] | tde-bot: Page title: #15 - fix FTBFS when aRts support is not available from tdelibs. - tdeedu - TDE Gitea Workspace |
| [12:20] | cethyel: please give this try when you've got time, I'm not sure where you put these headers in Debian |
| [12:25] | cethyel has left |
| [13:36] | michelec2 has joined |
| [13:39] | michelec2: @tdeedu: will test tomorrow and let you know |
| [13:41] | michelec2: @python: the bindings are modules for calling C++ functions from python code. I haven't really checked how it works behind the scenes, but I think the idea of using some cmake routing to help the process could be good |
| [13:43] | michelec2: regarding adding the cpp files to the module, I think generating files all the times minimize the risk of having old code. In fact, we should take this a step further and see how to generate updated sip files from the actual tqt3 files, so everything is up to date all the times :-) |
| [13:44] | michelec2: *(two comments above) using cmake routines |
| [15:19] | blu.256 has joined |
| [15:44] | michelec2 has left |
tde-devs@chat.jabb.im < 2021/12/02 > |
|---|
