#tde-devs < 2022/12/23 > |
| [00:43] | micheleC has joined |
| [00:43] | micheleC: @akh thanks for the PR in tdeblis |
| [00:43] | micheleC: there will be things to fix up, Slavek will follow up with you sometimes after Christmas he said |
| [02:31] | guy has quit (Quit: Leaving) |
| [02:45] | akh: @micheleC Fantastic. Do you know of a good guide for integrating code into cmake? Either a general intro of for TDE in specific. |
| [02:47] | akh: Probably best for one of y'all to handle it for my PR but I'd like to learn how to do it myself in future. |
| [02:48] | micheleC: a good way is to look at other cmake files we used in various repo and follow through |
| [02:48] | micheleC: that is how I learned cmake mostly ;-) |
| [02:48] | akh: :^) |
| [02:52] | akh: Am I correct that the files I should be looking at are "CMakeLists.txt" (for specifying what to build) and "configure.in.in" (for feature tests)? |
| [02:53] | micheleC: CMakeLists.txt are the files for cmake. configure.in.in are for autotools |
| [02:54] | micheleC: also you can google cmake tutorial and you will easily find tons of material to learn the basic of cmake |
| [08:20] | akh: Does "git commit --amend" work with gitea? Tried using it last night and it did a regular commit |
| [08:21] | micheleC: git commit --amend will amend your last commit message |
| [08:21] | micheleC: if you then push or force pushed to a branch, it will work as ususal |
| [08:21] | micheleC: usual |
| [08:23] | akh: must have done something wrong on my end |
| [08:27] | akh: yea, i think i see what went wrong — thnx |
| [08:30] | micheleC: (y) |
| [10:02] | akh has quit (Remote host closed the connection) |
| [15:38] | micheleC has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org) |
| [20:53] | akh has joined |
#tde-devs < 2022/12/23 > |
© 2010-2026 Trinity Desktop Project