Bug 56450

Summary:	g++ 3.2 does not link with a project due to missing libraries from subdirectories
Product:	[Applications] kdevelop	Reporter:	Alex Harford <alex>
Component:	Build tools: Automake	Assignee:	KDevelop Developers <kdevelop-devel>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version:	2.1.4
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Alex Harford 2003-03-26 21:12:50 UTC

Version:           2.1.4 (using KDE KDE 3.1)
Installed from:    Slackware Packages
Compiler:          g++ 3.2 
OS:          Linux

I have sent a KDevelop program to a friend who is trying to compile on his RedHat 8.0 system with g++ 3.2

I am using g++ 2.95.

Everything links fine on my computer but the libraries created in subdirectories do not link because it is not enough to include just the libBlah.a file for g++ 3.2.  It also needs to have the '-lBlah -LBlahdirectory' options added.

The workaround I have used it to take the line from the Makefile.am and add it manually:

buffy_LDFLAGS = $(all_libraries) -lCollision -LCollision -lCharacter -LCharacter

This workaround still works on my g++ 2.95 system.

Comment 1 Caleb Tennis 2003-03-26 22:11:56 UTC

*** Bug 56452 has been marked as a duplicate of this bug. ***

Comment 2 Amilcar do Carmo Lucas 2003-08-25 18:49:01 UTC

Sorry, KDevelop 2.x is no longer under development. 
 
The bug has been fixed in KDevelop3. 
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 open Develop2 projects. To do so, goto the "Project -> Open 
Project ... " and select 
"KDevelop 2 Project Files" in the "Filter:". 
You can have and run KDevelop3 and KDevelop2 at the same time on the same 
computer without any problems. 
So migrating is a breeze. :) 
 
Anyway, thanks for reporting the bug. I'm closing it but please feel free to 
reopen it if for some strange 
reason the bug presists in KDevelop3 
 
P.S. : The KDevelop team closed over 337 reported and confirmed bugs since the 
release of the last KDevelop2.x