Hi Jeff,
I'm using Eclipse CDT, and I'm not sure if it doesn't have this problem, or if I didn't try the right test. I used an IOC app, typed "findThisError." on a random line in a source file, compiled, double clicked on the error message ("../drvSis3350.cpp:361: error: 'findThisError' was not declared in this scope"), and it took me to the right place.
Garth
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Hill, Jeff
Sent: Tuesday, May 14, 2013 11:38 AM
To: Tech Talk ([email protected])
Subject: RE: using the EPICS build system with an IDE
Furthermore, this simple patch to configure/RULES_BUILD appears to produce IDE compatible compiler output, which appears to be an improvement, from my perspective.
@@ -210,15 +210,15 @@
%$(OBJ): %.c
@$(RM) $@
- $(COMPILE.c) -c $<
+ $(COMPILE.c) -c $(realpath $<)
%$(OBJ): %.cc
@$(RM) $@
- $(COMPILE.cpp) -c $<
+ $(COMPILE.cpp) -c $(realpath $<)
%$(OBJ): %.cpp
@$(RM) $@
- $(COMPILE.cpp) -c $<
+ $(COMPILE.cpp) -c $(realpath $<)
> -----Original Message-----
> From: [email protected] [mailto:tech-talk-
> [email protected]] On Behalf Of Hill, Jeff
> Sent: Tuesday, May 14, 2013 12:09 PM
> To: Tech Talk ([email protected])
> Subject: using the EPICS build system with an IDE
>
> Hi All,
>
> I have noticed over the years that the EPICS build system isn't
> particularly helpful when using an IDE because it doesn't generate
> full source file paths on the compiler command line, and instead
> subdirectory dependent relative paths are used. This seems to cause
> gcc to produce also relative source file paths in its compiler
> messages which can interfere with clicking on the error message and
> vectoring the focus to the appropriate source file in the IDE. It
> seems that gcc could easily provide an option to force generation of
> full (not
> relative) source file paths in its output no matter what the format is
> of its input file paths might be, but AFAIKT, it doesn't.
>
> However, maybe this post suggests a solution that could be applied
> generically within the internals of the EPICS build system to produce
> full path names in the compilers input while continuing to navigate
> the build system with relative paths.
>
> http://gcc.gnu.org/ml/gcc-help/2008-03/msg00084.html
>
> This would result in rather more verbose build message output, but
> would improve productivity when using an IDE from my perspective. I
> suppose that we might also provide a configure option which determines
> the type of compiler file path output that gets generated depending on
> a particular user's needs, if that was important.
>
> Comments?
>
> Jeff
- Replies:
- RE: using the EPICS build system with an IDE Hill, Jeff
- References:
- using the EPICS build system with an IDE Hill, Jeff
- RE: using the EPICS build system with an IDE Hill, Jeff
- Navigate by Date:
- Prev:
RE: using the EPICS build system with an IDE Hill, Jeff
- Next:
Re: using the EPICS build system with an IDE Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: using the EPICS build system with an IDE Hill, Jeff
- Next:
RE: using the EPICS build system with an IDE Hill, Jeff
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|