Bug 60208 - Problems adding subdir to a KDE2 project definition
Summary: Problems adding subdir to a KDE2 project definition
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 2.1.5
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-22 02:45 UTC by Ian Wadham
Modified: 2003-06-30 13:29 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Wadham 2003-06-22 02:45:25 UTC
Version:           2.1.5 (using KDE 3.1.1)
Installed from:    SuSE
Compiler:          gcc version 3.3 20030226 (prerelease) (SuSE Linux)
OS:          Linux (i686) release 2.4.20-4GB

I am using a project originally defined in KDE2, I tried to add a sub-directory (btw
there seems to be no obvious way to do this in the KDevelop menus).  Having
made a directory and added a file to the project in that directory, KDevelop
generated a Makefile.am in the directory, but Autoconf, Automake and Configure
in the Build menu failed to create a Makefile.in and Makefile.  All recursive Make
and Rebuild operations then crashed, because the new sub-dir was the first one
entered in the "depth first" recursion.  Consequently the project could not be rebuilt.

I was eventually able to work around the problem by manually editing "config.in"
and adding the path of the required Makefile near the end of "config.in".

I did not have this problem with a project created since I installed KDE3.
Comment 1 Amilcar do Carmo Lucas 2003-06-22 19:08:10 UTC
This is solved in KDevelop3 from CVS 
 
 KDevelop 2.x is no longer under development. 
 
You are strongly advised to update to the latest CVS version of KDevelop3 code 
name gideon, take a look at: 
http://www.kdevelop.org/index.html?filename=branches_compiling.html 
for all the details you need. If you find a problem or need help please send a 
mail to the mailing list: 
http://www.kdevelop.org/index.html?filename=mailinglist.html 
or drop us a line at the channel #kdevelop on the server irc.kde.org using 
ksirc, for example. 
Please use the CVS version and compile it yourself because that way you can 
easily patch it if a bug is found. 
 
KDevelop3 can import KDevelop2 projects. To do so, run the kdevprj2kdevelop 
script. 
You can have and run KDevelop3 and KDevelop2 at the same time on the same 
computer without any problems. 
So migrating is a breeze. :) 
 
Closing. Please feel free to reopen if the bug presists (for some strange 
reason) in KDevelop3 
Comment 2 Amilcar do Carmo Lucas 2003-06-30 13:29:39 UTC
Going to close it as fixed 
Comment 3 Amilcar do Carmo Lucas 2003-06-30 13:29:49 UTC
*** Bug has been marked as fixed ***.