| make/project issues [message #176434] |
Tue, 12 September 2006 15:25 |
Eclipse User |
|
|
|
Originally posted by: bongo.silvertine.net
Hi,
I'm using Eclipse 3.2 and CDT 3.1.0 on Linux. I'm terrible at creating my own
makefiles and autoconf doesn't seem much easier (to get started). With a
standard makefile, it's easy to specify multiple targets and an install. I can't
find how to do that with Managed Make. I see the "Create Make Target" from the
Project menu, but it's always greyed out, even with a new project. It also
doesn't occur in the project's context menu despite what the Help docs say.
Basically, I have a subdir of core code with 2 different main functions. It
would be a real pain, and seem unnecessary, to create a separate project for
each. Does anyone know a way around this?
I prefer Eclipse over an IDE like KDevelop, but KDevelop has the nice feature
that its auto build system is autoconf. The reason I'd like to eventually use
something like autoconf is for building on other platforms by simply checking
out the project from CVS and running the standard commands. I read an article on
using autoconf with Eclipse
( http://www-128.ibm.com/developerworks/eserver/library/es-uni x-eclipse/), which
requires writing an XML script. Is there any easier way to use autoconf? Can I
do anything like this with a Managed Make?
How come I can create a new project in my workspace dir tree ONLY when I select
'Use default location'? Even if I manually enter the exact same directory, just
to see what would happen, I get "Project contents cannot be inside workspace
directory". That makes absolutely no sense to me. What I really wanted to do is
put a few projects within a sub-dir of my workspace. My workspace dir is now a
dummy dir in parallel to my real workspace dir just to get around this. The
problem doesn't occur if I checkout from CVS. Hmmmm....
thanks,
Jason
|
|
|
Powered by
FUDForum. Page generated in 0.57485 seconds
Home