| blob | 5776ea722e881e4ab05d6e33ae8edd78e8c6a22f |
3 # ************************************************************
4 # Description : Base class for all project creators
5 # Author : Chad Elliott
6 # Create Date : 3/13/2002
7 # ************************************************************
9 # ************************************************************
10 # Pragmas
11 # ************************************************************
25 #use Tie::IxHash;
30 # ************************************************************
31 # Data Section
32 # ************************************************************
34 ## The basic extensions known to a project creator
40 ## This feature is enabled or disabled depending on whether
41 ## or not the -static option is used.
44 ## Valid names for assignments within a project
45 ## Bit Meaning
46 ## 0 Preserve the order for additions (1) or invert it (0)
47 ## 1 Add this value to template input value (if there is one)
48 ## 2 Preserve <% %> settings for evaluation within the template
80 );
82 ## Custom definitions only
83 ## Bit Meaning
84 ## 0 Value is always an array
85 ## 1 Value is an array and name gets 'outputext' converted to 'files'
86 ## 2 Value is always scalar
87 ## 3 Name can also be used in an 'optional' clause
88 ## 4 Needs <%...%> conversion
133 );
135 ## Custom sections as well as definitions
136 ## Value Meaning
137 ## 0 No modifications
138 ## 1 Needs <%...%> conversion
146 );
148 ## All matching assignment arrays will get these keywords
150 );
152 ## Deal with these components in a special way
156 );
159 );
165 ## Matches with generic_outputext
168 ## These constants are used with the "project info" and
169 ## must match the order that is defined by the call order
170 ## of ProjectCreator::update_project_info(). This called
171 ## order is determined by the TemplateParser.
172 ##
173 ## NOTE: If you are going to add a new constant, you must make it the
174 ## numeric value of the CONFIGURATIONS constant and increment
175 ## the existing CONFIGURATIONS value.
186 # ************************************************************
187 # C++ Specific Component Settings
188 # ************************************************************
190 ## Resource files tag for C++
193 ## Valid component names within a project along with the valid file extensions
195 'template_files' => [ "_T\\.cpp", "_T\\.cxx", "_T\\.cc", "_T\\.c", "_T\\.C", "_t\\.cpp", "_t\\.cxx", "_t\\.cc", "_t\\.c", "_t\\.C", "\\.tpp" ],
200 );
202 ## Exclude these extensions when auto generating the component values
204 );
206 ## These matching assignment arrays will get added, but only to the
207 ## specific project component types.
211 ],
213 ],
214 );
216 # ************************************************************
217 # C# Specific Component Settings
218 # ************************************************************
220 ## Resource files tag for C#
223 ## Valid component names within a project along with the valid file extensions
235 );
239 ],
243 ],
244 );
246 # ************************************************************
247 # Java Specific Component Settings
248 # ************************************************************
250 ## Valid component names within a project along with the valid file extensions
253 );
255 # ************************************************************
256 # Visual Basic Specific Component Settings
257 # ************************************************************
259 ## Resource files tag for VB
262 ## Valid component names within a project along with the valid file extensions
269 );
272 );
274 # ************************************************************
275 # Language Specific Component Settings
276 # ************************************************************
278 # Index Description
279 # ----- -----------
280 # 0 File types
281 # 1 Files automatically excluded from source_files
282 # 2 Assignments available in standard file types
283 # 3 The entry point for executables
284 # 4 The language uses a C preprocessor
285 # 5 Name of the tag for 'resource_files' for this language
286 # * This is special because it gets treated like source_files in that
287 # a project with only these files is a library/exe not "custom only".
289 ## NOTE: We call the constant as a function to support Perl 5.6.
300 );
303 # ************************************************************
304 # Subroutine Section
305 # ************************************************************
308 my($class, $global, $inc, $template, $ti, $dynamic, $static, $relative, $addtemp, $addproj, $progress, $toplevel, $baseprojs, $gfeature, $relative_f, $feature, $features, $hierarchy, $exclude, $makeco, $nmod, $applypj, $genins, $into, $language, $use_env, $expandvars, $gendot, $comments, $foreclipse, $pid) = @_;
365 }
369 ## Is the name passed in a known keyword for a project. This includes
370 ## keywords mapped by Define_Custom or Modify_Custom.
373 }
382 ## If it doesn't contain a path, search the include path
386 }
388 ## Read and parse the global project file
392 }
395 }
401 ## If the value we are going to set for $name has been used as a
402 ## scoped template variable, we need to hijack the whole assignment
403 ## and turn it into a template variable assignment.
407 }
408 }
414 ## Handle both recursive_includes and recursive_libpaths in one
415 ## search and replace.
417 ## This portion of code was lifted directly from Creator::relative()
418 ## but modified to always expand the variables. We will turn the
419 ## expanded values back into variables below and once they're passed
420 ## off to the assignment processing code, they will be turned into
421 ## relative values (if possible).
430 }
431 }
433 ## Create an array out of the recursive directory list. Convert all
434 ## of the relative or full path values back into $() values.
440 ## This directory doesn't exist, just add the original value
442 }
444 ## Create an array out of the directory list and add it to our
445 ## array.
448 }
449 }
451 ## We need to return a string, so we join it all together space
452 ## separated.
454 }
457 }
463 ## See if the name is one of the special "recursive" settings. If so,
464 ## fix up the value and change the name.
470 ## Support dependency attributes. They may or may not be used by
471 ## the project or workspace creator implementation. They are
472 ## stored separately from the dependencies themselves. Also, note
473 ## that a value to be added may contain more than one element to be
474 ## added. This function will be called for each one, so we only
475 ## need to handle one at a time.
477 ## The value may contain multiple projects. But, only one
478 ## dependency attribute will be present at any time. So, once we
479 ## get here, we need to remove any of the other projects from the
480 ## front of the key string.
485 }
487 ## Check the after value and warn the user in the event that it
488 ## contains a value that can not be used within a project name.
493 }
495 ## Support the '*' mechanism as in the project name, to allow
496 ## the user to correctly depend on another project within the same
497 ## directory.
501 }
503 }
504 ## Support the '*' mechanism for libs assignment as well.
507 }
509 ## If this particular project type does not consider the dollar sign
510 ## special and the user has provided two dollarsigns as an escape, we
511 ## will turn it into a single dollar sign.
514 }
516 ## If the assignment name is valid and requires parameter (<%...%>)
517 ## replacement, then do so. But, only do so on actual keywords.
518 ## User defined keywords must not have the parameters replaced in
519 ## order for them to get the correct replacement values later on.
523 }
524 }
528 }
530 ## Call the base process_assigment() after we have modified the name and
531 ## value.
534 ## Support keyword mapping here only at the project level scope. The
535 ## scoped keyword mapping is done through the parse_scoped_assignment()
536 ## method.
543 }
544 }
545 }
551 ## See if the name is one of the special "recursive" settings. If so,
552 ## fix up the value and change the name.
556 }
562 ## See if the name is one of the special "recursive" settings. If so,
563 ## fix up the value and change the name.
566 ## If the assignment name is valid and requires parameter (<%...%>)
567 ## replacement, then do so. But, only do so on actual keywords.
568 ## User defined keywords must not have the parameters replaced in
569 ## order for them to get the correct replacement values later on.
573 }
576 }
582 ## If there is a previous value ($nval) and the keyword is going to be
583 ## evaled, we need to separate the values with a command separator.
584 ## This has to be done at the MPC level because it isn't always
585 ## possible for the user to know if a value has already been added to
586 ## the keyword (prebuild, postbuild and postclean).
591 }
594 }
595 }
597 ## For an addition, we need to see if it is a project keyword being
598 ## used within a 'specific' section. If it is, we may need to update
599 ## scoped settings for that variable (which are in essence template
600 ## variables).
603 ## Next, we just give everything to the base class method.
605 }
611 ## For a subtraction, we need to see if it is a project keyword being
612 ## used within a 'specific' section. If it is, we may need to update
613 ## scoped settings for that variable (which are in essence template
614 ## variables).
617 ## Next, we just give everything to the base class method.
619 }
625 ## If we weren't passed an assignment hash, then we need to
626 ## look one up that may possibly correctly deal with keyword mappings
633 }
634 }
636 ## Get the assignment value
639 ## If we are involved in a subtraction, we get back a value and
640 ## it's a scoped or mapped assignment, then we need to possibly
641 ## expand any template variables. Otherwise, the subtractions
642 ## may not work correctly.
645 }
648 }
656 ## Deal with the inheritance hierarchy first
657 ## Add in the base projects from the command line
664 }
667 }
668 }
672 ## Read in the parent onto ourself
678 }
685 }
686 }
692 ## Push the base project file onto the parent stack
695 ## Collect up some information about the inheritance tree
699 }
704 }
706 ## Begin reading the parent
711 ## Take the base project file off of the parent stack
715 }
717 ## The base project has already been read. So, if
718 ## we are reading the original project (not a parent base
719 ## project), then the current base project is redundant.
727 }
728 }
729 }
730 }
734 }
735 }
736 }
738 ## Copy each value from global_assign into assign
743 }
744 }
745 }
748 }
762 }
765 }
766 }
770 }
771 }
774 }
780 ## First check for properties that correspond to the current project
781 ## type. Elements that begin with "prop:" indicate a property.
791 }
794 }
795 }
798 }
799 }
802 }
803 }
805 ## If none of the elements match a property, then check the type
806 ## against the current project type or the default component name
807 ## (which is what it would be set to if a specific clause is used with
808 ## out parenthesis).
813 ## Nothing matched
815 }
824 ## parse_known() passes back an array of values
825 ## that make up the contents of the line parsed.
826 ## The array can have 0 to 4 items. The first,
827 ## if defined, is always an identifier of some
828 ## sort.
835 ## Project Ending
838 ## Call into the project type's pre-generation hook.
841 ## Fill in all the default values
844 ## Perform any additions, subtractions
845 ## or overrides for the project values.
852 }
855 }
858 }
859 }
860 }
865 }
866 }
869 ## Generate default target names after all source files are added
870 ## and after we've added in all of the options from the
871 ## command line. If the user set exename on the command line
872 ## and no "main" is found, sharedname will be set too and
873 ## most templates do not handle that well.
876 ## End of project; Write out the file.
879 ## write_project() can return 0 for error, 1 for project
880 ## was written and 2 for project was skipped
882 ## Save the library name and location
891 }
894 }
899 }
904 }
906 }
907 }
909 ## Check for unused verbatim markers
915 }
916 }
917 }
918 }
919 }
921 ## Reset all of the project specific data. I am explicitly
922 ## not resetting dependency_attributes. It is necessary that
923 ## this information stay for the life of the ProjectCreator
924 ## object so that the WorkspaceCreator can have access to the
925 ## information.
929 }
933 }
946 }
947 }
949 }
951 ## Project Beginning
954 ## Set up the default project name
958 ## We should only set the project name if we are not
959 ## reading in a parent project.
965 ## Replace any *'s with the default name
970 }
973 }
977 }
978 }
983 }
984 }
985 }
987 ## Signify that we have a valid project
989 }
990 }
992 ## $values[1] = name; $values[2] = value
995 }
999 }
1000 }
1002 ## $values[1] = name; $values[2] = value
1005 }
1009 }
1010 }
1012 ## $values[1] = name; $values[2] = value
1015 }
1019 }
1020 }
1029 }
1033 }
1039 }
1047 {});
1048 }
1050 ## We still need to parse the scope, but we will be
1051 ## throwing away whatever is processed. However, it
1052 ## could still be invalid code that will cause an error.
1058 }
1059 }
1063 }
1066 }
1071 }
1075 }
1076 }
1077 }
1086 }
1087 }
1091 }
1092 }
1095 }
1098 }
1104 ## Map the assignment name on a scoped assignment
1108 }
1115 }
1118 }
1122 }
1124 ## If there is no value in $$flags, then we need to get
1125 ## the outer scope value and put it in there.
1129 }
1131 }
1133 ## If there is no value in $$flags, then we need to get
1134 ## the outer scope value and put it in there.
1138 }
1140 }
1142 }
1145 }
1153 ## Save the addtemp state if we haven't done so before
1157 }
1159 ## If the name that is used within a specific is a mapped keyword
1160 ## then we need to translate it into the mapped keyword as it will
1161 ## be used by the TemplateParser.
1169 }
1170 }
1172 ## Now modify the addtemp values
1180 ## Regardless of whether there was and assignment value, we need to
1181 ## look at the template value of the base so that modification of a
1182 ## scoped variable includes the base values.
1187 }
1188 }
1191 }
1192 }
1194 ## Subsitute all pseudo variables for the project specific characters.
1199 ## If there are template variable settings, then we need to add
1200 ## this new one to the end of the settings that did not come from
1201 ## the command line. That way, adjust_value() does not need to
1202 ## sort the values (and have knowledge about which came from the
1203 ## command line and which didn't).
1210 }
1211 }
1212 }
1215 }
1217 ## If the variable name is not scoped, we need to look through existing
1218 ## scoped variables that match the base. If we find one, we need to
1219 ## propagate this value into the scoped settings.
1228 }
1229 }
1230 }
1231 }
1232 }
1234 ## 0: (0 set, 1 add, -1 subtract)
1235 ## 1: The text value
1236 ## 2: (true set on command line, false set in project)
1237 ## 3: The original variable name if it's scoped or mapped
1239 }
1247 ## Unknown assignments within a 'specific' section are handled as
1248 ## template value modifications. These are handled exactly as the
1249 ## -value_template option in Options.pm.
1251 ## If $type is not defined, then we are skipping this section
1255 }
1264 }
1269 ## This is a special concession for Windows. It will not allow
1270 ## you to set an empty environment variable. If an empty
1271 ## double quoted string is found, we will assume that the user
1272 ## wanted an empty string.
1276 }
1277 }
1279 }
1280 }
1282 ## If the type is not defined, then this is something other than an
1283 ## assignment in a 'specific' section and should be flagged as an error
1285 }
1294 }
1295 }
1301 }
1311 ## If this returns true, then we've found an assignment
1316 }
1317 }
1319 ## If we successfully remove a '!' from the front, then
1320 ## the file(s) listed are to be excluded
1324 ## Convert any $(...) in this line before we process any
1325 ## wild card characters. If we do not, scoped assignments will
1326 ## not work nor will we get the correct wild carded file list.
1327 ## We also need to make sure that any back slashes are converted to
1328 ## slashes to ensure that later flag_overrides checks will happen
1329 ## correctly.
1333 ## Now look for specially listed files.
1334 ## Regular expressions are very slow. Searching the line twice with
1335 ## index() is 328 times faster than searching with just the regular
1336 ## expression when it doesn't match (which is likely to be the case).
1351 }
1353 ## Check for both possible error conditions
1357 }
1361 }
1363 ## Keys used internally to MPC need to be in forward slash format.
1369 }
1370 ## We can not convert slashes here as we do for dependencies
1371 ## (below). The files specified here need to retain the forward
1372 ## slashes as they are used elsewhere.
1374 }
1377 }
1378 }
1380 ## If there is a command helper, we need to add the output files
1381 ## here. It is possible that helper determined output files are
1382 ## the only files added by this component type.
1395 }
1396 }
1397 }
1399 ## Set up the files array. If the line contains a wild card
1400 ## character use CORE::glob() to get the files specified.
1404 }
1405 ## Don't glob the line if we're wanting to remove the file. Wait
1406 ## until later to do the wildcard expansion (in remove_excluded).
1409 }
1412 }
1414 ## If we want to remove these files at the end too, then
1415 ## add them to our remove_files hash array.
1419 }
1422 }
1423 }
1425 ## If we're excluding these files, then put them in the hash
1430 }
1432 ## Set the flag overrides for each file
1436 ## We are giving these flag overrides to multiple files. We must
1437 ## do so because these files are all in the same group.
1439 }
1440 }
1443 ## Add the file if we're not excluding it
1446 ## The user listed a file explicitly, whether we
1447 ## excluded it or not.
1449 }
1450 }
1451 }
1454 }
1469 }
1472 }
1475 }
1482 }
1483 }
1486 }
1503 ## For the custom scoped assignments, we want to put a copy of
1504 ## the original custom defined values in our flags associative array.
1508 }
1509 }
1510 }
1514 }
1517 }
1520 }
1523 }
1526 # preserve order
1527 #tie %$names, "Tie::IxHash";
1528 #tie %$comps, "Tie::IxHash";
1535 }
1541 }
1546 }
1547 }
1554 }
1557 ## The default components name was never used
1558 ## so we remove it from the components
1561 ## For custom_only projects, an empty section is functionally
1562 ## equivalent to not defining it at all.
1566 }
1568 ## It was used, so we need to add that name to
1569 ## the set of group names unless it's already been added.
1572 ## Define the defaulted section value so that if a following
1573 ## empty section of the same type is found, it will not cause the
1574 ## defaulted value to be overwritten.
1576 }
1580 }
1582 ## We are at the end of a component. If the only group
1583 ## we added was the default group, then we need to remove
1584 ## the group setting altogether.
1590 }
1591 }
1593 ## This is not an error,
1594 ## this is the end of the components
1596 }
1597 }
1604 }
1605 }
1607 ## If this is a "special" component, we need to see if the
1608 ## user provided all directories. If they have, then we need to
1609 ## store an array of directories that the user supplied. Otherwise,
1610 ## we just store a 1.
1619 }
1623 }
1624 }
1625 }
1626 }
1629 }
1632 }
1633 }
1635 ## If we didn't encounter an error, didn't have any files explicitly
1636 ## listed and we attempted to exclude files, then we need to find the
1637 ## set of files that don't match the excluded files and add them.
1649 }
1650 }
1658 }
1661 }
1669 }
1671 ## All types are lower case
1676 }
1678 ## Instead of always creating a new array for a particular type and
1679 ## location, create a new array if there isn't one already or the user
1680 ## does not want to add to the existing verbatim settings.
1688 ## This is not an error,
1689 ## this is the end of the verbatim
1692 }
1695 }
1709 }
1713 }
1714 }
1717 ## The required features are enabled, so we say that
1718 ## a project has been defined and we allow the parser to
1719 ## find the data held within the feature.
1724 }
1725 }
1727 ## Otherwise, we read in all the lines until we find the
1728 ## closing brace for the feature and it appears to the parser
1729 ## that nothing was defined.
1734 ## This is a very simplistic way of finding the end of
1735 ## the feature definition. It will work as long as no spurious
1736 ## open curly braces are counted.
1743 }
1744 }
1745 }
1748 }
1757 }
1758 }
1762 }
1770 }
1771 }
1772 }
1773 }
1774 }
1780 ## Make the tag something _files
1783 ## We can not have a custom type named "generic"
1789 }
1790 }
1793 }
1798 }
1802 }
1805 }
1807 }
1812 ## Update the custom_types assignment
1819 }
1827 }
1839 }
1840 }
1845 }
1846 }
1851 }
1859 ## Fix $opt spacing
1863 ## Set up the 'optional' hash table
1868 }
1872 }
1873 }
1878 }
1879 }
1880 }
1885 ## Propagate the custom defined values into the mapped values
1891 ## Bypass the process_assignment() defined in this class
1892 ## to avoid unwanted keyword mapping.
1894 }
1895 }
1897 ## Set some defaults (if they haven't already been set)
1900 }
1903 }
1906 }
1909 }
1912 }
1915 }
1918 }
1920 }
1923 ## If this returns true, then we've found an assignment
1926 ## The 'automatic' keyword has always contained two distinct
1927 ## functions. The first is to automatically add input files of
1928 ## the specified extension. And the second is to automatically
1929 ## add generated files to the right components. It has now been
1930 ## split into separate functionality and we map the 'automatic'
1931 ## keyword to the two new ones here.
1942 }
1946 }
1947 ## Try to convert the value into a relative path
1955 }
1960 }
1965 }
1966 }
1969 ## Transform the name from something outputext to
1970 ## something files. We expect this to match the
1971 ## names of valid_assignments.
1973 }
1975 ## Get it ready for regular expressions
1978 ## Split the value into an array using a comma as the
1979 ## separator. If there are no elements in the array we're
1980 ## going to add an empty element to the array. This way,
1981 ## assignments of blank values are useful.
1985 ## Process the array assignment after adjusting the values
1989 }
1990 }
1991 }
1997 }
1998 }
2000 ## $status is zero until the end of the define custom block, so
2001 ## we can't use it for this check.
2003 }
2005 ## Check for keyword mapping here
2013 }
2016 }
2020 }
2026 }
2027 }
2032 }
2033 }
2038 }
2039 }
2040 }
2043 }
2052 ## Get both of the relative value hash maps and put them in an array
2059 ## Go through each value and try to convert it to a variable setting
2061 ## Fix up the value, replacing '.' with the current working
2062 ## directory.
2067 }
2070 }
2073 ## Go through each relative value hash map and see if any of the
2074 ## values match the value that we're currently inspecting.
2078 ## Get the relative replacement value and convert back-slashes
2082 ## We only need to check for reverse replacement if the length
2083 ## of the value is greater than or equal to the length of our
2084 ## replacement value.
2087 ## Cut the string down by the length of the replacement value
2090 ## Check for equivalence, taking into account file system
2091 ## case-insenitivity.
2094 }
2097 }
2099 ## If they match, replace the value and save it in our array.
2104 }
2105 }
2106 }
2108 ## Once it's been found, there's no reason to continue on through
2109 ## the relative hash maps.
2111 }
2114 }
2117 }
2124 ## If we are modifying the libs, libpaths, macros or includes
2125 ## assignment with either addition or subtraction, we are going to
2126 ## perform a little fix on the value to avoid multiple
2127 ## libraries and to try to insure the correct linking order
2134 ## Convert the array into keys for a hash table
2137 ## In order to ensure that duplicates are correctly removed, we
2138 ## need to get the modified assignment value before we attempt to
2139 ## do so.
2143 ## We need to supply quotes if there is a space in the value or
2144 ## a variable. The variable may contain spaces.
2146 ## If we're going to add quotes around this item and the
2147 ## value ends in a backslash we need to append another
2148 ## backslash so that when it's used with
2149 ## StringProcessor::create_array() the function will not think
2150 ## that the trailing quote is escaped.
2153 }
2156 }
2157 }
2158 }
2161 }
2162 }
2165 }
2181 ## Check for the TemplateInputReader for the template key provided.
2186 }
2189 }
2190 }
2191 }
2194 ## Check for the TemplateInputReader for the template key provided.
2199 }
2202 }
2203 }
2204 }
2205 }
2209 ## Check for the TemplateInputReader for the template key provided.
2214 }
2217 }
2218 }
2219 }
2222 ## Check for the TemplateInputReader for the template key provided.
2227 }
2230 }
2231 }
2232 }
2233 }
2236 ## We have a TemplateInputReader for this template key, so we need
2237 ## to set the entry corresponding to $tikey to it for use in the
2238 ## get_template_input() method.
2240 }
2242 ## We haven't read this file yet, so we will create the template
2243 ## input reader and store it in the entry for the template key
2244 ## ($tkey) and the template input key ($tikey).
2249 ## Process the template input file
2254 }
2256 ## Not finding a template input file is only an error if the user
2257 ## specifically provided a template input file override.
2261 }
2262 }
2263 }
2265 ## Now that we've read in the template input file, set up our
2266 ## automatic template variables.
2270 }
2271 }
2273 ## We do this regardless of whether or not this parser is cached or
2274 ## not. If the features have changed (through a workspace cmdline
2275 ## setting), we need to reflect it.
2277 ## Put the features into the template input set
2281 }
2284 }
2291 ## This method expects that the file name will be unix style
2294 ## Remove the leading ./
2298 ## Take into account file system case-insenitivity.
2302 }
2308 }
2311 }
2322 }
2327 }
2335 }
2338 }
2339 }
2355 }
2357 ## We are coming into an '||', if status is already true
2358 ## then we can leave immediately
2363 }
2364 }
2367 }
2368 }
2371 }
2373 }
2377 }
2380 }
2381 }
2382 }
2385 }
2393 foreach my $opt (keys %{$self->{'generated_exts'}->{$gentype}->{'optional'}->{$tag}->{$name}}) {
2394 ## Get the name value
2398 ## Convert the value into a hash map for easy lookup
2402 ## See if the option or options are contained in the value. We
2403 ## need to call this even if $value is not defined due to the
2404 ## ability to negate optional parameters.
2406 ## Add the optional portion
2407 push(@$array, @{$self->{'generated_exts'}->{$gentype}->{'optional'}->{$tag}->{$name}->{$opt}});
2408 }
2409 }
2410 }
2411 }
2412 }
2418 ## Get the general pre extension array.
2419 ## $self->{'generated_exts'}->{$gentype}->{$keyword} is guaranteed to
2420 ## be defined due to the defaulting that is done in
2421 ## parse_define_custom() and the only three calls to this method use
2422 ## valid $keyword values.
2425 ## Add the component specific pre extension array
2430 }
2432 ## Add in any optional portion to the array
2436 }
2438 ## If the current array only has the default,
2439 ## then we need to remove it
2443 }
2445 }
2448 }
2467 }
2468 }
2469 }
2471 ## If gendir was specified, then we need to account for that
2479 }
2483 }
2484 }
2485 }
2486 }
2490 }
2493 }
2494 }
2495 }
2496 }
2497 }
2501 ## $part - The full path of the input file minus the extension
2502 ## $type - The input file type (e.g., 'java_files')
2503 ## $file - The full path of the input file
2504 ## $noext - bool indicating an inverse need for an extension
2505 ## $arrs - bool indicating that the return array should be made of arrays
2507 ## A custom type is not allowed to generate it's own input files
2510 ## See if the type for which we are generating ($tag) is also a custom
2511 ## file type. If it is, we need to do some massaging.
2514 ## If the custom type ($type) doesn't specify that it generates
2515 ## generic files, we need to see if there is a command helper for
2516 ## this type and see what sort of output it knows about.
2521 }
2523 ## We will need to use 'generic_files' instead of $tag if $tag is
2524 ## defined in 'generated_exts', but only for the type that will
2525 ## actually generate the right type of generic file.
2536 }
2537 }
2539 }
2540 }
2542 ## If we were not able to find the right file type, then we can get
2543 ## out early. However, if the type for which we are generating
2544 ## ($tag) is a built-in type, we need to continue on as there is a
2545 ## possibility that the input type ($type) will generate files for
2546 ## the generating type.
2549 }
2565 }
2566 }
2571 ## If both arrays are defined to be the defaults, then there
2572 ## is nothing for us to do.
2573 }
2578 ## Correctly deal with pre filename and directories
2580 ## Split the directory and base name of the file. Only set the
2581 ## directory if the output follows the input directory.
2585 }
2588 }
2590 ## If gendir was specified, then we need to account for that
2596 }
2600 }
2601 }
2603 ## Loop through creating all of the possible file names
2612 }
2617 }
2618 }
2619 }
2620 }
2623 }
2626 }
2627 }
2628 }
2630 ## Now add the explicit output. We need to use the original tag value
2631 ## ($otag) so that we can find the custom output files.
2634 }
2640 ## This method is called by list_default_generated. It performs the
2641 ## actual file insertion and grouping.
2642 ## Get the generated filenames
2648 }
2649 }
2654 ## Get all files in one list and save the directory
2655 ## and component group in a hashed array.
2663 }
2664 }
2665 }
2667 ## Create a small array of only the files we want to add.
2668 ## We put them all together so we can keep them in order when
2669 ## we put them at the front of the main file list.
2673 }
2675 ## If we have files to add, make sure we add them to a group
2676 ## that has the same directory location as the files we're adding.
2684 }
2686 ## If this component name does not match the component name for
2687 ## which we are adding files and there are components defined
2688 ## for it, we will look to see if we can find a matching group
2689 ## name. We have to make sure that we do not use the hash map
2690 ## ($self->{$vc}) unless it's defined. Doing so will
2691 ## automatically create the map and that will cause MPC to
2692 ## think that the user provided the empty setting (when it
2693 ## wasn't).
2702 }
2706 }
2707 }
2708 }
2710 }
2711 }
2713 }
2714 }
2716 }
2723 }
2726 }
2728 }
2729 }
2730 }
2731 }
2744 ## Remove c++ style comments
2747 ## Remove one line c style comments
2752 ## Found the end of a multi-line c style comment
2754 }
2755 }
2758 ## Found the beginning of a multi-line c style comment
2760 }
2762 ## If the current language supports a c preprocessor, we
2763 ## will perform a minimal check for #if 0
2765 ## Found the beginning of a #if 0
2767 }
2770 ## We need to keep track of any other #if directives
2771 ## to be sure that when we see an #endif we don't
2772 ## count the wrong one.
2774 }
2776 ## Found a #endif, so decrement our count
2778 }
2779 }
2780 }
2781 }
2783 ## Check for main; Make sure it's not #if 0'ed and not commented out
2788 ## If we've found a main, set the exename to the basename
2789 ## of the cpp file with the extension removed
2794 }
2796 }
2797 }
2798 }
2800 }
2802 }
2811 ## If additional main's have been supplied by the user for this
2812 ## language type, then just push them onto the array.
2815 ## Now search each source file until we've found a main function.
2819 }
2822 }
2828 ## If this is a custom_only project, we need not waste time setting the
2829 ## sharedname, staticname or exename. Searching all of the files for a
2830 ## main function is very time consuming and unnecessary.
2843 }
2847 }
2848 }
2852 }
2854 ## If it's neither an exe or library target, we will search
2855 ## through the source files for a main()
2857 ## Set the exename assignment
2862 ## If we still don't have a project type, then we will
2863 ## default to a library if there are source or resource files
2867 }
2872 }
2875 }
2876 }
2877 }
2878 }
2880 ## If we are generating only static projects, then we need to
2881 ## unset the sharedname, so that we can insure that projects of
2882 ## various types only generate static targets.
2887 }
2888 }
2890 ## Check for the use of an asterisk in the name
2897 }
2898 }
2899 }
2914 ## If the file doesn't even contain _pch, then there's no point
2915 ## in looping through all of the extensions
2924 }
2925 }
2926 }
2934 }
2935 }
2936 }
2937 }
2938 }
2941 }
2944 }
2945 }
2946 }
2952 ## Unset the precompiled header settings if they are set but empty
2956 }
2957 }
2969 ## If we are converting slashes, then we need to
2970 ## convert the pch file back to forward slashes
2973 ## Find out which files are duplicated
2984 }
2985 }
2986 }
2987 }
2988 }
2989 }
2990 }
2998 ## The special actions taken based on $saverc only applies to
2999 ## C++ resource files.
3005 ## Always exclude the precompiled header and cpp
3014 }
3015 }
3017 }
3019 ## Save these files for later. There may
3020 ## be more than one and we want to try and
3021 ## find the one that corresponds to this project
3024 }
3027 }
3028 }
3029 }
3031 ## Now deal with the saved files
3034 ## Theres only one rc file, take it
3036 }
3041 ## Use a case insensitive search.
3042 ## After all, this is a Windows specific file type.
3047 }
3048 }
3049 }
3050 }
3051 }
3052 }
3064 }
3073 ## If we are not automatically adding generated output, then we
3074 ## need to skip this component type.
3077 ## If we are auto-generating the source_files, then
3078 ## we need to make sure that any generated source
3079 ## files that are added are put at the front of the list.
3083 ## If I call keys %{$self->{$gentype}} using perl 5.6.1
3084 ## it returns nothing. I have to put it in an
3085 ## intermediate variable to ensure that I get the keys.
3091 }
3092 }
3112 ## No need to check for previously added files
3113 ## here since there are none.
3118 }
3119 }
3121 }
3123 ## The first file listed in @files is the preferred
3124 ## extension for the custom command. Take the first
3125 ## file extension and see if it matches one in the accepted
3126 ## extensions.
3131 }
3133 ## If it doesn't match one of the accepted extensions,
3134 ## then just use the first extension from the type for
3135 ## which we are generating.
3137 }
3139 ## Add all the files that match the chosen extension
3142 }
3143 }
3144 }
3145 }
3150 }
3151 }
3152 }
3154 ## No need to check for previously added files
3155 ## here since there are none.
3159 }
3160 }
3165 }
3168 }
3171 }
3173 }
3176 }
3177 }
3178 }
3179 }
3180 }
3181 }
3197 ## The order of @tags does make a difference in the way that generated
3198 ## files get added. Hence the sort call on the generate_exts keys to
3199 ## ensure that user defined types come first. They are reverse sorted
3200 ## using the custom sort function to ensure that user defined types
3201 ## that rely on other user defined types for input files are processed
3202 ## first.
3209 ## If the tag is defined, then process directories
3217 }
3227 ## Since the file was actually a directory, we will
3228 ## need to propagate the flag overrides (if there are
3229 ## any) to the newly located files.
3234 }
3235 }
3237 ## Always push the @portion array onto the back of
3238 ## @built.
3240 }
3245 }
3246 }
3247 }
3251 }
3253 }
3254 }
3255 }
3256 }
3258 ## Generate default values for undefined tags
3270 }
3271 }
3273 ## If the type that we're generating defaults for ($tag) is a
3274 ## custom type, then we need to see if other custom types
3275 ## ($gentype) will generate files that will be used as input. It
3276 ## has to be done here so that the built-in types will have all
3277 ## of the possible input files that they can.
3282 }
3283 }
3285 ## Now that we have the files for this type ($tag), we need to
3286 ## locate a command helper for the custom command and see if it
3287 ## knows about any additional output files based on the file
3288 ## name.
3307 }
3308 }
3309 }
3310 }
3311 }
3312 }
3313 }
3314 }
3315 }
3316 }
3317 }
3324 ## There's no point in going on if there's nothing in this component
3325 ## list.
3328 ## Convert the array into keys for a hash table
3332 ## Find out which source files are listed
3339 ## Is the source file in the component array?
3341 ## Remove the element and fix the index and count
3345 }
3346 }
3347 }
3348 }
3349 }
3356 ## Find out which generated source files are listed
3366 }
3367 }
3368 }
3369 }
3370 }
3373 }
3379 ## This method is called when the user has custom input files and has
3380 ## provided source files. If the user defaults the component (i.e.
3381 ## source_files, resource_files, etc.) they are filled in by the
3382 ## generate_default_components method.
3386 ## After all source and headers have been defaulted, see if we
3387 ## need to add the generated files
3389 ## Build up the list of files
3391 #tie %arr, "Tie::IxHash"; # preserve insertion order.
3399 ## Take the last group name we encounter
3406 }
3407 }
3408 }
3411 ## Only add generated files if the following is true:
3412 ## 1) The generating type is not the same as the receiving type.
3413 ## 2) The receiving type is not "special" (unless it hasn't been
3414 ## supplied by the user).
3415 ## 3) The receiving type is not user defined or it is user
3416 ## defined and has 'automatic_in' set to true.
3425 }
3426 }
3427 }
3428 }
3429 }
3430 }
3445 }
3452 ## Convert the file to unix style for basename
3456 }
3458 }
3459 }
3460 }
3461 }
3464 }
3471 ## Go through each file listed in our original type and attempt to find
3472 ## out if it is the generated file we may need to add ($file).
3476 ## Take the file and see if it contains an extension that our
3477 ## generating type ($gentype) knows about. If it does, remove it and
3478 ## stop looking for the extension.
3480 ## Remove the extension.
3481 ## If it works, then we can exit this loop.
3483 }
3485 ## If the user provided file does not match any of the
3486 ## extensions specified by the custom definition, we need
3487 ## to remove the extension or else this file will not be
3488 ## added to the project.
3491 ## See if we need to add the file. We always need to check since the
3492 ## output file may have absolutely nothing in common with the input
3493 ## file.
3496 ## $gen is a file that has a custom definition that generates
3497 ## files of the type $tag. The $file passed in is of type
3498 ## $gentype and, as far as I can tell, $created will always be
3499 ## longer or of the same length of $file. It doesn't really
3500 ## matter if $file contains a '.' or not.
3504 }
3508 }
3510 }
3511 }
3512 }
3515 }
3522 ## Create a hash array keyed off of the existing files of the type
3523 ## that we plan on adding.
3528 ## Check to see if files exist in the default group
3532 }
3535 }
3536 }
3538 ## Create an array of extensions for the files we want to add
3543 }
3545 ## Check each file against a possible new file addition
3554 }
3555 }
3558 ## Get the array of files for the selected component name
3564 }
3565 }
3567 ## First, see if it will be generated so that we can correctly
3568 ## deal with 'gendir' settings.
3571 }
3573 ## Next check to see if the file exists
3581 }
3583 }
3584 }
3585 }
3587 ## If we have any files at all in the component array, check
3588 ## to see if we need to add a new group name
3592 }
3598 }
3601 }
3603 ## Put the array back into the component list
3607 }
3608 }
3609 }
3610 }
3611 }
3613 ## We only need to add the default group name if we wanted to
3614 ## add the default group when adding new files and we added a group
3615 ## by some other name. Otherwise, defaulted files would always be
3616 ## in a group, which is not what we want.
3619 }
3620 }
3629 }
3631 ## Since files on UNIX can have back slashes, we transform them
3632 ## into underscores.
3635 ## Convert the name to a usable name
3638 ## Take off the extension
3640 }
3643 }
3650 ## Process each file type and remove the excluded files
3662 }
3664 ## The file does not match exactly with one of the files to
3665 ## remove. Look for wildcard specifications in the files to
3666 ## be removed and perform the removal if one of them matches
3667 ## the current file.
3679 }
3680 }
3681 }
3682 }
3683 }
3684 }
3685 }
3687 }
3688 }
3692 ## We need to sort the custom component types such that a custom type
3693 ## that generates input for another custom type comes first in the
3694 ## list.
3703 }
3704 }
3705 }
3706 }
3709 }
3712 }
3717 ## Generate default project name
3720 }
3722 ## Generate the default pch file names (if needed)
3728 ## If the pch file names are empty strings then we need to fix that
3731 ## Generate default components, but %specialComponents
3732 ## are skipped in the initial default components generation
3735 ## Remove source files that are also listed in the template files
3736 ## If we do not do this, then generated projects can be invalid.
3739 ## If pch files are listed in header_files or source_files more than
3740 ## once, we need to remove the extras
3743 ## Generate the default generated list of files only if we defaulted
3744 ## the generated file list. I want to ensure that source_files comes
3745 ## first in the list to pick up group information (since source_files
3746 ## are most likely going to be grouped than anything else).
3754 }
3756 ## Now that all of the source files have been added
3757 ## we need to remove those that have need to be removed
3760 ## Collect up all of the source files that have already been listed
3761 ## with the extension removed for use directly below.
3771 }
3772 }
3773 }
3774 }
3776 ## Add %specialComponents files based on the
3777 ## source_components (i.e. .h and .i or .inl based on .cpp)
3780 }
3782 ## Now, if the %specialComponents are still empty
3783 ## then take any file that matches the components extension
3789 ## We only want to generate default components if we have
3790 ## defaulted the source files or we have no files listed
3791 ## in the current special component.
3798 }
3799 }
3801 }
3803 ## If the "special" type was supplied and it was all
3804 ## directories, we need to use those directories to generate
3805 ## the default components instead of the current directory.
3814 }
3816 }
3818 }
3819 }
3820 }
3821 }
3823 ## The code to add template files automatically when it is left
3824 ## defaulted by the user may add source files that happen to end in _t
3825 ## (minus the extension). If we do not remove template files that are
3826 ## also listed as source files, the generated projects can be invalid.
3829 ## Now that all of the other files have been added
3830 ## we need to remove those that have need to be removed
3834 ## Tie custom files together if need be. This currently only applies
3835 ## to types with command helpers. At some point, if it is found to be
3836 ## desirous, we could extend the MPC syntax somehow to support this
3837 ## sort of thing manually.
3842 ## There has to be at least two files files in order for
3843 ## something to be tied together.
3851 ## We have a tied file, now we need to actually perform
3852 ## the tieing of the two. We will do this by saying that
3853 ## the output of the original is necessary for the
3854 ## processing of the tied file.
3861 }
3862 }
3866 ## We have found a set of files that are generated
3867 ## based on the component type of the original file
3868 ## ($gentype), so we just add the first one and
3869 ## we're done.
3873 ## We are about to modify the flag overrides for a tied file.
3874 ## We need to make a copy so that we do not affect the
3875 ## overrides of grouped, but no longer affiliated files.
3880 ## Start a new dependent setting based on the original
3881 ## custom build settings.
3884 }
3889 ## We are about to modify the flag overrides for a tied file.
3890 ## We need to make a copy so that we do not affect the
3891 ## overrides of grouped, but no longer affiliated files.
3895 }
3897 ## Update the dependent value for this tied file.
3899 }
3900 }
3901 }
3902 }
3903 }
3904 }
3905 }
3911 ## Save the unmodified project name so that when we
3912 ## need to determine the default target name, we can use
3913 ## what is expected by the user.
3916 ## If we are applying the name modifier to the project
3917 ## then we will modify the project name
3924 }
3925 }
3927 ## Set the project_name assignment so that the TemplateParser
3928 ## can get the project name.
3930 }
3935 }
3942 }
3947 }
3958 }
3959 }
3961 ## By default, if 'convert_slashes' is true, then we convert slashes
3962 ## to backslashes. There are cases where we do not want to convert
3963 ## the slashes, in that case get_component_list() was called with
3964 ## an additional parameter indicating this.
3968 }
3969 }
3973 }
3976 }
3989 }
3995 }
4001 ## We only match if the built file name matches from
4002 ## beginning to end or from a slash to the end.
4006 }
4007 }
4008 }
4009 }
4010 }
4013 }
4023 ## These names (held in $type) are variables that contain various
4024 ## commands that will be used in templates within the context of a
4025 ## foreach (e.g., <%custom_type->input_files%> or <%feature->value%>).
4028 }
4031 }
4034 }
4039 }
4044 }
4045 }
4046 }
4050 ## If the passed in type is not a builtin type, try the type with an
4051 ## 's' on the end.
4054 ## This is a hack for dealing with the fact that built-in types
4055 ## (e.g., Source_Files, Header_Files, etc.) are not real custom
4056 ## definitions. However, we can "modify" them to some extent.
4059 }
4062 }
4072 }
4073 }
4076 }
4083 ## Make it all lower case
4086 ## Remove the grouped_ part
4089 ## Add the s if it isn't there
4102 }
4104 }
4107 }
4111 }
4112 }
4113 }
4114 }
4116 ## If there is more than one name, then we will need
4117 ## to deal with that at a later time.
4120 }
4121 }
4124 }
4130 ## If the passed in type does not have a generated_exts definition,
4131 ## then try the type with an 's' on the end.
4134 ## If we have a builtin type that has the variable ($cmd) that we are
4135 ## looking for, process the value through command parameter conversion.
4141 }
4143 ## Otherwise, there's nothing here.
4145 }
4151 ## Add the built-in OS compatibility commands
4168 }
4184 }
4186 ## Add the project specific compatibility commands
4199 }
4215 }
4217 ## Support both pseudo variables and project settings
4219 ## If the pseudo variable is defined or the project setting has a
4220 ## value, then we'll need to do the replacement. However, if it's
4221 ## a project keyword and it's not defined, we will need to delay
4222 ## the replacement until later (unless $always_clear is true).
4227 }
4230 }
4232 ## Perform the modification and replacement here
4237 }
4240 }
4241 }
4243 }
4245 ## We need to clear out this variable usage.
4247 }
4249 ## Save this variable usage to be put back after we're done
4250 ## processing the string.
4254 }
4255 }
4256 }
4260 ## We only want to warn the user that we did not recognize the
4261 ## pseudo template parameter if there was an input and an output
4262 ## file passed to this function. If this variable was used
4263 ## without the parenthesis (as in an if statement), then we don't
4264 ## want to warn the user.
4268 }
4270 ## If we didn't recognize the pseudo template parameter then
4271 ## we don't want to return anything back.
4273 }
4274 }
4275 }
4277 ## Replace the saved variables so that they may be replaced (or
4278 ## removed) later on.
4281 }
4283 }
4291 ## Add in the values that change for every call to this function
4300 ## An input file doesn't always have an extension. If there isn't
4301 ## one, then we need to set the 'input_ext' field to an empty string
4302 ## ($1 will not necessarily have a valid value).
4305 }
4308 }
4310 ## Check for the gendir setting associated with this input file. We
4311 ## have to check at so many levels so we don't inadvertently create
4312 ## intermediate hash tables.
4317 }
4318 }
4320 ## If there is no gendir setting, just set it to the current directory.
4327 ## An output file doesn't always have an extension. If there isn't
4328 ## one, then we need to set the 'output_ext' field to an empty
4329 ## string ($1 will not necessarily have a valid value).
4333 }
4336 }
4339 ## In order to call basename or dirname, we must make sure that the
4340 ## directory separators are forward slashes.
4348 }
4349 }
4351 ## Add in the specific types of output files
4365 }
4366 }
4367 }
4368 }
4369 }
4372 }
4386 }
4388 }
4399 }
4404 ## Remove the extension
4407 ## If we are converting slashes,
4408 ## change them back for this parameter
4415 }
4422 }
4439 }
4442 }
4443 }
4447 }
4450 }
4454 }
4456 }
4467 ## Get the component list for the component type
4470 ## Check for directories in the component list. If the component
4471 ## type is not automatic, we may have directories here and will need
4472 ## to get the file list for that type.
4480 };
4481 }
4489 }
4490 }
4501 }
4509 ## Remove the extension
4512 ## If we are converting slashes,
4513 ## change them back for this parameter
4526 }
4527 }
4528 }
4532 }
4534 ## Add all of the output files. We can not add $generic_key to the
4535 ## list here (as it used to be). It may have been handled by
4536 ## generated_filenames.
4538 ## The output of multiple components could be input for the
4539 ## current component type ($based). We need to avoid adding
4540 ## duplicates here.
4546 }
4547 }
4552 }
4553 }
4560 }
4561 }
4567 }
4569 ## Add specially listed files avoiding duplicates. We don't want
4570 ## to add these files if gendir is set to something besides .
4576 }
4577 }
4582 }
4587 }
4588 }
4591 }
4593 }
4594 }
4596 # Generate output files based on $based
4599 }
4600 }
4602 # Generate source output files based on $based
4608 ## We've found a file that matches one of the source file
4609 ## extensions. Now we have to make sure that it doesn't
4610 ## match a template file extension.
4616 }
4617 }
4620 }
4621 }
4622 }
4623 }
4624 }
4626 # Generate non source output files based on $based
4634 ## We've found a file that matches one of the source file
4635 ## extensions. Now we have to make sure that it doesn't
4636 ## match a template file extension.
4641 }
4642 }
4644 }
4645 }
4647 }
4648 }
4649 }
4651 # Generate non-template output files based on $based
4660 }
4661 }
4663 }
4664 }
4665 }
4670 }
4672 }
4675 }
4679 ## Clear out the previous custom_multi_details hash map so that we don't
4680 ## have extraneous data associated with commands from previous iterations.
4690 ## Use $tag as the key for custom_multi_details and store the command as
4691 ## a data member that we can access later. $command shouldn't be used
4692 ## as the key because it is not guaranteed to be unique.
4699 }
4701 # only 1 output file is supported with output_option
4708 }
4711 }
4714 }
4715 }
4716 }
4718 ## Sort the list of types so that generated projects are reproducable.
4719 ## Additionally, we need them to be ordered (and numbered) so that we can
4720 ## match the command with the right tag when iterating in the template.
4726 }
4727 }
4733 }
4734 }
4736 ## This is only used with 'combined_custom'.
4737 ##
4738 ## $based - The command for the original define custom.
4739 ## $cmd - The member after the arrow operator.
4740 ##
4741 ## We cannot use a direct lookup because the command is no longer the
4742 ## key for custom_multi_details. It is possible to have two or more custom
4743 ## types that use the same command. Therefore, we have to use the custom
4744 ## type name ($tag) as the key. Since this code can only be called within
4745 ## a foreach, we have to rely on the fact that the values created above
4746 ## (during the processing of 'commands') are sorted to correlate the
4747 ## command, stored in $base, with the correct tag in order to get the
4748 ## correct command flags and other associated values.
4754 }
4756 }
4757 }
4758 }
4761 }
4773 ## By default, if the feature is not listed, then it is enabled.
4778 }
4780 ## For automakes sake, if we're to this point the feature is
4781 ## enabled and we will set it in the feature parser explicitly
4784 }
4785 }
4786 }
4788 ## If it passes the requires, then check the avoids
4794 ## By default, if the feature is not listed, then it is enabled.
4799 }
4800 }
4801 }
4802 }
4807 }
4810 }
4817 ## We always write a project if the user has provided a verbatim.
4818 ## We have no idea what that verbatim clause does, so we need to just
4819 ## do what the user tells us to do.
4822 ## The order here is important, we must check for source or resource
4823 ## files first and then for custom input files.
4826 ## For implicitly-discovered projects, just having a resource file without
4827 ## source or generated file is not enough to write a project.
4832 ## See if the project contains a file that corresponds to this
4833 ## component name.
4836 ## Return 2 if we have found a custom input file (and thus no
4837 ## source or resource files due to the foreach order).
4839 }
4840 ## We have either source files or resource files, we need to
4841 ## see if this project creator supports the current language.
4842 ## If it doesn't then we don't need to create the project.
4844 ## Return 1 if we have found a source file or a resource file.
4846 }
4847 }
4848 }
4849 }
4851 }
4853 ## Indicate that there is no need to write the project
4855 }
4865 ## The template override will override all templates
4869 ## Save the template name for use as a key for various function calls
4872 ## Create the output file name based on the project name and the
4873 ## template that we're currently using.
4878 ## If the template files does not end in the template extension
4879 ## then we will add it on.
4882 }
4884 ## If the template file does not contain a path, then we
4885 ## will search through the include paths for it.
4889 }
4892 }
4895 ## Read in the template values for the specific target and project
4896 ## type. The template input file we get may depend upon the
4897 ## current template that we're using.
4904 ## Set the project_file assignment for the template parser
4919 }
4922 }
4925 }
4926 }
4940 ## At this point in time, webapps do not get a project file,
4941 ## but they do appear in the workspace
4942 }
4944 ## First write the output to a temporary file
4951 }
4955 }
4960 }
4962 ## If they are different, then rename the temporary file
4970 }
4971 }
4976 }
4977 }
4979 ## We will pretend that we wrote the file
4981 }
4982 }
4988 }
4994 }
4995 }
5000 }
5001 }
5003 ## There may be more than one template associated with this
5004 ## project creator. If there is, we can only add one generated
5005 ## file and we rely on the project creator to tell us which
5006 ## template generates the file that we need to track.
5009 }
5010 }
5015 }
5016 }
5018 }
5036 }
5038 }
5057 }
5060 }
5061 }
5063 }
5064 }
5065 }
5066 }
5072 }
5083 }
5088 }
5089 }
5090 }
5109 }
5111 ## A return value of 2 from need_to_write_project() indicates
5112 ## that the only reason that we need to write the project is that
5113 ## there are custom input files (i.e., no source or resource
5114 ## files).
5119 }
5127 }
5128 }
5135 }
5136 }
5137 }
5138 }
5139 }
5141 ## Hook for implementing type-specific behavior.
5145 }
5146 ## We don't need to pass a file name here. write_output_file()
5147 ## will determine the file name for itself.
5150 ## Write the .ins file if the user requested it and we were
5151 ## successful.
5154 }
5155 }
5156 }
5163 }
5166 }
5167 }
5168 }
5171 }
5176 }
5185 # if we are a worker, we need to strip leading 'number|'
5190 }
5192 }
5195 }
5196 }
5201 }
5213 }
5219 }
5220 }
5227 ## Build up an array of extensions. Since they are stored as regular
5228 ## expressions, we need to remove the escaped period to provide the
5229 ## minimal amount of text for each extension to provide maximum
5230 ## flexibility within the project template.
5234 }
5235 }
5237 }
5243 }
5249 ## Only put data structures that need to be cleared
5250 ## out when the mpc file is done being read, not at the
5251 ## end of each project within the mpc file. Those go in
5252 ## the closing curly brace section of parse_line().
5256 }
5267 }
5268 }
5281 );
5287 }
5288 }
5293 ## Allow subclasses to override the default extensions
5295 }
5302 ## This follows along the same logic as read_template_input() by
5303 ## checking for exe target and then defaulting to a lib target
5307 }
5310 }
5311 }
5315 }
5318 }
5326 ## Append the values of all names into one string
5333 }
5335 ## There may be more than one template associated with this project
5336 ## creator. If there is, we can only add one generated file and we
5337 ## rely on the project creator to tell us which template generates the
5338 ## file that we need to track.
5340 ## If we already have an array, take the one off the top. Otherwise,
5341 ## create a new one which will be added below.
5345 ## Set up the hash table when we are starting a new project_info
5348 ## If we haven't seen this value yet, put it on the array
5352 }
5354 ## Always push the array back onto the project_info
5356 }
5359 }
5367 ## This will use the keys left in @_ as indices into the project
5368 ## info array. But, if the user wants configurations, we need to
5369 ## pop that key off and access it along with all the rest of the
5370 ## elements in the array. The CONFIGURATIONS key should always
5371 ## be last if it's included at all. If it's not, the caller will
5372 ## only receive the first configuration instead of all of them.
5377 }
5380 }
5387 ## Perform any additions, subtractions
5388 ## or overrides for the template values.
5395 ## If the template variable is a complex name, then we need to make
5396 ## sure that the mapped value belongs to the correct type based on
5397 ## the base of the complex name. The $tp (TemplateParser) variable
5398 ## will, in the majority of all calls to this method, be defined so
5399 ## it is checked second to avoid checking it if the name isn't
5400 ## complex.
5410 }
5412 }
5413 }
5415 }
5416 }
5424 }
5429 }
5431 ## Avoid adding duplicates. If the existing array contains
5432 ## the value already, remove it from the newly created array.
5437 }
5438 }
5440 ## We need to make $value a new array reference ($arr)
5441 ## to avoid modifying the array reference pointed to by $value
5444 }
5447 }
5448 }
5454 }
5457 }
5463 }
5464 }
5465 }
5466 }
5468 ## If the user set the variable to empty, then we need to
5469 ## set the value to undef
5471 }
5472 }
5474 }
5475 }
5478 }
5492 }
5496 }
5497 }
5498 }
5501 }
5509 }
5516 ## We don't apply the name modifier to the project file
5517 ## name if we have already applied it to the project name
5518 ## since the project file name comes from the project name.
5522 }
5524 }
5529 }
5534 }
5541 ## Only return the value stored in the valid_names hash map if it's
5542 ## defined and it's not an array reference. The array reference is
5543 ## a keyword mapping and all mapped keywords should have preserved
5544 ## assignment order.
5547 }
5550 }
5557 ## Only return the value stored in the valid_names hash map if it's
5558 ## defined and it's not an array reference. The array reference is
5559 ## a keyword mapping and no mapped keywords should be added to
5560 ## template input variables.
5563 }
5566 }
5570 #my $self = shift;
5572 }
5589 }
5590 }
5593 }
5595 }
5596 }
5598 }
5602 #my $self = shift;
5603 #my $name = shift;
5605 }
5611 ## Fill in the name if one wasn't provided
5614 ## Apply the transformation so that any name modifiers are utilized.
5619 }
5625 ## Remove any files that may have automatically been added
5626 ## to this project. If they were explicitly added, then we
5627 ## will leave them in the project.
5631 }
5632 }
5634 ## Unset the exename, sharedname and staticname
5638 }
5646 }
5648 ## If the user provided file does not match any of the
5649 ## extensions specified by the custom definition, we need
5650 ## to remove the extension or else this file will not be
5651 ## added to the project.
5654 }
5661 }
5664 }
5666 }
5668 }
5681 }
5692 }
5695 }
5705 ## Create a new feature parser. This relies on the fact that
5706 ## 'features' is restored first in restore_state().
5710 }
5711 }
5719 ## Clear out the template input reader that we're currently set
5720 ## to use.
5722 }
5723 }
5724 }
5726 ## If the user has changed the 'features' setting, then we need to
5727 ## make sure that we create a new feature parser regardless of
5728 ## whether or not the feature file has changed.
5730 }
5734 }
5735 }
5736 }
5741 }
5746 ## See if a language was supplied.
5748 ## If the language supplied is not one that we know about, return an
5749 ## error message.
5752 ## Otherwise, add it to the list for the language.
5754 }
5756 ## No language was supplied, so add the main to all of the languages
5757 ## that we support.
5760 }
5761 }
5763 ## Return no error message.
5765 }
5771 ## Not all entries in the %language map have a resource tag.
5772 ## For this, we will just return the tag for C++ since it probably
5773 ## doesn't really matter anyway.
5775 }
5780 ## No tag results in no command helper
5783 ## See if we have a command helper for this tag
5786 ## Give the command helper a reference to the creator. The helper
5787 ## can benefit from many of the infrastructure functions available.
5790 }
5792 ## None for the base define custom, try again with the parent
5794 }
5797 ## Return the dependency attribute specified as the first parameter to
5798 ## this method (not counting the ProjectCreator object).
5800 }
5803 #my($self, $name) = @_;
5805 }
5808 sub append_flag_override {
5820 }
5823 # Some project types can't represent the same input file being used by
5824 # more than one custom type. This function will look for such cases and
5825 # combine them into a single invocation of a synthetic custom type that
5826 # inherits properties from both of them.
5827 # Project types needing this transformation should call this function from
5828 # their overridden pre_write_output_file() method.
5829 sub combine_custom_types {
5852 }
5853 }
5854 }
5855 }
5856 }
5857 }
5859 # For each input file used in multiple custom types, move it into the new
5860 # synthetic type.
5864 . '_files';
5877 }
5878 }
5883 }
5888 }
5890 # Add to new type -- groups aren't relevant here, so just use the default
5893 # Remove from existing types
5901 }
5902 }
5903 }
5904 }
5908 }
5914 }
5915 }
5917 # If all existing uses agree to recurse, the new type should recurse too
5920 }
5922 }
5924 return 1;
5925 }
5927 sub set_forcount {
5930 }
5932 # ************************************************************
5933 # Accessors used by support scripts
5934 # ************************************************************
5936 sub getKeywords {
5938 }
5940 sub getValidComponents {
5943 }
5945 # ************************************************************
5946 # Virtual Methods To Be Overridden
5947 # ************************************************************
5949 sub get_builtin_output {
5951 return [];
5952 }
5954 sub languageSupported {
5957 }
5959 sub file_visible {
5961 return 1;
5962 }
5964 sub webapp_supported {
5966 return 0;
5967 }
5970 sub use_win_compatibility_commands {
5973 }
5976 sub post_file_creation {
5979 return undef;
5980 }
5983 sub escape_spaces {
5985 return 0;
5986 }
5989 sub validated_directory {
5992 }
5994 sub get_quote_symbol {
5997 }
5999 sub get_escaped_quote_symbol {
6002 }
6004 sub get_gt_symbol {
6007 }
6010 sub get_lt_symbol {
6013 }
6016 sub get_and_symbol {
6019 }
6022 sub get_or_symbol {
6025 }
6028 sub get_cmdsep_symbol {
6031 }
6034 sub dollar_special {
6036 return 0;
6037 }
6040 sub expand_variables_from_template_values {
6042 return 1;
6043 }
6046 sub require_dependencies {
6048 return 1;
6049 }
6052 sub dependency_is_filename {
6054 return 1;
6055 }
6058 sub fill_value {
6061 return undef;
6062 }
6065 sub project_file_prefix {
6068 }
6071 sub project_file_extension {
6074 }
6077 sub override_valid_component_extensions {
6080 return undef;
6081 }
6084 sub override_exclude_component_extensions {
6087 return undef;
6088 }
6091 sub get_dll_exe_template_input_file {
6093 return undef;
6094 }
6097 sub get_lib_exe_template_input_file {
6100 }
6103 sub get_lib_template_input_file {
6106 }
6109 sub get_dll_template_input_file {
6111 return undef;
6112 }
6115 sub get_template {
6117 }
6119 sub requires_forward_slashes {
6120 return 0;
6121 }
6123 sub warn_useless_project {
6124 return 1;
6125 }
6127 sub pre_write_output_file {
6128 return 1;
6129 }
6131 sub pre_generation {
6133 }
6135 sub default_to_library {
6136 return 0;
6137 }
6139 1;