Hello,

I'm quite determined to code for KDE (I'm very good at C++, ok at Qt, and a one year-long KDE user), yet I'm experiencing an issue that's a bit strange...

Here's the background:
Yesterday, I downloaded kdebase, kdelibs, kdepimlibs and kdepim from the anonymous SVN trunk. I got them in a folder named

Code: Select all

/home/me/RSPDT/Source/KDE

After that, I created a virtual machine using VirtualBox, on which I installed Fedora 13. I shared the KDE Source folder with the virtual machine, mounting it into

Code: Select all

/home/virtual_me/Source/KDE

The problem appears when, while in the virtual machine, I open KDevelop 4 and try to import the CMakeLists.txt of a project, say

Code: Select all

/home/virtual_me/Source/KDE/kdepim/kontact/CMakeLists.txt

When I import this file, KDevelop goes through the 2 steps of the import wizard, and when I click finish, it complains it can't load the project file named

Code: Select all

"/home/virtual_me/Source/KDE/kdepim/kontact/kontact.kdev4"

BUT, if I copy the kontact folder somewhere inside the virtual_me home folder (like the Desktop), KDevelop has no problems in importing CMakeLists.txt, and it creates a kontact.kdev4 file.

The shared folder is mounted using "uid=virtual_me,gid=virtual_me" in fstab, so I have read-write permissions from within the virtual machine.

Does KDevelop require some filesystem features that the VirtualBox sharing engine does not provide? Or it should have been completely transparent... Is there any way I can be more sure that the permissions are set right?

Cheers!

Update:
I just noticed that if I manually create (from within the virtual machine) a blank "kontact.kdev4" file in the project's folder, KDevelop4 will import the project correctly. It's clearly a permission issue.

The workaround is ok, but what happened?

Unfortunately I don't know what caused this, however are you able to make files executable on the "virtual folder"?

Well, I have some things to fix before I can build something successfully. I'll walk through the tutorial on the KDE website regarding "Building KDE", and hopefully I'll be able to build from sources, without KDevelop4. After that, I'll try to make things work with KDevelop too.

I've just run into the same problem with a sshfs mount (from a virtualbox VM). I guess the problem is with the mounted directories?

Anyway, creating an empty .kdev4 file did the trick.

It was a php project, and all files got indexed right.

Miguel

KDevelop4 support is not meant to work over KIO, but it should work fine if loaded from a mounted FS.

If you get any error, please describe it in http://bugs.kde.org so that we can look into it.