Conversion to the cmake building system. #2
Merged
SlavekB
merged 4 commits from feat/cmakeConv
into master
4 years ago
Loading…
Reference in new issue
There is no content yet.
Delete Branch 'feat/cmakeConv'
Deleting a branch is permanent. It CANNOT be undone. Continue?
@SlavekB , @MicheleC
I get stuck with this error:
that kind of error usually is solved with adding an header to an ui file, but I've got no idea where/which header is providing the class ConfigDialog.
Any help is welcome. 😅
Solved, thanks to Slavek.
Something's fussy with "KDE_XSL_STYLESHEET"
Solved, thanks to Slavek.
The problem with ConfigDialog was caused by the fact that
config.h
is generated from the fileconfig.ui
and then there is confusion betweenconfig.h
in the global folder andconfig.h
in the folderstarter
. Therefore, I renamed the file toconfigdialog.ui
.You can also see several additions there to ensure AUTOMOC. And adding
${X11_XTEST_LIBRARIES}
for the starter.For FTBFS due to
pth
, this was a common problem with using automatic ascii cast.A mystery was
MacStyle
for a while before I found out that it is defined at the TQt level, but only if TQT_NO_COMPAT is not used.Rem, have a look on this:
and that one:
Things to note:
It seems that the automake build does not process the translation stuff (translations folder).
The kickermenu folder is not precessed either, I believe this code is intended to work with KDE3 < 3.1 ; if so, during the cleanup this folder might go and the kickermenu-3.3 folder might be renamed.
According to Michele, this is quite the opposite, as a result cmake is processsing the kickermenu folder.
In addition, there is a tarball (svgs.tar.bz2) in the icons folder with two "paw" images /icons, I don't think we need them.
IMO, it would be more appropriate if baghirarc and qtrc where under the usual tde apps locations, instead of ~/.qt/
WIP:Conversion to the cmake building system.to Conversion to the cmake building system. 4 years ago...
Had a quick look. For what I see, kickermenu-3.3 was used until KDE 3.3, then from KDE3.4 kickermenu was used.
So of the two, kickermenu-3.3 is the one that could go, not kickermenu.
https://mirror.git.trinitydesktop.org/gitea/TDE/tde-style-baghira/src/branch/master/Makefile.am#L2
still some trouble with symbols visibility (i guess), i get this error when running "bab" from console:
I assume this couldn't work in the previous automake build either, because the function name was changed during the KDE => TDE conversion.
As we discussed it, I renamed the catalogs for translations. Because the translations were not installed at all in automake, I also changed the layout of the translation directory. Catalogs and translations from the original location will be removed in the commit following the merge so that there is time to change the settings in TWTW.
I suggest merging this PR and location changes related to configuration files will be made as a separate PR. What is your opinion?
Sounds like a good idea 👍
2aac2fdcff
into master 4 years agoGuys, if we are to change the location for the ~/.qt/qtrc file here: https://mirror.git.trinitydesktop.org/gitea/TDE/tde-style-baghira/src/branch/master/style/polish.cpp#L75
I believe that It also should be changed in tqt3 in here:
https://mirror.git.trinitydesktop.org/gitea/TDE/tqt3/src/branch/master/src/tools/qsettings.cpp#L478
The ~/.qt/ folder is used in many places in the code.
Changing it to something else (~/.tqt/) is a good idea but it needs to be coordinated across the complete code. It also needs an update procedure to migrate the files to the new location. So something to do in a minor release (R14.x.0) rather than a maintenance release (R14.0.x).
I agree with all of those assessments, I'll register an issue in tqt3 as a reminder/wish.
2aac2fdcff
.