| Summary: | Kdevelop's default libtool support is broken | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Rick L. Vinyard, Jr. <rvinyard> |
| Component: | Build tools: Automake | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED LATER | ||
| Severity: | normal | CC: | amilcar, smparrish |
| Priority: | NOR | ||
| Version: | 3.5.4 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
I know the libtool version we use for newly created projects is really old, but kde3 is dead and thats where this libtool stuff comes from. Same goes for kdevelop3, so this won't change. I will try to came up with a patch, and do a KDevelop 3.5.5 release. But It will only have time in two weeks from now. If you post a patch, it will speed up the 3.5.5 release. PS: did you try "libtoolize -- force" ? Its actually not about the automake buildtool, the problem is inside the debugger. And the debugger doesn't know anything about libtool. It might be fixable by changing all the templates to add --mode=execute, but only if that also works on older libtool versions (i.e. 1.5 and earlier). If nobody can test that, this is a wontfix. will be looked again if someone picks up autotools support from playground. |
Version: 3.5.4 (using KDE 4.2.4) Compiler: gcc 4.4.0 libtool 2.2.6 OS: Linux Installed from: Fedora RPMs When developing libtool projects in kdevelop you need to explicitly set the debugging shell to 'libtool'. When you create a new project in kdevelop the project options will have this already set. However, the version of libtool in F11 requires that the debugging shell be set to 'libtool --mode=execute'. Therefore, debugging appears to be broken with default and older projects. A bug report has also been filed for Fedora 11 here: http://bugzilla.redhat.com/show_bug.cgi?id=507654