| blob | f4977a65d2920c0127df5aa1e13c05c5bf32baa4 |
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) = @_;
364 }
368 ## Is the name passed in a known keyword for a project. This includes
369 ## keywords mapped by Define_Custom or Modify_Custom.
372 }
381 ## If it doesn't contain a path, search the include path
385 }
387 ## Read and parse the global project file
391 }
394 }
400 ## If the value we are going to set for $name has been used as a
401 ## scoped template variable, we need to hijack the whole assignment
402 ## and turn it into a template variable assignment.
406 }
407 }
413 ## Handle both recursive_includes and recursive_libpaths in one
414 ## search and replace.
416 ## This portion of code was lifted directly from Creator::relative()
417 ## but modified to always expand the variables. We will turn the
418 ## expanded values back into variables below and once they're passed
419 ## off to the assignment processing code, they will be turned into
420 ## relative values (if possible).
429 }
430 }
432 ## Create an array out of the recursive directory list. Convert all
433 ## of the relative or full path values back into $() values.
439 ## This directory doesn't exist, just add the original value
441 }
443 ## Create an array out of the directory list and add it to our
444 ## array.
447 }
448 }
450 ## We need to return a string, so we join it all together space
451 ## separated.
453 }
456 }
462 ## See if the name is one of the special "recursive" settings. If so,
463 ## fix up the value and change the name.
469 ## Support dependency attributes. They may or may not be used by
470 ## the project or workspace creator implementation. They are
471 ## stored separately from the dependencies themselves. Also, note
472 ## that a value to be added may contain more than one element to be
473 ## added. This function will be called for each one, so we only
474 ## need to handle one at a time.
476 ## The value may contain multiple projects. But, only one
477 ## dependency attribute will be present at any time. So, once we
478 ## get here, we need to remove any of the other projects from the
479 ## front of the key string.
484 }
486 ## Check the after value and warn the user in the event that it
487 ## contains a value that can not be used within a project name.
492 }
494 ## Support the '*' mechanism as in the project name, to allow
495 ## the user to correctly depend on another project within the same
496 ## directory.
500 }
502 }
503 ## Support the '*' mechanism for libs assignment as well.
506 }
508 ## If this particular project type does not consider the dollar sign
509 ## special and the user has provided two dollarsigns as an escape, we
510 ## will turn it into a single dollar sign.
513 }
515 ## If the assignment name is valid and requires parameter (<%...%>)
516 ## replacement, then do so. But, only do so on actual keywords.
517 ## User defined keywords must not have the parameters replaced in
518 ## order for them to get the correct replacement values later on.
522 }
523 }
527 }
529 ## Call the base process_assigment() after we have modified the name and
530 ## value.
533 ## Support keyword mapping here only at the project level scope. The
534 ## scoped keyword mapping is done through the parse_scoped_assignment()
535 ## method.
542 }
543 }
544 }
550 ## See if the name is one of the special "recursive" settings. If so,
551 ## fix up the value and change the name.
555 }
561 ## See if the name is one of the special "recursive" settings. If so,
562 ## fix up the value and change the name.
565 ## If the assignment name is valid and requires parameter (<%...%>)
566 ## replacement, then do so. But, only do so on actual keywords.
567 ## User defined keywords must not have the parameters replaced in
568 ## order for them to get the correct replacement values later on.
572 }
575 }
581 ## If there is a previous value ($nval) and the keyword is going to be
582 ## evaled, we need to separate the values with a command separator.
583 ## This has to be done at the MPC level because it isn't always
584 ## possible for the user to know if a value has already been added to
585 ## the keyword (prebuild, postbuild and postclean).
590 }
593 }
594 }
596 ## For an addition, we need to see if it is a project keyword being
597 ## used within a 'specific' section. If it is, we may need to update
598 ## scoped settings for that variable (which are in essence template
599 ## variables).
602 ## Next, we just give everything to the base class method.
604 }
610 ## For a subtraction, we need to see if it is a project keyword being
611 ## used within a 'specific' section. If it is, we may need to update
612 ## scoped settings for that variable (which are in essence template
613 ## variables).
616 ## Next, we just give everything to the base class method.
618 }
624 ## If we weren't passed an assignment hash, then we need to
625 ## look one up that may possibly correctly deal with keyword mappings
632 }
633 }
635 ## Get the assignment value
638 ## If we are involved in a subtraction, we get back a value and
639 ## it's a scoped or mapped assignment, then we need to possibly
640 ## expand any template variables. Otherwise, the subtractions
641 ## may not work correctly.
644 }
647 }
655 ## Deal with the inheritance hierarchy first
656 ## Add in the base projects from the command line
663 }
666 }
667 }
671 ## Read in the parent onto ourself
677 }
684 }
685 }
691 ## Push the base project file onto the parent stack
694 ## Collect up some information about the inheritance tree
698 }
703 }
705 ## Begin reading the parent
710 ## Take the base project file off of the parent stack
714 }
716 ## The base project has already been read. So, if
717 ## we are reading the original project (not a parent base
718 ## project), then the current base project is redundant.
726 }
727 }
728 }
729 }
733 }
734 }
735 }
737 ## Copy each value from global_assign into assign
742 }
743 }
744 }
747 }
761 }
764 }
765 }
769 }
770 }
773 }
779 ## First check for properties that correspond to the current project
780 ## type. Elements that begin with "prop:" indicate a property.
790 }
793 }
794 }
797 }
798 }
801 }
802 }
804 ## If none of the elements match a property, then check the type
805 ## against the current project type or the default component name
806 ## (which is what it would be set to if a specific clause is used with
807 ## out parenthesis).
812 ## Nothing matched
814 }
823 ## parse_known() passes back an array of values
824 ## that make up the contents of the line parsed.
825 ## The array can have 0 to 4 items. The first,
826 ## if defined, is always an identifier of some
827 ## sort.
834 ## Project Ending
837 ## Fill in all the default values
840 ## Perform any additions, subtractions
841 ## or overrides for the project values.
848 }
851 }
854 }
855 }
856 }
861 }
862 }
865 ## Generate default target names after all source files are added
866 ## and after we've added in all of the options from the
867 ## command line. If the user set exename on the command line
868 ## and no "main" is found, sharedname will be set too and
869 ## most templates do not handle that well.
872 ## End of project; Write out the file.
875 ## write_project() can return 0 for error, 1 for project
876 ## was written and 2 for project was skipped
878 ## Save the library name and location
887 }
890 }
895 }
900 }
902 }
903 }
905 ## Check for unused verbatim markers
911 }
912 }
913 }
914 }
915 }
917 ## Reset all of the project specific data. I am explicitly
918 ## not resetting dependency_attributes. It is necessary that
919 ## this information stay for the life of the ProjectCreator
920 ## object so that the WorkspaceCreator can have access to the
921 ## information.
925 }
929 }
942 }
943 }
945 }
947 ## Project Beginning
950 ## Set up the default project name
954 ## We should only set the project name if we are not
955 ## reading in a parent project.
961 ## Replace any *'s with the default name
966 }
969 }
973 }
974 }
979 }
980 }
981 }
983 ## Signify that we have a valid project
985 }
986 }
988 ## $values[1] = name; $values[2] = value
991 }
995 }
996 }
998 ## $values[1] = name; $values[2] = value
1001 }
1005 }
1006 }
1008 ## $values[1] = name; $values[2] = value
1011 }
1015 }
1016 }
1025 }
1029 }
1035 }
1043 {});
1044 }
1046 ## We still need to parse the scope, but we will be
1047 ## throwing away whatever is processed. However, it
1048 ## could still be invalid code that will cause an error.
1054 }
1055 }
1059 }
1062 }
1067 }
1071 }
1072 }
1073 }
1082 }
1083 }
1087 }
1088 }
1091 }
1094 }
1100 ## Map the assignment name on a scoped assignment
1104 }
1111 }
1114 }
1118 }
1120 ## If there is no value in $$flags, then we need to get
1121 ## the outer scope value and put it in there.
1125 }
1127 }
1129 ## If there is no value in $$flags, then we need to get
1130 ## the outer scope value and put it in there.
1134 }
1136 }
1138 }
1141 }
1149 ## Save the addtemp state if we haven't done so before
1153 }
1155 ## If the name that is used within a specific is a mapped keyword
1156 ## then we need to translate it into the mapped keyword as it will
1157 ## be used by the TemplateParser.
1165 }
1166 }
1168 ## Now modify the addtemp values
1176 ## Regardless of whether there was and assignment value, we need to
1177 ## look at the template value of the base so that modification of a
1178 ## scoped variable includes the base values.
1183 }
1184 }
1187 }
1188 }
1190 ## Subsitute all pseudo variables for the project specific characters.
1195 ## If there are template variable settings, then we need to add
1196 ## this new one to the end of the settings that did not come from
1197 ## the command line. That way, adjust_value() does not need to
1198 ## sort the values (and have knowledge about which came from the
1199 ## command line and which didn't).
1206 }
1207 }
1208 }
1211 }
1213 ## If the variable name is not scoped, we need to look through existing
1214 ## scoped variables that match the base. If we find one, we need to
1215 ## propagate this value into the scoped settings.
1224 }
1225 }
1226 }
1227 }
1228 }
1230 ## 0: (0 set, 1 add, -1 subtract)
1231 ## 1: The text value
1232 ## 2: (true set on command line, false set in project)
1233 ## 3: The original variable name if it's scoped or mapped
1235 }
1243 ## Unknown assignments within a 'specific' section are handled as
1244 ## template value modifications. These are handled exactly as the
1245 ## -value_template option in Options.pm.
1247 ## If $type is not defined, then we are skipping this section
1251 }
1260 }
1265 ## This is a special concession for Windows. It will not allow
1266 ## you to set an empty environment variable. If an empty
1267 ## double quoted string is found, we will assume that the user
1268 ## wanted an empty string.
1272 }
1273 }
1275 }
1276 }
1278 ## If the type is not defined, then this is something other than an
1279 ## assignment in a 'specific' section and should be flagged as an error
1281 }
1290 }
1291 }
1297 }
1307 ## If this returns true, then we've found an assignment
1312 }
1313 }
1315 ## If we successfully remove a '!' from the front, then
1316 ## the file(s) listed are to be excluded
1320 ## Convert any $(...) in this line before we process any
1321 ## wild card characters. If we do not, scoped assignments will
1322 ## not work nor will we get the correct wild carded file list.
1323 ## We also need to make sure that any back slashes are converted to
1324 ## slashes to ensure that later flag_overrides checks will happen
1325 ## correctly.
1329 ## Now look for specially listed files.
1330 ## Regular expressions are very slow. Searching the line twice with
1331 ## index() is 328 times faster than searching with just the regular
1332 ## expression when it doesn't match (which is likely to be the case).
1347 }
1349 ## Check for both possible error conditions
1353 }
1357 }
1359 ## Keys used internally to MPC need to be in forward slash format.
1365 }
1366 ## We can not convert slashes here as we do for dependencies
1367 ## (below). The files specified here need to retain the forward
1368 ## slashes as they are used elsewhere.
1370 }
1373 }
1374 }
1376 ## If there is a command helper, we need to add the output files
1377 ## here. It is possible that helper determined output files are
1378 ## the only files added by this component type.
1391 }
1392 }
1393 }
1395 ## Set up the files array. If the line contains a wild card
1396 ## character use CORE::glob() to get the files specified.
1400 }
1401 ## Don't glob the line if we're wanting to remove the file. Wait
1402 ## until later to do the wildcard expansion (in remove_excluded).
1405 }
1408 }
1410 ## If we want to remove these files at the end too, then
1411 ## add them to our remove_files hash array.
1415 }
1418 }
1419 }
1421 ## If we're excluding these files, then put them in the hash
1426 }
1428 ## Set the flag overrides for each file
1432 ## We are giving these flag overrides to multiple files. We must
1433 ## do so because these files are all in the same group.
1435 }
1436 }
1439 ## Add the file if we're not excluding it
1442 ## The user listed a file explicitly, whether we
1443 ## excluded it or not.
1445 }
1446 }
1447 }
1450 }
1465 }
1468 }
1471 }
1478 }
1479 }
1482 }
1499 ## For the custom scoped assignments, we want to put a copy of
1500 ## the original custom defined values in our flags associative array.
1504 }
1505 }
1506 }
1510 }
1513 }
1516 }
1519 }
1522 # preserve order
1523 #tie %$names, "Tie::IxHash";
1524 #tie %$comps, "Tie::IxHash";
1531 }
1537 }
1542 }
1543 }
1550 }
1553 ## The default components name was never used
1554 ## so we remove it from the components
1557 ## For custom_only projects, an empty section is functionally
1558 ## equivalent to not defining it at all.
1562 }
1564 ## It was used, so we need to add that name to
1565 ## the set of group names unless it's already been added.
1568 ## Define the defaulted section value so that if a following
1569 ## empty section of the same type is found, it will not cause the
1570 ## defaulted value to be overwritten.
1572 }
1576 }
1578 ## We are at the end of a component. If the only group
1579 ## we added was the default group, then we need to remove
1580 ## the group setting altogether.
1586 }
1587 }
1589 ## This is not an error,
1590 ## this is the end of the components
1592 }
1593 }
1600 }
1601 }
1603 ## If this is a "special" component, we need to see if the
1604 ## user provided all directories. If they have, then we need to
1605 ## store an array of directories that the user supplied. Otherwise,
1606 ## we just store a 1.
1615 }
1619 }
1620 }
1621 }
1622 }
1625 }
1628 }
1629 }
1631 ## If we didn't encounter an error, didn't have any files explicitly
1632 ## listed and we attempted to exclude files, then we need to find the
1633 ## set of files that don't match the excluded files and add them.
1645 }
1646 }
1654 }
1657 }
1665 }
1667 ## All types are lower case
1672 }
1674 ## Instead of always creating a new array for a particular type and
1675 ## location, create a new array if there isn't one already or the user
1676 ## does not want to add to the existing verbatim settings.
1684 ## This is not an error,
1685 ## this is the end of the verbatim
1688 }
1691 }
1705 }
1709 }
1710 }
1713 ## The required features are enabled, so we say that
1714 ## a project has been defined and we allow the parser to
1715 ## find the data held within the feature.
1720 }
1721 }
1723 ## Otherwise, we read in all the lines until we find the
1724 ## closing brace for the feature and it appears to the parser
1725 ## that nothing was defined.
1730 ## This is a very simplistic way of finding the end of
1731 ## the feature definition. It will work as long as no spurious
1732 ## open curly braces are counted.
1739 }
1740 }
1741 }
1744 }
1753 }
1754 }
1758 }
1766 }
1767 }
1768 }
1769 }
1770 }
1776 ## Make the tag something _files
1779 ## We can not have a custom type named "generic"
1785 }
1786 }
1789 }
1794 }
1798 }
1801 }
1803 }
1808 ## Update the custom_types assignment
1815 }
1823 }
1835 }
1836 }
1841 }
1842 }
1847 }
1855 ## Fix $opt spacing
1859 ## Set up the 'optional' hash table
1864 }
1868 }
1869 }
1874 }
1875 }
1876 }
1881 ## Propagate the custom defined values into the mapped values
1887 ## Bypass the process_assignment() defined in this class
1888 ## to avoid unwanted keyword mapping.
1890 }
1891 }
1893 ## Set some defaults (if they haven't already been set)
1896 }
1899 }
1902 }
1905 }
1908 }
1911 }
1914 }
1916 }
1919 ## If this returns true, then we've found an assignment
1922 ## The 'automatic' keyword has always contained two distinct
1923 ## functions. The first is to automatically add input files of
1924 ## the specified extension. And the second is to automatically
1925 ## add generated files to the right components. It has now been
1926 ## split into separate functionality and we map the 'automatic'
1927 ## keyword to the two new ones here.
1938 }
1942 }
1943 ## Try to convert the value into a relative path
1951 }
1956 }
1961 }
1962 }
1965 ## Transform the name from something outputext to
1966 ## something files. We expect this to match the
1967 ## names of valid_assignments.
1969 }
1971 ## Get it ready for regular expressions
1974 ## Split the value into an array using a comma as the
1975 ## separator. If there are no elements in the array we're
1976 ## going to add an empty element to the array. This way,
1977 ## assignments of blank values are useful.
1981 ## Process the array assignment after adjusting the values
1985 }
1986 }
1987 }
1993 }
1994 }
1996 ## $status is zero until the end of the define custom block, so
1997 ## we can't use it for this check.
1999 }
2001 ## Check for keyword mapping here
2009 }
2012 }
2016 }
2022 }
2023 }
2028 }
2029 }
2034 }
2035 }
2036 }
2039 }
2048 ## Get both of the relative value hash maps and put them in an array
2055 ## Go through each value and try to convert it to a variable setting
2057 ## Fix up the value, replacing '.' with the current working
2058 ## directory.
2063 }
2066 }
2069 ## Go through each relative value hash map and see if any of the
2070 ## values match the value that we're currently inspecting.
2074 ## Get the relative replacement value and convert back-slashes
2078 ## We only need to check for reverse replacement if the length
2079 ## of the value is greater than or equal to the length of our
2080 ## replacement value.
2083 ## Cut the string down by the length of the replacement value
2086 ## Check for equivalence, taking into account file system
2087 ## case-insenitivity.
2090 }
2093 }
2095 ## If they match, replace the value and save it in our array.
2100 }
2101 }
2102 }
2104 ## Once it's been found, there's no reason to continue on through
2105 ## the relative hash maps.
2107 }
2110 }
2113 }
2120 ## If we are modifying the libs, libpaths, macros or includes
2121 ## assignment with either addition or subtraction, we are going to
2122 ## perform a little fix on the value to avoid multiple
2123 ## libraries and to try to insure the correct linking order
2130 ## Convert the array into keys for a hash table
2133 ## In order to ensure that duplicates are correctly removed, we
2134 ## need to get the modified assignment value before we attempt to
2135 ## do so.
2139 ## We need to supply quotes if there is a space in the value or
2140 ## a variable. The variable may contain spaces.
2142 ## If we're going to add quotes around this item and the
2143 ## value ends in a backslash we need to append another
2144 ## backslash so that when it's used with
2145 ## StringProcessor::create_array() the function will not think
2146 ## that the trailing quote is escaped.
2149 }
2152 }
2153 }
2154 }
2157 }
2158 }
2161 }
2177 ## Check for the TemplateInputReader for the template key provided.
2182 }
2185 }
2186 }
2187 }
2190 ## Check for the TemplateInputReader for the template key provided.
2195 }
2198 }
2199 }
2200 }
2201 }
2205 ## Check for the TemplateInputReader for the template key provided.
2210 }
2213 }
2214 }
2215 }
2218 ## Check for the TemplateInputReader for the template key provided.
2223 }
2226 }
2227 }
2228 }
2229 }
2232 ## We have a TemplateInputReader for this template key, so we need
2233 ## to set the entry corresponding to $tikey to it for use in the
2234 ## get_template_input() method.
2236 }
2238 ## We haven't read this file yet, so we will create the template
2239 ## input reader and store it in the entry for the template key
2240 ## ($tkey) and the template input key ($tikey).
2245 ## Process the template input file
2250 }
2252 ## Not finding a template input file is only an error if the user
2253 ## specifically provided a template input file override.
2257 }
2258 }
2259 }
2261 ## Now that we've read in the template input file, set up our
2262 ## automatic template variables.
2266 }
2267 }
2269 ## We do this regardless of whether or not this parser is cached or
2270 ## not. If the features have changed (through a workspace cmdline
2271 ## setting), we need to reflect it.
2273 ## Put the features into the template input set
2277 }
2280 }
2287 ## This method expects that the file name will be unix style
2290 ## Remove the leading ./
2294 ## Take into account file system case-insenitivity.
2298 }
2304 }
2307 }
2318 }
2323 }
2331 }
2334 }
2335 }
2351 }
2353 ## We are coming into an '||', if status is already true
2354 ## then we can leave immediately
2359 }
2360 }
2363 }
2364 }
2367 }
2369 }
2373 }
2376 }
2377 }
2378 }
2381 }
2389 foreach my $opt (keys %{$self->{'generated_exts'}->{$gentype}->{'optional'}->{$tag}->{$name}}) {
2390 ## Get the name value
2394 ## Convert the value into a hash map for easy lookup
2398 ## See if the option or options are contained in the value. We
2399 ## need to call this even if $value is not defined due to the
2400 ## ability to negate optional parameters.
2402 ## Add the optional portion
2403 push(@$array, @{$self->{'generated_exts'}->{$gentype}->{'optional'}->{$tag}->{$name}->{$opt}});
2404 }
2405 }
2406 }
2407 }
2408 }
2414 ## Get the general pre extension array.
2415 ## $self->{'generated_exts'}->{$gentype}->{$keyword} is guaranteed to
2416 ## be defined due to the defaulting that is done in
2417 ## parse_define_custom() and the only three calls to this method use
2418 ## valid $keyword values.
2421 ## Add the component specific pre extension array
2426 }
2428 ## Add in any optional portion to the array
2432 }
2434 ## If the current array only has the default,
2435 ## then we need to remove it
2439 }
2441 }
2444 }
2463 }
2464 }
2465 }
2467 ## If gendir was specified, then we need to account for that
2475 }
2479 }
2480 }
2481 }
2482 }
2486 }
2489 }
2490 }
2491 }
2492 }
2493 }
2497 ## $part - The full path of the input file minus the extension
2498 ## $type - The input file type (e.g., 'java_files')
2499 ## $file - The full path of the input file
2500 ## $noext - bool indicating an inverse need for an extension
2501 ## $arrs - bool indicating that the return array should be made of arrays
2503 ## A custom type is not allowed to generate it's own input files
2506 ## See if the type for which we are generating ($tag) is also a custom
2507 ## file type. If it is, we need to do some massaging.
2510 ## If the custom type ($type) doesn't specify that it generates
2511 ## generic files, we need to see if there is a command helper for
2512 ## this type and see what sort of output it knows about.
2517 }
2519 ## We will need to use 'generic_files' instead of $tag if $tag is
2520 ## defined in 'generated_exts', but only for the type that will
2521 ## actually generate the right type of generic file.
2532 }
2533 }
2535 }
2536 }
2538 ## If we were not able to find the right file type, then we can get
2539 ## out early. However, if the type for which we are generating
2540 ## ($tag) is a built-in type, we need to continue on as there is a
2541 ## possibility that the input type ($type) will generate files for
2542 ## the generating type.
2545 }
2561 }
2562 }
2567 ## If both arrays are defined to be the defaults, then there
2568 ## is nothing for us to do.
2569 }
2574 ## Correctly deal with pre filename and directories
2576 ## Split the directory and base name of the file. Only set the
2577 ## directory if the output follows the input directory.
2581 }
2584 }
2586 ## If gendir was specified, then we need to account for that
2592 }
2596 }
2597 }
2599 ## Loop through creating all of the possible file names
2608 }
2613 }
2614 }
2615 }
2616 }
2619 }
2622 }
2623 }
2624 }
2626 ## Now add the explicit output. We need to use the original tag value
2627 ## ($otag) so that we can find the custom output files.
2630 }
2636 ## This method is called by list_default_generated. It performs the
2637 ## actual file insertion and grouping.
2638 ## Get the generated filenames
2644 }
2645 }
2650 ## Get all files in one list and save the directory
2651 ## and component group in a hashed array.
2659 }
2660 }
2661 }
2663 ## Create a small array of only the files we want to add.
2664 ## We put them all together so we can keep them in order when
2665 ## we put them at the front of the main file list.
2669 }
2671 ## If we have files to add, make sure we add them to a group
2672 ## that has the same directory location as the files we're adding.
2680 }
2682 ## If this component name does not match the component name for
2683 ## which we are adding files and there are components defined
2684 ## for it, we will look to see if we can find a matching group
2685 ## name. We have to make sure that we do not use the hash map
2686 ## ($self->{$vc}) unless it's defined. Doing so will
2687 ## automatically create the map and that will cause MPC to
2688 ## think that the user provided the empty setting (when it
2689 ## wasn't).
2698 }
2702 }
2703 }
2704 }
2706 }
2707 }
2709 }
2710 }
2712 }
2719 }
2722 }
2724 }
2725 }
2726 }
2727 }
2740 ## Remove c++ style comments
2743 ## Remove one line c style comments
2748 ## Found the end of a multi-line c style comment
2750 }
2751 }
2754 ## Found the beginning of a multi-line c style comment
2756 }
2758 ## If the current language supports a c preprocessor, we
2759 ## will perform a minimal check for #if 0
2761 ## Found the beginning of a #if 0
2763 }
2766 ## We need to keep track of any other #if directives
2767 ## to be sure that when we see an #endif we don't
2768 ## count the wrong one.
2770 }
2772 ## Found a #endif, so decrement our count
2774 }
2775 }
2776 }
2777 }
2779 ## Check for main; Make sure it's not #if 0'ed and not commented out
2784 ## If we've found a main, set the exename to the basename
2785 ## of the cpp file with the extension removed
2790 }
2792 }
2793 }
2794 }
2796 }
2798 }
2807 ## If additional main's have been supplied by the user for this
2808 ## language type, then just push them onto the array.
2811 ## Now search each source file until we've found a main function.
2815 }
2818 }
2824 ## If this is a custom_only project, we need not waste time setting the
2825 ## sharedname, staticname or exename. Searching all of the files for a
2826 ## main function is very time consuming and unnecessary.
2839 }
2843 }
2844 }
2848 }
2850 ## If it's neither an exe or library target, we will search
2851 ## through the source files for a main()
2853 ## Set the exename assignment
2858 ## If we still don't have a project type, then we will
2859 ## default to a library if there are source or resource files
2863 }
2868 }
2871 }
2872 }
2873 }
2874 }
2876 ## If we are generating only static projects, then we need to
2877 ## unset the sharedname, so that we can insure that projects of
2878 ## various types only generate static targets.
2883 }
2884 }
2886 ## Check for the use of an asterisk in the name
2893 }
2894 }
2895 }
2910 ## If the file doesn't even contain _pch, then there's no point
2911 ## in looping through all of the extensions
2920 }
2921 }
2922 }
2930 }
2931 }
2932 }
2933 }
2934 }
2937 }
2940 }
2941 }
2942 }
2948 ## Unset the precompiled header settings if they are set but empty
2952 }
2953 }
2965 ## If we are converting slashes, then we need to
2966 ## convert the pch file back to forward slashes
2969 ## Find out which files are duplicated
2980 }
2981 }
2982 }
2983 }
2984 }
2985 }
2986 }
2994 ## The special actions taken based on $saverc only applies to
2995 ## C++ resource files.
3001 ## Always exclude the precompiled header and cpp
3010 }
3011 }
3013 }
3015 ## Save these files for later. There may
3016 ## be more than one and we want to try and
3017 ## find the one that corresponds to this project
3020 }
3023 }
3024 }
3025 }
3027 ## Now deal with the saved files
3030 ## Theres only one rc file, take it
3032 }
3037 ## Use a case insensitive search.
3038 ## After all, this is a Windows specific file type.
3043 }
3044 }
3045 }
3046 }
3047 }
3048 }
3060 }
3069 ## If we are not automatically adding generated output, then we
3070 ## need to skip this component type.
3073 ## If we are auto-generating the source_files, then
3074 ## we need to make sure that any generated source
3075 ## files that are added are put at the front of the list.
3079 ## If I call keys %{$self->{$gentype}} using perl 5.6.1
3080 ## it returns nothing. I have to put it in an
3081 ## intermediate variable to ensure that I get the keys.
3087 }
3088 }
3108 ## No need to check for previously added files
3109 ## here since there are none.
3114 }
3115 }
3117 }
3119 ## The first file listed in @files is the preferred
3120 ## extension for the custom command. Take the first
3121 ## file extension and see if it matches one in the accepted
3122 ## extensions.
3127 }
3129 ## If it doesn't match one of the accepted extensions,
3130 ## then just use the first extension from the type for
3131 ## which we are generating.
3133 }
3135 ## Add all the files that match the chosen extension
3138 }
3139 }
3140 }
3141 }
3146 }
3147 }
3148 }
3150 ## No need to check for previously added files
3151 ## here since there are none.
3155 }
3156 }
3161 }
3164 }
3167 }
3169 }
3172 }
3173 }
3174 }
3175 }
3176 }
3177 }
3193 ## The order of @tags does make a difference in the way that generated
3194 ## files get added. Hence the sort call on the generate_exts keys to
3195 ## ensure that user defined types come first. They are reverse sorted
3196 ## using the custom sort function to ensure that user defined types
3197 ## that rely on other user defined types for input files are processed
3198 ## first.
3205 ## If the tag is defined, then process directories
3213 }
3223 ## Since the file was actually a directory, we will
3224 ## need to propagate the flag overrides (if there are
3225 ## any) to the newly located files.
3230 }
3231 }
3233 ## Always push the @portion array onto the back of
3234 ## @built.
3236 }
3241 }
3242 }
3243 }
3247 }
3249 }
3250 }
3251 }
3252 }
3254 ## Generate default values for undefined tags
3266 }
3267 }
3269 ## If the type that we're generating defaults for ($tag) is a
3270 ## custom type, then we need to see if other custom types
3271 ## ($gentype) will generate files that will be used as input. It
3272 ## has to be done here so that the built-in types will have all
3273 ## of the possible input files that they can.
3278 }
3279 }
3281 ## Now that we have the files for this type ($tag), we need to
3282 ## locate a command helper for the custom command and see if it
3283 ## knows about any additional output files based on the file
3284 ## name.
3303 }
3304 }
3305 }
3306 }
3307 }
3308 }
3309 }
3310 }
3311 }
3312 }
3313 }
3320 ## There's no point in going on if there's nothing in this component
3321 ## list.
3324 ## Convert the array into keys for a hash table
3328 ## Find out which source files are listed
3335 ## Is the source file in the component array?
3337 ## Remove the element and fix the index and count
3341 }
3342 }
3343 }
3344 }
3345 }
3352 ## Find out which generated source files are listed
3362 }
3363 }
3364 }
3365 }
3366 }
3369 }
3375 ## This method is called when the user has custom input files and has
3376 ## provided source files. If the user defaults the component (i.e.
3377 ## source_files, resource_files, etc.) they are filled in by the
3378 ## generate_default_components method.
3382 ## After all source and headers have been defaulted, see if we
3383 ## need to add the generated files
3385 ## Build up the list of files
3387 #tie %arr, "Tie::IxHash"; # preserve insertion order.
3395 ## Take the last group name we encounter
3402 }
3403 }
3404 }
3407 ## Only add generated files if the following is true:
3408 ## 1) The generating type is not the same as the receiving type.
3409 ## 2) The receiving type is not "special" (unless it hasn't been
3410 ## supplied by the user).
3411 ## 3) The receiving type is not user defined or it is user
3412 ## defined and has 'automatic_in' set to true.
3423 }
3424 }
3425 }
3426 }
3427 }
3428 }
3443 }
3450 ## Convert the file to unix style for basename
3454 }
3456 }
3457 }
3458 }
3459 }
3462 }
3469 ## Go through each file listed in our original type and attempt to find
3470 ## out if it is the generated file we may need to add ($file).
3474 ## Take the file and see if it contains an extension that our
3475 ## generating type ($gentype) knows about. If it does, remove it and
3476 ## stop looking for the extension.
3478 ## Remove the extension.
3479 ## If it works, then we can exit this loop.
3481 }
3483 ## If the user provided file does not match any of the
3484 ## extensions specified by the custom definition, we need
3485 ## to remove the extension or else this file will not be
3486 ## added to the project.
3489 ## See if we need to add the file. We always need to check since the
3490 ## output file may have absolutely nothing in common with the input
3491 ## file.
3494 ## $gen is a file that has a custom definition that generates
3495 ## files of the type $tag. The $file passed in is of type
3496 ## $gentype and, as far as I can tell, $created will always be
3497 ## longer or of the same length of $file. It doesn't really
3498 ## matter if $file contains a '.' or not.
3502 }
3506 }
3508 }
3509 }
3510 }
3513 }
3520 ## Create a hash array keyed off of the existing files of the type
3521 ## that we plan on adding.
3526 ## Check to see if files exist in the default group
3530 }
3533 }
3534 }
3536 ## Create an array of extensions for the files we want to add
3541 }
3543 ## Check each file against a possible new file addition
3552 }
3553 }
3556 ## Get the array of files for the selected component name
3562 }
3563 }
3565 ## First, see if it will be generated so that we can correctly
3566 ## deal with 'gendir' settings.
3569 }
3571 ## Next check to see if the file exists
3579 }
3581 }
3582 }
3583 }
3585 ## If we have any files at all in the component array, check
3586 ## to see if we need to add a new group name
3590 }
3596 }
3599 }
3601 ## Put the array back into the component list
3605 }
3606 }
3607 }
3608 }
3609 }
3611 ## We only need to add the default group name if we wanted to
3612 ## add the default group when adding new files and we added a group
3613 ## by some other name. Otherwise, defaulted files would always be
3614 ## in a group, which is not what we want.
3617 }
3618 }
3627 }
3629 ## Since files on UNIX can have back slashes, we transform them
3630 ## into underscores.
3633 ## Convert the name to a usable name
3636 ## Take off the extension
3638 }
3641 }
3648 ## Process each file type and remove the excluded files
3660 }
3662 ## The file does not match exactly with one of the files to
3663 ## remove. Look for wildcard specifications in the files to
3664 ## be removed and perform the removal if one of them matches
3665 ## the current file.
3677 }
3678 }
3679 }
3680 }
3681 }
3682 }
3683 }
3685 }
3686 }
3690 ## We need to sort the custom component types such that a custom type
3691 ## that generates input for another custom type comes first in the
3692 ## list.
3701 }
3702 }
3703 }
3704 }
3707 }
3710 }
3715 ## Generate default project name
3718 }
3720 ## Generate the default pch file names (if needed)
3726 ## If the pch file names are empty strings then we need to fix that
3729 ## Generate default components, but %specialComponents
3730 ## are skipped in the initial default components generation
3733 ## Remove source files that are also listed in the template files
3734 ## If we do not do this, then generated projects can be invalid.
3737 ## If pch files are listed in header_files or source_files more than
3738 ## once, we need to remove the extras
3741 ## Generate the default generated list of files only if we defaulted
3742 ## the generated file list. I want to ensure that source_files comes
3743 ## first in the list to pick up group information (since source_files
3744 ## are most likely going to be grouped than anything else).
3752 }
3754 ## Now that all of the source files have been added
3755 ## we need to remove those that have need to be removed
3758 ## Collect up all of the source files that have already been listed
3759 ## with the extension removed for use directly below.
3769 }
3770 }
3771 }
3772 }
3774 ## Add %specialComponents files based on the
3775 ## source_components (i.e. .h and .i or .inl based on .cpp)
3778 }
3780 ## Now, if the %specialComponents are still empty
3781 ## then take any file that matches the components extension
3787 ## We only want to generate default components if we have
3788 ## defaulted the source files or we have no files listed
3789 ## in the current special component.
3796 }
3797 }
3799 }
3801 ## If the "special" type was supplied and it was all
3802 ## directories, we need to use those directories to generate
3803 ## the default components instead of the current directory.
3812 }
3814 }
3816 }
3817 }
3818 }
3819 }
3821 ## The code to add template files automatically when it is left
3822 ## defaulted by the user may add source files that happen to end in _t
3823 ## (minus the extension). If we do not remove template files that are
3824 ## also listed as source files, the generated projects can be invalid.
3827 ## Now that all of the other files have been added
3828 ## we need to remove those that have need to be removed
3832 ## Tie custom files together if need be. This currently only applies
3833 ## to types with command helpers. At some point, if it is found to be
3834 ## desirous, we could extend the MPC syntax somehow to support this
3835 ## sort of thing manually.
3840 ## There has to be at least two files files in order for
3841 ## something to be tied together.
3849 ## We have a tied file, now we need to actually perform
3850 ## the tieing of the two. We will do this by saying that
3851 ## the output of the original is necessary for the
3852 ## processing of the tied file.
3859 }
3860 }
3864 ## We have found a set of files that are generated
3865 ## based on the component type of the original file
3866 ## ($gentype), so we just add the first one and
3867 ## we're done.
3871 ## We are about to modify the flag overrides for a tied file.
3872 ## We need to make a copy so that we do not affect the
3873 ## overrides of grouped, but no longer affiliated files.
3878 ## Start a new dependent setting based on the original
3879 ## custom build settings.
3882 }
3887 ## We are about to modify the flag overrides for a tied file.
3888 ## We need to make a copy so that we do not affect the
3889 ## overrides of grouped, but no longer affiliated files.
3893 }
3895 ## Update the dependent value for this tied file.
3897 }
3898 }
3899 }
3900 }
3901 }
3902 }
3903 }
3909 ## Save the unmodified project name so that when we
3910 ## need to determine the default target name, we can use
3911 ## what is expected by the user.
3914 ## If we are applying the name modifier to the project
3915 ## then we will modify the project name
3922 }
3923 }
3925 ## Set the project_name assignment so that the TemplateParser
3926 ## can get the project name.
3928 }
3933 }
3940 }
3945 }
3956 }
3957 }
3959 ## By default, if 'convert_slashes' is true, then we convert slashes
3960 ## to backslashes. There are cases where we do not want to convert
3961 ## the slashes, in that case get_component_list() was called with
3962 ## an additional parameter indicating this.
3966 }
3967 }
3971 }
3974 }
3987 }
3993 }
3999 ## We only match if the built file name matches from
4000 ## beginning to end or from a slash to the end.
4004 }
4005 }
4006 }
4007 }
4008 }
4011 }
4021 ## These names (held in $type) are variables that contain various
4022 ## commands that will be used in templates within the context of a
4023 ## foreach (e.g., <%custom_type->input_files%> or <%feature->value%>).
4026 }
4029 }
4032 }
4037 }
4042 }
4043 }
4044 }
4048 ## If the passed in type is not a builtin type, try the type with an
4049 ## 's' on the end.
4052 ## This is a hack for dealing with the fact that built-in types
4053 ## (e.g., Source_Files, Header_Files, etc.) are not real custom
4054 ## definitions. However, we can "modify" them to some extent.
4057 }
4060 }
4070 }
4071 }
4074 }
4081 ## Make it all lower case
4084 ## Remove the grouped_ part
4087 ## Add the s if it isn't there
4100 }
4102 }
4105 }
4109 }
4110 }
4111 }
4112 }
4114 ## If there is more than one name, then we will need
4115 ## to deal with that at a later time.
4118 }
4119 }
4122 }
4128 ## If the passed in type does not have a generated_exts definition,
4129 ## then try the type with an 's' on the end.
4132 ## If we have a builtin type that has the variable ($cmd) that we are
4133 ## looking for, process the value through command parameter conversion.
4139 }
4141 ## Otherwise, there's nothing here.
4143 }
4149 ## Add the built-in OS compatibility commands
4166 }
4182 }
4184 ## Add the project specific compatibility commands
4197 }
4213 }
4215 ## Support both pseudo variables and project settings
4217 ## If the pseudo variable is defined or the project setting has a
4218 ## value, then we'll need to do the replacement. However, if it's
4219 ## a project keyword and it's not defined, we will need to delay
4220 ## the replacement until later (unless $always_clear is true).
4225 }
4228 }
4230 ## Perform the modification and replacement here
4235 }
4238 }
4239 }
4241 }
4243 ## We need to clear out this variable usage.
4245 }
4247 ## Save this variable usage to be put back after we're done
4248 ## processing the string.
4252 }
4253 }
4254 }
4258 ## We only want to warn the user that we did not recognize the
4259 ## pseudo template parameter if there was an input and an output
4260 ## file passed to this function. If this variable was used
4261 ## without the parenthesis (as in an if statement), then we don't
4262 ## want to warn the user.
4266 }
4268 ## If we didn't recognize the pseudo template parameter then
4269 ## we don't want to return anything back.
4271 }
4272 }
4273 }
4275 ## Replace the saved variables so that they may be replaced (or
4276 ## removed) later on.
4279 }
4281 }
4289 ## Add in the values that change for every call to this function
4298 ## An input file doesn't always have an extension. If there isn't
4299 ## one, then we need to set the 'input_ext' field to an empty string
4300 ## ($1 will not necessarily have a valid value).
4303 }
4306 }
4308 ## Check for the gendir setting associated with this input file. We
4309 ## have to check at so many levels so we don't inadvertantly create
4310 ## intermediate hash tables.
4315 }
4316 }
4318 ## If there is no gendir setting, just set it to the current directory.
4325 ## An output file doesn't always have an extension. If there isn't
4326 ## one, then we need to set the 'output_ext' field to an empty
4327 ## string ($1 will not necessarily have a valid value).
4331 }
4334 }
4337 ## In order to call basename or dirname, we must make sure that the
4338 ## directory separators are forward slashes.
4346 }
4347 }
4349 ## Add in the specific types of output files
4363 }
4364 }
4365 }
4366 }
4367 }
4370 }
4384 }
4386 }
4397 }
4402 ## Remove the extension
4405 ## If we are converting slashes,
4406 ## change them back for this parameter
4413 }
4420 }
4437 }
4440 }
4441 }
4445 }
4448 }
4452 }
4454 }
4465 ## Get the component list for the component type
4468 ## Check for directories in the component list. If the component
4469 ## type is not automatic, we may have directories here and will need
4470 ## to get the file list for that type.
4478 };
4479 }
4487 }
4488 }
4499 }
4507 ## Remove the extension
4510 ## If we are converting slashes,
4511 ## change them back for this parameter
4524 }
4525 }
4526 }
4530 }
4532 ## Add all of the output files. We can not add $generic_key to the
4533 ## list here (as it used to be). It may have been handled by
4534 ## generated_filenames.
4536 ## The output of multiple components could be input for the
4537 ## current component type ($based). We need to avoid adding
4538 ## duplicates here.
4544 }
4545 }
4550 }
4551 }
4558 }
4559 }
4565 }
4567 ## Add specially listed files avoiding duplicates. We don't want
4568 ## to add these files if gendir is set to something besides .
4574 }
4575 }
4580 }
4585 }
4586 }
4589 }
4591 }
4592 }
4594 # Generate output files based on $based
4597 }
4598 }
4600 # Generate source output files based on $based
4606 ## We've found a file that matches one of the source file
4607 ## extensions. Now we have to make sure that it doesn't
4608 ## match a template file extension.
4614 }
4615 }
4618 }
4619 }
4620 }
4621 }
4622 }
4624 # Generate non source output files based on $based
4632 ## We've found a file that matches one of the source file
4633 ## extensions. Now we have to make sure that it doesn't
4634 ## match a template file extension.
4639 }
4640 }
4642 }
4643 }
4645 }
4646 }
4647 }
4649 # Generate non-template output files based on $based
4658 }
4659 }
4661 }
4662 }
4663 }
4668 }
4670 }
4673 }
4687 }
4689 # only 1 output file is supported with output_option
4696 }
4699 }
4702 }
4703 }
4704 }
4705 }
4708 # only used with 'combined_custom'
4710 }
4716 }
4717 }
4720 }
4732 ## By default, if the feature is not listed, then it is enabled.
4737 }
4739 ## For automakes sake, if we're to this point the feature is
4740 ## enabled and we will set it in the feature parser explicitly
4743 }
4744 }
4745 }
4747 ## If it passes the requires, then check the avoids
4753 ## By default, if the feature is not listed, then it is enabled.
4758 }
4759 }
4760 }
4761 }
4766 }
4769 }
4776 ## We always write a project if the user has provided a verbatim.
4777 ## We have no idea what that verbatim clause does, so we need to just
4778 ## do what the user tells us to do.
4781 ## The order here is important, we must check for source or resource
4782 ## files first and then for custom input files.
4785 ## For implicitly-discovered projects, just having a resource file without
4786 ## source or generated file is not enough to write a project.
4791 ## See if the project contains a file that corresponds to this
4792 ## component name.
4795 ## Return 2 if we have found a custom input file (and thus no
4796 ## source or resource files due to the foreach order).
4798 }
4799 ## We have either source files or resource files, we need to
4800 ## see if this project creator supports the current language.
4801 ## If it doesn't then we don't need to create the project.
4803 ## Return 1 if we have found a source file or a resource file.
4805 }
4806 }
4807 }
4808 }
4810 }
4812 ## Indicate that there is no need to write the project
4814 }
4824 ## The template override will override all templates
4828 ## Save the template name for use as a key for various function calls
4831 ## Create the output file name based on the project name and the
4832 ## template that we're currently using.
4837 ## If the template files does not end in the template extension
4838 ## then we will add it on.
4841 }
4843 ## If the template file does not contain a path, then we
4844 ## will search through the include paths for it.
4848 }
4851 }
4854 ## Read in the template values for the specific target and project
4855 ## type. The template input file we get may depend upon the
4856 ## current template that we're using.
4863 ## Set the project_file assignment for the template parser
4878 }
4881 }
4884 }
4885 }
4899 ## At this point in time, webapps do not get a project file,
4900 ## but they do appear in the workspace
4901 }
4903 ## First write the output to a temporary file
4910 }
4914 }
4919 }
4921 ## If they are different, then rename the temporary file
4929 }
4930 }
4935 }
4936 }
4938 ## We will pretend that we wrote the file
4940 }
4941 }
4947 }
4953 }
4954 }
4959 }
4960 }
4962 ## There may be more than one template associated with this
4963 ## project creator. If there is, we can only add one generated
4964 ## file and we rely on the project creator to tell us which
4965 ## template generates the file that we need to track.
4968 }
4969 }
4974 }
4975 }
4977 }
4995 }
4997 }
5016 }
5019 }
5020 }
5022 }
5023 }
5024 }
5025 }
5031 }
5042 }
5047 }
5048 }
5049 }
5068 }
5070 ## A return value of 2 from need_to_write_project() indicates
5071 ## that the only reason that we need to write the project is that
5072 ## there are custom input files (i.e., no source or resource
5073 ## files).
5078 }
5086 }
5087 }
5094 }
5095 }
5096 }
5097 }
5098 }
5100 ## Hook for implementing type-specific behavior.
5104 }
5105 ## We don't need to pass a file name here. write_output_file()
5106 ## will determine the file name for itself.
5109 ## Write the .ins file if the user requested it and we were
5110 ## successful.
5113 }
5114 }
5115 }
5122 }
5125 }
5126 }
5127 }
5130 }
5135 }
5144 # if we are a worker, we need to strip leading 'number|'
5149 }
5151 }
5154 }
5155 }
5160 }
5172 }
5178 }
5179 }
5186 ## Build up an array of extensions. Since they are stored as regular
5187 ## expressions, we need to remove the escaped period to provide the
5188 ## minimal amount of text for each extension to provide maximum
5189 ## flexibility within the project template.
5193 }
5194 }
5196 }
5202 }
5208 ## Only put data structures that need to be cleared
5209 ## out when the mpc file is done being read, not at the
5210 ## end of each project within the mpc file. Those go in
5211 ## the closing curly brace section of parse_line().
5215 }
5226 }
5227 }
5240 );
5246 }
5247 }
5252 ## Allow subclasses to override the default extensions
5254 }
5261 ## This follows along the same logic as read_template_input() by
5262 ## checking for exe target and then defaulting to a lib target
5266 }
5269 }
5270 }
5274 }
5277 }
5285 ## Append the values of all names into one string
5292 }
5294 ## There may be more than one template associated with this project
5295 ## creator. If there is, we can only add one generated file and we
5296 ## rely on the project creator to tell us which template generates the
5297 ## file that we need to track.
5299 ## If we already have an array, take the one off the top. Otherwise,
5300 ## create a new one which will be added below.
5304 ## Set up the hash table when we are starting a new project_info
5307 ## If we haven't seen this value yet, put it on the array
5311 }
5313 ## Always push the array back onto the project_info
5315 }
5318 }
5326 ## This will use the keys left in @_ as indices into the project
5327 ## info array. But, if the user wants configurations, we need to
5328 ## pop that key off and access it along with all the rest of the
5329 ## elements in the array. The CONFIGURATIONS key should always
5330 ## be last if it's included at all. If it's not, the caller will
5331 ## only receive the first configuration instead of all of them.
5336 }
5339 }
5346 ## Perform any additions, subtractions
5347 ## or overrides for the template values.
5354 ## If the template variable is a complex name, then we need to make
5355 ## sure that the mapped value belongs to the correct type based on
5356 ## the base of the complex name. The $tp (TemplateParser) variable
5357 ## will, in the majority of all calls to this method, be defined so
5358 ## it is checked second to avoid checking it if the name isn't
5359 ## complex.
5369 }
5371 }
5372 }
5374 }
5375 }
5383 }
5388 }
5390 ## Avoid adding duplicates. If the existing array contains
5391 ## the value already, remove it from the newly created array.
5396 }
5397 }
5399 ## We need to make $value a new array reference ($arr)
5400 ## to avoid modifying the array reference pointed to by $value
5403 }
5406 }
5407 }
5413 }
5416 }
5422 }
5423 }
5424 }
5425 }
5427 ## If the user set the variable to empty, then we need to
5428 ## set the value to undef
5430 }
5431 }
5433 }
5434 }
5437 }
5451 }
5455 }
5456 }
5457 }
5460 }
5468 }
5475 ## We don't apply the name modifier to the project file
5476 ## name if we have already applied it to the project name
5477 ## since the project file name comes from the project name.
5481 }
5483 }
5488 }
5493 }
5500 ## Only return the value stored in the valid_names hash map if it's
5501 ## defined and it's not an array reference. The array reference is
5502 ## a keyword mapping and all mapped keywords should have preserved
5503 ## assignment order.
5506 }
5509 }
5516 ## Only return the value stored in the valid_names hash map if it's
5517 ## defined and it's not an array reference. The array reference is
5518 ## a keyword mapping and no mapped keywords should be added to
5519 ## template input variables.
5522 }
5525 }
5529 #my $self = shift;
5531 }
5548 }
5549 }
5552 }
5554 }
5555 }
5557 }
5561 #my $self = shift;
5562 #my $name = shift;
5564 }
5570 ## Fill in the name if one wasn't provided
5573 ## Apply the transformation so that any name modifiers are utilized.
5578 }
5584 ## Remove any files that may have automatically been added
5585 ## to this project. If they were explicitly added, then we
5586 ## will leave them in the project.
5590 }
5591 }
5593 ## Unset the exename, sharedname and staticname
5597 }
5605 }
5607 ## If the user provided file does not match any of the
5608 ## extensions specified by the custom definition, we need
5609 ## to remove the extension or else this file will not be
5610 ## added to the project.
5613 }
5620 }
5623 }
5625 }
5627 }
5640 }
5651 }
5654 }
5664 ## Create a new feature parser. This relies on the fact that
5665 ## 'features' is restored first in restore_state().
5669 }
5670 }
5678 ## Clear out the template input reader that we're currently set
5679 ## to use.
5681 }
5682 }
5683 }
5685 ## If the user has changed the 'features' setting, then we need to
5686 ## make sure that we create a new feature parser regardless of
5687 ## whether or not the feature file has changed.
5689 }
5693 }
5694 }
5695 }
5700 }
5705 ## See if a language was supplied.
5707 ## If the language supplied is not one that we know about, return an
5708 ## error message.
5711 ## Otherwise, add it to the list for the language.
5713 }
5715 ## No language was supplied, so add the main to all of the languages
5716 ## that we support.
5719 }
5720 }
5722 ## Return no error message.
5724 }
5730 ## Not all entries in the %language map have a resource tag.
5731 ## For this, we will just return the tag for C++ since it probably
5732 ## doesn't really matter anyway.
5734 }
5739 ## No tag results in no command helper
5742 ## See if we have a command helper for this tag
5745 ## Give the command helper a reference to the creator. The helper
5746 ## can benefit from many of the infrastructure functions available.
5749 }
5751 ## None for the base define custom, try again with the parent
5753 }
5756 ## Return the dependency attribute specified as the first parameter to
5757 ## this method (not counting the ProjectCreator object).
5759 }
5762 #my($self, $name) = @_;
5764 }
5767 sub append_flag_override {
5779 }
5782 # Some project types can't represent the same input file being used by
5783 # more than one custom type. This function will look for such cases and
5784 # combine them into a single invocation of a synthetic custom type that
5785 # inherits properties from both of them.
5786 # Project types needing this transformation should call this function from
5787 # their overridden pre_write_output_file() method.
5788 sub combine_custom_types {
5811 }
5812 }
5813 }
5814 }
5815 }
5816 }
5818 # For each input file used in multiple custom types, move it into the new
5819 # synthetic type.
5823 . '_files';
5836 }
5837 }
5842 }
5847 }
5849 # Add to new type -- groups aren't relevant here, so just use the default
5852 # Remove from existing types
5860 }
5861 }
5862 }
5863 }
5867 }
5873 }
5874 }
5876 # If all existing uses agree to recurse, the new type should recurse too
5879 }
5881 }
5883 return 1;
5884 }
5887 # ************************************************************
5888 # Accessors used by support scripts
5889 # ************************************************************
5891 sub getKeywords {
5893 }
5895 sub getValidComponents {
5898 }
5900 # ************************************************************
5901 # Virtual Methods To Be Overridden
5902 # ************************************************************
5904 sub get_builtin_output {
5906 return [];
5907 }
5909 sub languageSupported {
5912 }
5914 sub file_visible {
5916 return 1;
5917 }
5919 sub webapp_supported {
5921 return 0;
5922 }
5925 sub use_win_compatibility_commands {
5928 }
5931 sub post_file_creation {
5934 return undef;
5935 }
5938 sub escape_spaces {
5940 return 0;
5941 }
5944 sub validated_directory {
5947 }
5949 sub get_quote_symbol {
5952 }
5954 sub get_escaped_quote_symbol {
5957 }
5959 sub get_gt_symbol {
5962 }
5965 sub get_lt_symbol {
5968 }
5971 sub get_and_symbol {
5974 }
5977 sub get_or_symbol {
5980 }
5983 sub get_cmdsep_symbol {
5986 }
5989 sub dollar_special {
5991 return 0;
5992 }
5995 sub expand_variables_from_template_values {
5997 return 1;
5998 }
6001 sub require_dependencies {
6003 return 1;
6004 }
6007 sub dependency_is_filename {
6009 return 1;
6010 }
6013 sub fill_value {
6016 return undef;
6017 }
6020 sub project_file_prefix {
6023 }
6026 sub project_file_extension {
6029 }
6032 sub override_valid_component_extensions {
6035 return undef;
6036 }
6039 sub override_exclude_component_extensions {
6042 return undef;
6043 }
6046 sub get_dll_exe_template_input_file {
6048 return undef;
6049 }
6052 sub get_lib_exe_template_input_file {
6055 }
6058 sub get_lib_template_input_file {
6061 }
6064 sub get_dll_template_input_file {
6066 return undef;
6067 }
6070 sub get_template {
6072 }
6074 sub requires_forward_slashes {
6075 return 0;
6076 }
6078 sub warn_useless_project {
6079 return 1;
6080 }
6082 sub pre_write_output_file {
6083 return 1;
6084 }
6086 1;