Hi Martin,
On Oct 22, 2014, at 8:26 PM, Konrad, Martin <[email protected]> wrote:
> how can I enforce a certain build order in the top-level Makefile of an
> IOC? I need it to be
>
> 1. subdirectory *App (also builds a data conversion tool)
> 2. convert a data file in the $(TOP) directory (using the data
> conversion tool)
> 3. subdirectory doc (uses the converted data file to generate a plot)
>
> See the attached file for my Makefile as it is now. The behavior I see
> now is 1 -> 3 -> 2.
Why do you have to run the conversion tool from the top level Makefile? I would personally try to avoid mixing up rules from different build areas, so would either add a new directory to run the tool in, run it in the directory it was built in, or in the docs directory.
If you add a new directory, use xxx_DEPEND_DIRS variables to set dependencies between directories. For example, if bApp needs aApp to have been built first, you would set bApp_DEPEND_DIRS = aApp.
HTH,
- Andrew
- References:
- order of rules in Makefile Konrad, Martin
- Navigate by Date:
- Prev:
RE: asyndriver : Multiple drvAsynIPPort Mark Rivers
- Next:
Re: Discussion about licenses, copyrights, business, and source code J. Lewis Muir
- 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:
order of rules in Makefile Konrad, Martin
- Next:
Re: order of rules in Makefile Konrad, Martin
- 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
|