Bug 35893 - generated link commands
Summary: generated link commands
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: kdevelop 2.x (obsolete) (show other bugs)
Version: unspecified
Platform: unspecified Other
: NOR normal
Target Milestone: ---
Assignee: KDevelop-Devel List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-07 20:33 UTC by Franco De Angelis
Modified: 2002-10-09 21:57 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 Franco De Angelis 2001-12-07 20:31:19 UTC
(*** This bug was imported into bugs.kde.org ***)

Hello

first of all I am a new user of kdevelop and I really love it. I never had 
time to learn all the automake/autoconf stuff and now I can generate 
"standard" gnu packages nearly effortless! :-) Thank you very much!

...I tried to write a simple OpenGL application in C (no qt no kde just a 
plain C OpenGL app).

The resulting package autoconfigures/compiles well under linux but when the 
packages is transferred on a SGI the autogenerated makefile attempts to link 
the wrong X11 libraries / in the wrong order and the compilation fails.

The only way I managed to succeed is to either

- modify the SGI Makefile by hand

or

-  un-check all the library checkboxes in project options -> linker options 
 and explicitly specify all the libraries in the order which is correct for 
the SGI in project options -> linker options -> additional libraries

I don't think this is the right approach - I shouldn't need know about SGI 
specific issues and also that may not work on other architectures....

If you agree this shouldn't happen I can provide you more detail


Regards
Franco De Angelis
Comment 1 Caleb Tennis 2002-10-09 21:57:58 UTC
The automake/configure combination should take care of this type of stuff for 
you, yes.  If this is still a persistent problem, try a newer version of 
KDevelop (or Gideon) and re-report this as a bug.