On Tuesday 15 March 2011 12:38:52 Jeff Hill wrote:
>
> Yes, I am testing what you suggest since yesterday evening, and it works,
> but as Ralph and I were discussing its perhaps a bit awkward to not have
> the source files, and the header files, at the same level.
When you switch to Michael's new source layout the source and header files
*are* at the same level. That works because the <something>/pdq/Makefile
fragment will contain the line
SRC_DIRS += $(SOMETHING)/pdq
Thus the build system will use that path to find the .cpp files .h files while
compiling, but uses the original path to find the .h files when installing the
INC files. Sorry I didn't write that earlier, but my subconscious was aware
of it.
Please look at Michael's branch like I asked before replying any further.
- Andrew
--
An error is only a mistake if you don't learn from it.
When you learn something from it, it becomes a lesson.
- References:
- class library header file naming and install conventions Jeff Hill
- Re: class library header file naming and install conventions Andrew Johnson
- RE: class library header file naming and install conventions Jeff Hill
- Navigate by Date:
- Prev:
RE: class library header file naming and install conventions Jeff Hill
- Next:
Re: os independent interface to socket sendmsg/recvmsg Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
- Navigate by Thread:
- Prev:
RE: class library header file naming and install conventions Jeff Hill
- Next:
Re: class library header file naming and install conventions Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
|