(Created page with "<code> --enable-final</code> : Concatena todos os arquivos .cpp em um grande arquivo all_cpp.cpp, e compila de uma só vez, ao invés de compilar cada arquivo .cpp por vez. Is...")
|Line 68:||Line 68:|
: .cpp all_cpp.cpp, , .cpp . , , . , c .
a do , , .
|This section needs improvements: Please help us to
cleanup confusing sections and fix sections which contain a todo
O sistema build mudou no KDE4.
O jeito mais fácil é usar kdesdk/kapptemplate para gerar o CMakeLists.txt. Ou você pode apenas copiar um CMakeLists.txt de outro aplicativo e instalá-lo em um novo diretório acima do que estão os códigos existentes do KDE. Ou você pode iniciar da velha maneira, do zero.
Consulte o TechBase, especialmente os documentos da arquitetura. Consulte também o livro do kde.
Bem, você não é obrigado, mas é muito melhor. KPart permite uma poderosa reutilização de código. Tendo em vista o fato de que é simples usar essa tecnologia e que ela é amplamente implementada, é uma pena não usá-la se você puder.
Por favor, siga esse tutorial do CMake .
Use make -f Makefile.cvs Ele vai executar todas as etapas de geração do Makefile
Enquanto hackeia um programa pode ser útil excluir determinados diretórios da compilação que, de outra forma, seriam recompilados, mas que efetivamente não precisam ser. Também, se você fez o checkout do código que não compilou e não tem tempo ou conhecimento para corrigir os erros, você pode querer desativar a compilação do diretório tudo junto. Há dois casos. Diretório e subdiretórios. Para os diretórios você pode simplesmente apagá-los (ou não fazer checkout neles)
Se por alguma razão você não quer fazer isso, você pode também definir
DO_NOT_COMPILE="someapp" antes de chamar configure, que fará configure ignorar "someapp". Para compilar apenas poucos diretórios, ao invés de usar
DO_NOT_COMPILE para excluir a maioria deles, você pode listar em um arquivo chamado inst-apps, no nível superior, os subdiretórios de nível superior que você quer compilar.
Para desativar a compilação de qualquer diretório, inclusive subdiretórios, você tem que modificar os arquivos Makefile ou Makefile.am. Makefile.am não é recomendado porque o arquivo está no Subversion do KDE e você pode acidentalmente commitar suas alterações. Então, vamos modificar o Makefile aqui:
Abra o Makefile no diretório imediatamente acima do diretório que você deseja excluir, em um editor de texto e procure por uma variável
SUBDIRS. Ela, frequentemente, se parecerá um pouco como
SUBDIRS = share core ui . proxy taskmanager taskbar applets extensions data
Basta remover o diretório que você deseja excluir e salvar seu arquivo. Um novo make vai ignorar o diretório que você acabou de remover.
Às vezes você terá que olhar com mais atenção porque a variável SUBDIRS consiste de uma série de outras variáveis:
SUBDIRS = $(COMPILE_FIRST) $(TOPSUBDIRS) $(COMPILE_LAST)
Aqui você tem que encontrar as variáveis
COMPILE_LAST. Uma destas contém o diretório que você quer excluir. Remova o diretório de onde você encontrá-lo e salve o Makefile novamente.
Para desfazer as alterações, você pode gerar novamente o Makefile do zero ou reverter para um backup mais antigo (você fez um, não é? :-).
Para criar novamente um Makefile, basta make force-reedit.
Você também pode copiar a linha original no arquivo ao editar e fazer um comentário, prefixando um '#' na frente dele. Em seguida, desfazer a mudança é tão fácil como fazer a linha modificada com um comentário e remover o comentário na linha original.
Esta é uma boa coisa a fazer no momento do empacotamento, mas, claro, não para desenvolvedores, já que uma mudança em um arquivo significa recompilar tudo.
If you are a developer, you should definitely compile Qt and KDE with --enable-debug. You will then be able to debug your program even inside Qt and KDE function calls. If you are just a user, you can still use --enable-debug. KDE will occupy more space on your hard disk but it won't slow down your desktop. The advantage is that you get stack trace when an application crashes. If you can reproduce a crashing behaviour, go to bugs.kde.org, check that your bug doesn't exist yet and submit it. It will help us improve kde. For Qt, the compilation options are explained in qt-copy/README.qt-copy.
See --enable-final above :) . make final uses the all-in-one-file trick in the current directory even if --enable-final wasn't used, and make no-final does a normal compilation in the current directory even if --enable-final was used. Include your moc files! Header files declaring a QObject descendant have to be run through moc to produce a .moc file. This .moc file has to be compiled, for which two possibilities exists: compile it separately, or #include it in the C++ file implementing that above mentioned class. The latter is more efficient in term of compilation speed. BTW, kdesdk/scripts/includemocs does this automatically. Buy more ram, a faster machine and another processor. On a bi-PIII 866 MHz with 1GB of RAM, kde compiles at a decent speed :-)))
The strip is done at install. To use it, use "make install-strip" instead of "make install".
If you are working on an existing application, respect the author's indentation. Else, you can use whatever indentation you like.
If you do
QString translatedStuff = i18n("foobar"); translatedStuff will contain the translation of "foobar", while for
const char *markedStuff = I18N_NOOP("foobar"); markedStuff will still contain literal "foobar", but translators will know you want "foobar" translated so you can later on do
QString translatedStuff = i18n(markedStuff); and get the translation of "foobar", which wouldn't work without that I18N_NOOP.
So, normally you want to just use i18n(), but in cases where you absolutely need to pass something untranslated, but still need to translate it later or in the case that you have something to be translated before the KInstance exists, use
This often comes from the moc files not being in sync with the sources, or not linked at all. Check that you are running the right moc. 'which moc' will tell it. Regenerate your moc files (make force-reedit; make clean; make).
You need am_edit to reparse your Makefile.am to generate the correct Makefile. If it's the first Q_OBJECT you're using in this directory, you'll need to re-run Makefile.cvs or create_makefile from kdesdk/scripts. Otherwise, you can simply run "make force-reedit".
Hmm, don't do that, if some of the classes use the Q_OBJECT macro. Maybe METASOURCES=file.cpp might work for moc files though.
KDE searches its libraries in $KDEDIR/lib and in the lib directory of all the components of $KDEDIRS (note the additional 'S', this different from $KDEDIR). So, while you are still developing your library and don't want to install it, you can use this trick:
Now, KDE should find your library when using KTrader or KLibLoader.
If want to install your application privately, configure it with another prefix: for $HOME/kdeprefix, use
configure --prefix=$HOME/kdeprefix. Then let KDE know about this prefix: set KDEDIRS to $HOME/kdeprefix:$KDEDIR. To make KDE aware of new prefixes, one can also edit /etc/kderc and add
but this doesn't answer this specific question ;-) Make sure to run "kbuildsycoca" after setting the new KDEDIRS.
The mimetype database must be rebuilt when you install new services (such as applications or parts). In theory this happens by itself (kded is watching those directories), but in doubt, run "kbuildsycoca".
The best way to debug trader-related problems is to use
ktradertest: cd kdelibs/kio/tests; make ktradertest, then run
./ktradertest to see how to use it.
The solution is simple: start new apps from a command line, then they will use the new lib.
The reason is that applications started by other KDE applications (kicker, minicli, konqueror, etc.) are started via kdeinit, which loads the libs when KDE starts. So the "old" version of the libs keep being used. But if you want kdeinit to start using the new libs, simply restart it. This is done by typing kdeinit in a terminal.
This is necessary if you can't start things from the command line - e.g. for a kioslave. If you change something in kio, you need to restart kdeinit and kill the running kioslave, so that a new one is started.
Apps are often tempted to link to their part because they of course have much functionality in common. However this is wrong for the reasons below.
A lib is something you link to, a module is something you dlopen. You can't dlopen a lib ; you can't link to a module.
A lib has a version number and is installed in $libdir (e.g. $KDEDIR/lib) a module doesn't have a version number (in its name), it's more like a binary (we don't have konqueror-1.14.23 either :), and is installed into kde_moduledir (e.g. $KDEDIR/lib/kde3) (which means it's not in the search path for ld.so, so this breaks on systems without -rpath).
If you didn't understand the above, don't worry. The point is: you should NOT make your application link to your (or any other) KPart, nor any other kind of dlopened module.
Let the app dlopen the part. This is what KOffice does. However this limits the app to the very limited ReadOnlyPart/ReadWritePart API. Keep in mind that you can't call a non-virtual method whose implementation you don't link to. The solution is to define a ReadWritePart-derived class (like we have in koffice: KoDocument), with new virtual methods. Either this derived class has code (and you need a lib shared by the app and the part, see point 2 below), or an abstract interface (header file only) is enough. You can also use known interfaces to child objects of the part instead of changing the base class of the part itself - this is the solution used by e.g. KParts::BrowserExtension.
Define a common library with the common classes and let both the part and the app use it. That library can be noinst_ or lib_, both work. In the first case the compiled object code is duplicated, in the second case a real versioned lib will be installed. The idea here is that the part itself is not available to the app, but instead the part is a very thin wrapper around the same classes as the app uses. Only KParts-specific stuff remains in the part.
In KDE there are several ways to start other programs from within your application. Here is a short summary of your options with reasons why you should or should not use them.
You never want to use this unless you have a very good reason why it is impossible to use KProcess.
You want to use this if you need to start a new process which needs to be a child of your process, e.g. because you want to catch stdout/stderr or need to send it data via stdin. You should never use this to start other KDE applications unless your application is called kgdb :-)
Preferred way to launch desktop (KDE/Gnome/X) applications or KDE services. The application/service must have a .desktop file. It will make use of KDEinit for increased startup performance and lower memory usage. These benefits only apply to applications available as KDEinit loadable module (KLM)
Generic way to open documents/applications/shell commands. Uses startServiceBy.... where applicable. Offers the additional benefit of startup-notification.
KRun can start any application, from the binary or the desktop file, it will determine the mimetype of a file before running the preferred handler for it, and it can also start shell commands. This makes KRun the recommended way to run another program in KDE.
KToolInvocation::invokeBrowser launches a web browser. The difference with using the more generic KRun on the webpage URL is that KRun has to determine the mimetype of the URL first (which, for HTTP, involves starting a download to read the headers), so if you know that the URL is an HTML webpage, use invokeBrowser, it will be faster.
More details: the problem with KRun for webpages is that it delays the appearance of the browser window, and if the user's preferred browser is a non-kde application like firefox then it has to start a second download while konqueror which can reuse the kioslave started by KRun. On the other hand if the URL might be an image or anything else than html, then KRun is the right solution, so that the right application is started.
You have spotted a bug and you want to write the code to fix it. Or you want to code a specific feature. Sending a patch is very appreciated by developers. A tutorial is available but here is a description of how you should proceed:
Ok, you have done it, your code has been included in KDE. You are now fully part of the KDE project. Thanx a lot.
Never make assumptions about the geometry of the "desktop" or the arrangement of the screens. Make use of the following functions from kglobalsettings.h:
static QRect KGlobalSettings::splashScreenDesktopGeometry(); static QRect KGlobalSettings::desktopGeometry(const QPoint& point); static QRect KGlobalSettings::desktopGeometry(QWidget *w);
Use splashScreenDesktopGeometry() to determine the geometry of the desktop when you want to display an application splash screen. Use desktopGeometry() to determine the geometry of the desktop with respect to a given point on the desktop, or with respect to a given widget. Do not use the Qt class QDesktopWidget to determine these values yourself. The KDE functions take the user's settings into account, something the Qt functions cannot do.
It is ideal to try to avoid using the desktop geometry altogether. Your application will be much more standards compliant if you let the window manager place your windows for you. When this is not possible, you have the aforementioned functions available. Please beware that the geometry that is returned from these functions may not start at (0,0)! Do your math correctly!
One other caution: Both KWin and the NETWM specification have severe difficulties handling struts with Xinerama or "merged" displays. This can result in dead areas on the screen, for instance if kicker does not span a whole edge. There is not much that can be done about this, and you should try to avoid hacks to circumvent this at this time. We hope to find a proper solution for this soon.
This is almost certainly an installation problem, not a KDE code problem. A number of problems can lead to this, but most likely you have more than one version of Qt laying around and the configure script is calling a different one than KDE is using.
Another thing that may help is to rebuild and reinstall your kdewidgets.so file, which is located in the kdelibs/kdewidgets directory. Note that if you *do* have multiple versions of Qt, this may compile against the wrong one.
This problem creeps up on various mailing lists occasionally, so looking at the archives on lists.kde.org may be helpful.
Symbols defined in a C++ anonymous namespace do NOT have internal linkage. Anonymous namespaces only give an unique name for that translation unit and that is it; they don't change the linkage of the symbol at all.
Linkage isn't changed on those because the second phase of two-phase name lookup ignores functions with internal linkages. Also, entities with internal linkage cannot be used as template arguments.
Yes. Calling delete on a null pointer is a noop in C++. Having "if (ptr) delete ptr;" is redundant. Doing
ptr = 0; after a delete is a good idea, especially if the delete can be called on it from a different code path.
If you're running a 64 bits system, your libraries might have been compiled with the -DLIB_SUFFIX=64 option given to cmake. If your application wasn't compiled with that option, it'll get its modules installed into $prefix/lib/kde4, not $prefix/lib64/kde4 -- and then it will not be found. Easy solutions: a symlink to lib64 or compile your code with -DLIB_SUFFIX=64, too.