Version: 4.0.1 (using KDE 1.2) OS: Linux I try to import my project regular GNU Makefile into Kdevelop 4 and get an error message that Kdevelop 4 is unable to open project file xxx.kdev4. The whole point here is to CREATE the project file. I was using this method with no problem with Kdevelop 3.5.5. Why would you put out a new version that is a REGRESSION from the older version ??? Reproducible: Didn't try
Refrain from statements such as your last sentence in future bug reports, this does not help anyone. Attach your Makefile so we can actually try to reproduce and fix your bug. Also explain *in detailed steps* what you are doing and when it is failing.
Created attachment 52668 [details] Makefile trying to use with Kdevelop4. Worked with Kdevelop3
I open Kdevelop4 and then choose Project-> Open/Import Project. The filter list does include Makefile. I navigate to the folder containing the Makefile and then choose that file. I then choose the Next button. I leave the name as utils and Build System as Custom Makefile Project Manager. I then choose Finish and get the error popup: Unable to load the project file path/utils/utils.kdev4. I looked for additional information on the Kdevelop website and search Google but did not find anything pertinent to my issue. I then considered just create a New project but the only choice is New from Template. The only templates are for Qt and No GUI Cmake. I looked for additional templates put did not find any on the Kdevelop website.
Comment on attachment 52668 [details] Makefile trying to use with Kdevelop4. Worked with Kdevelop3 Will replace with more generic example
Created attachment 52669 [details] I want to submit a more generic example for the Makefile
I didn't really want to give the Makefile I sent out the world, but don't know how to delete the attachment. I guess it is meaningless to most people though. If there is a way to delete this file, then please do so and I will come up with a more generic example.
The content of attachment 52668 [details] has been deleted by Matt Rogers <mattr@kde.org> who provided the following reason: user requested deletion due to privacy concerns The token used to delete this attachment was generated at 2010-10-25 14:49:19.
Sorry it took so long for me to get back to this. I am still having the same problem in importing a very simple GNU Makefile into Kdevelop4. It could be that I have an installation problem or that my Makefile doesn't conform to the type needed by Kdevelop4. I will attach a very simple Makefile as an example. When I try to Import the Makefile to create a new project I get an error from Kdevelop4 that it is unable to open the project file xxx.kdev4. I was under the impression that the import would create the kdev4 file. Please let me know if there is something I am missing. My installation is under Fedora 13 Linux. Tnanks.
Created attachment 57530 [details] Simple Makefile for a "Hello World" program Let me know if you need more info or if the method I am using is in error. Thanks.
Well, I believe I have identified the issue. The directory that I have been using for my projects is actually an NFS mount to files on a different computer. Also, I am running Fedora 13 in a Virtual Machine so in this case the mount is actually using the VMWare hgfs mount. Apparently there is an issue with Kdevelop4 being able to resolve the directory structure under the mount point. I copied the example that I had just include to the home directory (not a mount point) and was Kdevelop4 was then able to create the project from the Makefile. I also did the same with a much more complex actual project and Kdevelop4 was also able to create the project. This does seem then to be a much more obscure issue than I original thought. It would still be nice to be able to perform the project create with the mounted directory as I was able to do this with Kdevelop3.
Note that once I created the kdev4 file which just consists of the three lines: [PROJECT] Manger=KDevCustomMakeManager Name=src I copied this file into the project that was under the mount point I was then able to open the project under the mount point and build the project.
sounds valid, but there might actually be a report about this one already somewhere...
Git commit 4406fd80028b95eb6712560beba8d5c7f6ff4129 by Olivier JG. Committed on 20/08/2011 at 03:52. Pushed by olivierjg into branch 'master'. Close Project config tmp file before attempting to upload it. CCBUG: 254519 M +1 -0 shell/projectcontroller.cpp http://commits.kde.org/kdevplatform/4406fd80028b95eb6712560beba8d5c7f6ff4129
Can someone who has run into this bug, or anyone who has an NFS mount try again to import a project without an existing kdev4 file? I think this should be fixed in master.
Seeing this on a fuse mount in KDevelop Version 4.2.2 Using KDE Development Platform 4.6.5 (4.6.5). What's the earliest version this fix may be in?
j_n: the fix will probably be only in the upcoming 4.3 release, which will take some time still. so if possible try a nightly package, or compile kdev from sources - it's not that hard.
just tested this, I could open a nfs dir as a new project like expected. closing as fixed.