#trinity-desktop < 2024/03/27 > |
[00:05] | Maik has quit (Ping timeout: 260 seconds) |
[00:14] | SlavekB has joined |
[00:29] | Maik has joined |
[02:10] | Armanelgtron has quit (Ping timeout: 268 seconds) |
[02:12] | Armanelgtron has joined |
[02:27] | Armanelgtron has quit (Ping timeout: 272 seconds) |
[02:31] | Armanelgtron has joined |
[02:39] | Armanelgtron has quit (Ping timeout: 268 seconds) |
[02:42] | Armanelgtron has joined |
[02:55] | Armanelgtron has quit (Ping timeout: 268 seconds) |
[02:59] | Armanelgtron has joined |
[03:16] | Armanelgtron has quit (Ping timeout: 260 seconds) |
[03:21] | Armanelgtron has joined |
[03:26] | Armanelgtron has quit (Ping timeout: 260 seconds) |
[03:29] | Armanelgtron has joined |
[03:40] | Armanelgtron has quit (Ping timeout: 260 seconds) |
[03:43] | Armanelgtron has joined |
[04:42] | Armanelgtron has quit (Ping timeout: 268 seconds) |
[04:46] | Armanelgtron has joined |
[04:59] | Armanelgtron has quit (Ping timeout: 255 seconds) |
[05:03] | Armanelgtron has joined |
[05:05] | Guest50 has quit (Ping timeout: 250 seconds) |
[06:53] | Guest50 has joined |
[06:58] | Guest50: denk How can I check the functionality of TDE? |
[06:58] | Guest50: I rebooted the FreeBSD virtual machine. |
[06:58] | Guest50: I already have XFCE installed. The welcome screen prompts you to select only XFCE, but not TDE, |
[07:03] | Guest43 has quit (Ping timeout: 250 seconds) |
[07:33] | Guest43 has joined |
[07:54] | inverted_rabbit has left |
[08:03] | denk: did I say something about xfce? |
[08:03] | denk: xwpe is an IDE with borland-like interface |
[08:04] | inverted_rabbit has joined |
[08:04] | denk: https://www.identicalsoftware.com/xwpe/ |
[08:04] | tde-bot: Page title: Xwpe-ALPHA Project |
[08:08] | inverted_rabbit has left |
[08:15] | Guest43: denk No. |
[08:24] | denk: well, yes, I use tde under freebsd |
[08:24] | denk: #ttyvb "/usr/local/bin/xdm -nodaemon" xterm off secure |
[08:24] | denk: ttyvb "/opt/trinity/bin/tdm -nodaemon" xterm on secure |
[08:25] | denk: edit /etc/ttys |
[08:25] | denk: if you configured xorg you should see the tdm login screen |
[08:27] | denk: another way that I used some time ago is xdmcp |
[08:27] | denk: enable it in tdm configuration, then you can connect it via xorg (or xephyr) |
[09:55] | SlavekB has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org) |
[10:21] | micheleC has joined |
[10:22] | micheleC: @solemnwarning: what ideas do you have in mind on tdevelop? |
[10:23] | solemnwarning: Well for starters I figured I'd try fixing the segfault I keep hitting in the code completion... trying to get tdevelop building atm |
[10:24] | solemnwarning: Next up getting the "read includes etc from makefile" functionality working |
[10:24] | solemnwarning: Also I'd like a tree view on the side which is specifically files in the project rather than just everything that happens to be in the directory (akin to the "solution explorer" view in VS) |
[10:27] | solemnwarning: On the subject of files in the project, I'm not sure why there is a "<project>.kdevelop.filelist" which lists everything added to the project and a "blacklist" block in the "<project>.kdevelop" file with everything I _didn't_ chose to import when creating the project, feels both unnecessary and a potential information leak with the latter slurping up any random crap that was in my working |
[10:27] | solemnwarning: copy at the time |
[10:28] | solemnwarning: It seems to have initialised the project with absolute paths in places too... hoping they would all work fine as relative paths too and its just the project initialisation that needs fixing up |
[10:29] | solemnwarning: Oh right, the "compile this file" command is trying to do "make foo.o" from the top directory of the project for "foo/foo.cpp", which should obvs. either be "make foo/foo.o" or "make -C foo foo.o" depending on project structure |
[10:30] | solemnwarning: I'm gonna stop going on about what doesn't work in tdevelop for now :v |
[10:30] | solemnwarning: ...except for the CMake stuff. Maybe I should just try using autotools instead. |
[10:31] | micheleC: ok, that is quite a list. |
[10:31] | micheleC: if you are going to look into the code, we will be happy to support you on questions that you may have |
[10:32] | solemnwarning: Yeah... a lot of it is bug fixes and I wouldn't expect it to be contentious if I started fixing them, but I'm concious of the fact my baseline for a "good(ish) IDE" is Visual Studio, so I just wanted to check I wasn't going to step on any toes if I started adding VS-like UI features or even tweaking existing ones to be more like it |
[10:33] | micheleC: re autotools/cmake, I suggest you focus more on the second since more and more code is using cmake. TDE as well is building most packages with cmake and it is a matter of time before no more autotools |
[10:33] | micheleC: development is welcomed, so feel free to go ahead. |
[10:34] | solemnwarning: I couldn't get cmake to pick up on bdb on my machine for some reason... although commenting out those checks got me past that :v |
[10:34] | micheleC: I use neovim, far superior to even VS Studio IMO |
[10:34] | solemnwarning: I've got as far as `cmake --build` now, although its trying to execute a C header... |
[10:35] | solemnwarning: e.g: |
[10:35] | solemnwarning: [6/1337] cd /mnt/fastscratch/tdevelop/build/lib/interfaces && /mnt/fastscratch/tdevelop/lib/interfaces/KDevCoreIface.h > /mnt/fastscratch/tdevelop/build/lib/interfaces/KDevCoreIface.kidl |
[10:35] | solemnwarning: FAILED: lib/interfaces/KDevCoreIface.kidl /mnt/fastscratch/tdevelop/build/lib/interfaces/KDevCoreIface.kidl |
[10:35] | micheleC: which distro/Os are you on? |
[10:36] | solemnwarning: Debian |
[10:36] | solemnwarning: I'm using the prebuilt packages of everything TDE, I'm hoping I don't have to compile the whole project to build tdevelop? |
[10:36] | micheleC: there shouldn't be any issue then, as long as you use the tde-packaging files for it. Slavek and I are on Debian too |
[10:36] | solemnwarning: I'm using (mostly) the steps from here: https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules#Performing_a_cmake_Build_with_Ninja |
[10:37] | solemnwarning: Although I set the PREFIX to /opt/trinity-dev (and fixed up TQTDIR etc to point to /opt/trinity instead) |
[10:37] | micheleC: that is probably old/outdated. Have a look at this scripts: https://mirror.git.trinitydesktop.org/gitea/TDE/tde-packaging/src/branch/master/debian/_buildscripts/local |
[10:37] | micheleC: building will be much easier |
[10:38] | micheleC: if you follow the README you should be able to build TDE with ease, since all the packaging files and configuration is already there and well maintained |
[10:45] | solemnwarning: Hmm... if possible I'd like to be able to just build-debug-build-etc on tdevelop, not build and install the entirety of tde... |
[10:45] | solemnwarning: (I already have tde installed - I mean I'd rather keep the stable packages untouched) |
[10:47] | solemnwarning: That said I'm getting some build errors centered around TQ_SIGNAL and TQ_SLOT macros, and GCC suggesting "did you mean TQT_SIGNAL" etc... I'm guessing thats an API thats been renamed in the TDE libs since the last release? |
[10:49] | solemnwarning: Git history says yes |
[10:50] | solemnwarning: Is developing a single tde component on top of not-the-git-head of the rest of tde likely to be painful? |
[11:11] | SlavekB has joined |
[11:42] | Maik has quit (Ping timeout: 256 seconds) |
[11:42] | Droid has joined |
[11:42] | SlavekB has quit (Excess Flood) |
[11:46] | SlavekB has joined |
[11:52] | Guest50 has quit (Quit: Client closed) |
[11:57] | micheleC: > if possible I'd like to be able to just build-debug-build-etc on tdevelop |
[11:57] | micheleC: in that case just make sure you get the tde-packaging files, so you can later do a local build. Those will make sure you have the right settings |
[11:59] | micheleC: > TQ_SIGNAL and TQ_SLOT macros, and GCC suggesting "did you mean TQT_SIGNAL" |
[11:59] | micheleC: you can't build current "master" or "r14.1.x" on stable builds. There has been a lot of renaming since R14.1.1, so you will get into errors like that. If you want to build from latest commits on "master" you need to use PTB packages. And if you want to build from "r14.1.x", you need PSB |
[12:00] | micheleC: > developing a single tde component on top of not-the-git-head of the rest of tde likely to be painful |
[12:00] | micheleC: that shouldn't be a problem, but you may have problems when you want to rebase on top of latest commit, which is a requirement for getting the code in TDE officially |
[12:00] | solemnwarning: I'll probably set up a chroot later and try building the whole tde tree in there to simplify things |
[12:01] | solemnwarning: How much disk space (roughly) am I looking at for building the whole tree? |
[12:02] | micheleC: that is exactly what those scripts I pointed to will do for you. You can also use them to build locally, which is quicker. I usually use "-g -po" options to setup a local build folder, then do development there with "debian/rules binary" (first time) and then "ninja <target>" on subsequent builds. This is much quicker |
[12:02] | micheleC: > How much disk space (roughly) am I looking at for building the whole tree? |
[12:02] | micheleC: 25gb would be good. Even less if you don't use worktrees and multiple branches |
[12:02] | solemnwarning: ty |
[12:03] | micheleC: my git tree is 13.5GB, and I use worktree and have both master and r14.1.x fully checked out |
[12:03] | micheleC: then of course you need disk space for building and for storing the .deb packages |
[12:15] | Armanelgtron has quit (Ping timeout: 256 seconds) |
[12:20] | Armanelgtron has joined |
[12:23] | SlavekB has quit (Excess Flood) |
[12:23] | SlavekB has joined |
[12:24] | micheleC has left (Kopete 0.12.7 : http://trinitydesktop.org) |
[12:53] | micheleC has joined |
[12:53] | micheleC has left (Kopete 0.12.7 : http://trinitydesktop.org) |
[13:31] | Guest43 has quit (Ping timeout: 250 seconds) |
[13:41] | Guest43 has joined |
[13:58] | Guest43 has quit (Quit: Client closed) |
[13:58] | Guest43 has joined |
[14:09] | solemnwarning: Working through the debian build steps I got as far as building edeps/transcode, which fails on a missing dependency: builddeps:/build/transcode_1.1.7-10~0ubuntu20.10.0+4.dsc : Depends: libavresample-dev (>= 6.9) but it is not installable |
[14:42] | Guest50 has joined |
[14:54] | inverted_rabbit has joined |
[18:22] | Guest43 has quit (Quit: Client closed) |
[18:48] | SlavekB has quit (Quit: TDE Kopete : https://trinitydesktop.org) |
[19:13] | Guest50 has quit (Ping timeout: 250 seconds) |
[20:53] | Armanelgtron has quit (Ping timeout: 268 seconds) |
[20:58] | Armanelgtron has joined |
[21:25] | Armanelgtron has quit (Ping timeout: 260 seconds) |
[21:29] | Armanelgtron has joined |
[22:40] | SlavekB has joined |
[23:42] | micheleC has joined |
[23:47] | micheleC: @solemnwarning: transcode is required only on some older debian. Depending on your version, you cak safely skip it. Bookworm, trixie don't need it and it will FTBFS as you have experienced. |
#trinity-desktop < 2024/03/27 > |