KDevelop4/Manual/Sessioner og projekter
Sessioner og projekter: KDevelops grundlag
I dette afsnit vil vi gennemgå noget af terminologien, som KDevelop bruger til at beskrive verden og strukturere sit arbejde. I særdeleshed vil vi introducere begreberne sessioner og projekter og forklare, hvordan du kan opsætte de projekter, som du vil arbejde på i KDevelop.
Terminologi
KDevelop bruger begreberne sessioner og projekter. En session indeholder alle de projekter, som har noget med hinanden at gøre. I de eksempler, der følger antager vi, at du både udvikler et bibliotek og et program, som bruger det. Du kan tænke på en centralt KDE-bibliotek som det første og KDevelop som det andet. Et andet eksempel kunne være en Linux-kerneudvkler, som også arbejder på en enhedsdriver til Linux, som ikke er indføjet i selve kernen endnu.
Tager vi det sidste som eksempel, så ville du have en session i KDevelop, som har to projekter: Linux-kernen og enhedsdriveren. Du vil nok samle dem i en enkelt session (i stedet for at have to sessioner med et projekt i hver), fordi det vil være nyttigt at kunne se kernefunktioner og -datastrukturer i KDevelop, når du skriver kildekode til driveren — så kan du for eksempel få navne på kernefunktioner og -variable automatisk fuldført, og du kan se dokumentation for kernefunktioner mens du arbejder med driveren.
Now imagine you also happen to be a KDE developer. Then you would have a second session that contains KDE as a project. You could in principle have just one session for all of this, but there is no real reason for this: in your KDE work, you don't need to access kernel or device driver functions; and you don't want KDE class names autoexpanded while working working on the Linux kernel. Finally, building some of the KDE libraries is independent of re-compiling the Linux kernel (whereas whenever you compile the device driver it would also be good to re-compile the Linux kernel if some of the kernel header files have changed).
Finally, another use for sessions is if you work both on the current development version of a project, as well as on a branch: in that case, you don't want KDevelop to confuse classes that belong to mainline and the branch, so you'd have two sessions, with the same set of projects but from different directories (corresponding to different development branches).
Setting up a session and importing an existing project
Let's stick with the Linux kernel and device driver example — you may want to substitute your own set of libraries or projects for these two examples. To create a new session that contains these two projects go to the
menu at the top left (or, if this is the first time you use KDevelop: simply use the default session you get on first use, which is empty). Next, go to the menu to create the Linux kernel as a project inside this session. To do this, follow these steps:- Go to to import a project
- You then have multiple options to start a new project in the current session, depending on where the source files should come from: You can just point KDevelop at an existing directory, or you can ask KDevelop to get the sources from a repository. Let's look at these options in turns:
- If you want to work with a project that's already on your hard drive then just select as source and choose the as the directory in which your project resides. This could be a directory into which you unpackaged a tar file that you downloaded, or it could be a directory into which you checked out a version of the project using a version control system (e.g. git or subversion).
- Alternatively, assuming you wanted to work with the current development sources of deal.II and don't already have a version checked out:
- In the dialog box, under , choose to use , , or one of the other choices
- Choose a working directory as destination into which the sources should be checked out
- Choose an URL for the location of the repository where the source files can be obtained
- Hit
du -sk /path/to/KDevelop/project
to see how much data has already been downloaded.NoteThe problem with the progress bar has been reported as KDevelop bug 256832.NoteIn this process, I also get the error message You need to specify a valid location for the project which can be safely ignored. . This can take quite a long while; depending on the speed of your connection and the size of the project. Unfortunately, in KDevelop 4.2.x the progress bar does not actually show anything, but you can track progress by periodically looking at the output of the command line command
- It asks you to select a KDevelop project file in this directory. Since you probably don't have one yet, simply hit
- Hit again
- KDevelop will then ask you to choose a project manager. If this project uses standard Unix make files, choose the custom makefile project manager
- KDevelop will then start to parse the entire project. Again, it will take quite a while to go through all files and index classes etc. At the bottom right of the main window, there is a progress bar that shows how long this process has come along. (If you have several processor cores, you can accelerate this process by going to the menu item, then selecting on the left, and increasing the number of threads for background parsing on the right.)
Setting up an application as a second project
The next thing you want to do is set up other projects in the same session. In the example above, you would want to add the device driver as the second project, which you can do using exactly the same steps.
If you have multiple applications or libraries, simply repeat the steps to add more and more projects to your session.
Creating projects from scratch
There is of course also the possibility that you want to start a new project from scratch. This can be done using the
menu item. The details of what options this offers to you are described elsewhere in this manual.