[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Must be very simple
From: |
PATTON, BILLY \(SBCSI\) |
Subject: |
RE: Must be very simple |
Date: |
Mon, 20 Mar 2006 10:55:29 -0600 |
Let me back up and explain more
My top level makefile contains 8 flows. All flows depend on the
variables, which are lists, in the make.include files. From the TOP_DIR
there exists the possibility of 5 layers of directories. There are over
450 different directories created. In each directory there is the
possibility of a make.include and a make.dependencies. These files are
also stored in a Version Control System(VCS). The hierarchail targets
depends on these variables/list to create the rules. It's all very
hierarchial to separate all the directories. Having the list there
allows the developer of their piece the freedom to add items to any
list. When I put all these lists into a single file it was over 25K+
lines, not very good for developers. The developer needs the option of
having not to edit the VCS version every time they need to test their
fixes. So the top level make file needs to include the ones from the
developer area, if they exist, or from the VCS area if they don't.
-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of PATTON,
BILLY (SBCSI)
Sent: Monday, March 20, 2006 10:19 AM
To: Paul D. Smith
Cc: address@hidden
Subject: RE: Must be very simple
Over 450 + directories -I would be too large.
I'm working on a rule
all : inc_makefiles
.NONPARALLEL : inc_makefile
inc_makefile :
<tab>$(foreach ...
But this will not work.
I must have these variables alive for the creation of rules before any
rules fire.
wildcard will work if I know if the first directory exists. If it
doesn't I don't want to wildcard the second directory
I could K's of duplicate variables.
-----Original Message-----
From: Paul Smith [mailto:address@hidden On Behalf Of Paul D. Smith
Sent: Monday, March 20, 2006 10:12 AM
To: PATTON, BILLY (SBCSI)
Cc: address@hidden
Subject: RE: Must be very simple
%% "PATTON, BILLY \(SBCSI\)" <address@hidden> writes:
pb> Yes you are correct, It does not need to be in a rule format.
pb> This must be done before any rules are defined because these files
pb> have lists that are there to create the rules. But because the
pb> list may be edited I need to get he lists form the SRC_TREE if the
pb> exist then the other directory if they do not exist.
See my info about $(wildcard ...).
Of course, the normal way to do this is invoke make with -I:
make -I $(SRC_TREE) -I $(OTHER_DIR) ...
then just use:
include make.include
and make will walk the list of -I directories and include the first
"make.include" it finds.
--
------------------------------------------------------------------------
-------
Paul D. Smith <address@hidden> Find some GNU make tips at:
http://www.gnu.org http://make.paulandlesley.org
"Please remain calm...I may be mad, but I am a professional." --Mad
Scientist
_______________________________________________
Help-make mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/help-make
- Re: Must be very simple, (continued)
- Re: Must be very simple, Paul D. Smith, 2006/03/20
- RE: Must be very simple, PATTON, BILLY \(SBCSI\), 2006/03/20
- RE: Must be very simple, PATTON, BILLY \(SBCSI\), 2006/03/20
- RE: Must be very simple, PATTON, BILLY \(SBCSI\), 2006/03/20
- RE: Must be very simple, PATTON, BILLY \(SBCSI\), 2006/03/20
- RE: Must be very simple,
PATTON, BILLY \(SBCSI\) <=
- RE: Must be very simple, PATTON, BILLY \(SBCSI\), 2006/03/20
- RE: Must be very simple, PATTON, BILLY \(SBCSI\), 2006/03/20
- RE: Must be very simple, PATTON, BILLY \(SBCSI\), 2006/03/20
- RE: Must be very simple, PATTON, BILLY \(SBCSI\), 2006/03/20