|
| Re: References: What are they for? [message #1718266 is a reply to message #1718231] |
Mon, 21 December 2015 22:50   |
|
On 12/21/2015 02:07 PM, John Adriaan wrote:
> Hi all,
>
> I've been a C developer for 30 years (and C++ for 20) - but this is the
> first time I've used Eclipse. I know all the issues of configuring the
> compiler for INCLUDE paths, and configuring the linker for LIB dirs -
> but seriously: can't IDEs do that for you now?
>
> I created an Eclipse workspace that had a Static Library - that used the
> Archiver and everything. I then made that library a Referent for my
> Application, to ensure that it was built when I built my App. However,
> while compiling my App:
> * The Compile process still complained that it couldn't find the
> Library's Include paths;
> * The Linker still complained that it couldn't find the symbols that the
> Library had defined.
>
> If I've told Eclipse that THIS App depends on THAT Project, which
> happens to be a Static Library Project - isn't the obvious conclusion
> that you want to INCLUDE those header directories, and LINK that
> Library? Not just re-compiling the Library because it needs it?
>
> I mean: I can understand wanting fine-grained control. I can understand
> wanting to be able to say "Yeah... but no." Still: shouldn't the default
> be for the 95% of developers? Isn't it "Oh? You've REFERENCED that
> Project? Maybe it's because it's DEPENDENT on that project? And maybe it
> SHOULD be a FACTOR in that Project? So I should ADD it to the INCLUDE
> list? And ADD it to the LIBRARY list?"
>
> If someone doesn't WANT those defaults, then they're advanced enough to
> change it - after researching how. At the moment, you're requiring 95%
> of EVERYONE (including beginners - luckily not me) to research how to
> incorporate them - which is definitely NOT intuitive.
>
> Just a UX suggestion...
>
> John Adriaan
John,
Your "birds of a feather" will be the Eclipse CDT forum rather than this
newcomers' forum which is here for asking about how to install and use
Eclipse and generally less language-relevant questions than you're
asking here. Repost your question over there.
Hope this helps.
Russ
|
|
|
|
| Re: References: What are they for? [message #1718349 is a reply to message #1718329] |
Tue, 22 December 2015 17:58 |
David Vavra
Messages: 1426
Registered: October 2012 |
Senior Member |
|
|
Yeah, might be nice but think about it.
Outside of increased complexity and all that it entails, there are a number of reasons to link resources within Eclipse and code libraries are just one of them. With libraries alone, you have multiple platforms to support with multiple library name conventions in any number of different directory names. Then there's the problem of figuring out the interdependencies and order of the linked resources for builds. What should happen when a library project is added to a workspace? Calling it a library is mostly just to set the tool chain which in turn is mostly for building the makefile. Not as simple as one may think perhaps.
If you scan down the list of posts here, more than one seem to boil down to questioning why wasn't Eclipse built just for their approach. There's a point when a developer has to say "Enough, already!"
Sounds to me this is better suited as a plug-in. Any volunteers? How about you?
|
|
|
Powered by
FUDForum. Page generated in 0.02964 seconds
] 
Search
Help
Register
Login
Home
