| How to make Code Assist work? [message #109914] |
Thu, 08 July 2004 18:07  |
Eclipse User |
|
|
|
Originally posted by: publicNO.SPAMoverbored.net
Hi, I'm new to Eclipse and I'm working in a new environment with which
I'm unfamiliar (it's Windows). I do know that we use Microsoft's
nmake.exe, and there exist either DIRS or sources files in every
directory (there are also makefiles alongside sources files, but they
consist only of "!INCLUDE $(MAKEFILE_DEF)"). The sources files look like:
>>>
#
# dummy sources file
#
USE_PCH=1 # we use pre-compiled headers
!INCLUDE $(BLAH)\lala\something.mk
TARGETNAME=MyLib
TARGETTYPE=LIBRARY
SOURCES=\
blah1.cxx\
blah2.cxx\
INCLUDES=\
$(BLAH)\blah;\
$(INCLUDES);\
>>>
What I'm wondering right now is how to make Eclipse be able to understand
my environment, because Content Assist doesn't seem to be working (when I
use . or ->, nothing comes up, even after setting the delay to 0). Does
CDT recognize such an environment? (For example, when I use #includes, it
should know which directories to look in from the INCLUDE variable
defined in the sources file.) If not, is it possible to make it
understand it? I think at this point all I'd really like is Content
Assist and the ability to (intelligently) find where things are defined,
not building or debugging.
Thanks in advance!
|
|
|
| Re: How to make Code Assist work? [message #110070 is a reply to message #109914] |
Fri, 09 July 2004 13:17  |
| Eclipse User |
|
|
|
Originally posted by: publicNO.SPAMoverbored.net
How do I make Eclipse understand the sources and DIRS files as makefiles?
OvErboRed <publicNO@SPAMoverbored.net> wrote in
news:Xns952099FCAFE03yangstaoverbored@204.138.98.10:
> Hi, I'm new to Eclipse and I'm working in a new environment with which
> I'm unfamiliar (it's Windows). I do know that we use Microsoft's
> nmake.exe, and there exist either DIRS or sources files in every
> directory (there are also makefiles alongside sources files, but they
> consist only of "!INCLUDE $(MAKEFILE_DEF)"). The sources files look
> like:
>
>>>>
>
> #
> # dummy sources file
> #
>
> USE_PCH=1 # we use pre-compiled headers
> !INCLUDE $(BLAH)\lala\something.mk
>
> TARGETNAME=MyLib
> TARGETTYPE=LIBRARY
>
> SOURCES=\
> blah1.cxx\
> blah2.cxx\
>
> INCLUDES=\
> $(BLAH)\blah;\
> $(INCLUDES);\
>
>>>>
>
> What I'm wondering right now is how to make Eclipse be able to
> understand my environment, because Content Assist doesn't seem to be
> working (when I use . or ->, nothing comes up, even after setting the
> delay to 0). Does CDT recognize such an environment? (For example,
> when I use #includes, it should know which directories to look in from
> the INCLUDE variable defined in the sources file.) If not, is it
> possible to make it understand it? I think at this point all I'd
> really like is Content Assist and the ability to (intelligently) find
> where things are defined, not building or debugging.
>
> Thanks in advance!
|
|
|
Powered by
FUDForum. Page generated in 0.06783 seconds
Home