Bug 82154 - Linker flags inside of automake-manger for a special target are ignored
Summary: Linker flags inside of automake-manger for a special target are ignored
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: Automake (show other bugs)
Version: git master
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-25 14:05 UTC by David Ecker
Modified: 2004-07-20 13:43 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Ecker 2004-05-25 14:05:50 UTC
Version:           3.0.90-CVS (using KDE KDE 3.2.2)
Installed from:    Compiled From Sources
Compiler:          gcc-3.3.3 
OS:                Linux

Maybe I am just too stupid to enter the correct data.

I got one subproject (a elf binary) shown in my automake-manager. To include a new library for linking to this project I'll do a right click on the  name and select "Einstellungen" ("Configure" in english). I actually can enter anything into "other" of the LDFLAGS dialog or into the LDADD list. It is completly ignored and not stored in the project or any other file. After a reload of the complete project the data entered is gone. The information is not used in the linking process either.
Comment 1 Amilcar do Carmo Lucas 2004-07-19 23:17:54 UTC
Strange, it works here.
Comment 2 David Ecker 2004-07-20 08:25:27 UTC
I made a new HEAD update and compiled it this week. The problem is gone. Could such an error occure if the project file is invalid???, but otherwise the same problem persisted when creating a brand new c++ project.
Comment 3 Amilcar do Carmo Lucas 2004-07-20 11:00:40 UTC
Which project file are you refering to? *.kdevelop ?

Is the problem gone or is it still there ?
Comment 4 David Ecker 2004-07-20 12:21:32 UTC
Yes, a .kdevelop project!

The problem is gone after compiling CVS HEAD Sources this week. I just don't know if the problem was solved through new kdevelop sources or through recreating the project files 2 weeks ago. But since a new project had the same error at the time I found the problem, I haven't thought of a corrupt project file at that time.
Comment 5 Amilcar do Carmo Lucas 2004-07-20 13:43:09 UTC
Õk, it is fixed then