Changes between Version 3 and Version 4 of AddingFiles

Timestamp:

Mar 3, 2014 11:18:09 AM (10 years ago)

Author:

BJ Burg

Comment:

details on adding code generators for win and mac

AddingFiles

@@ -17 +17 @@
 If adding a header file that should be accessible from other frameworks (say, using a WebCore framework from WebKit2), then you must alter the file's target membership from "Project" to "Private" in the "Target Membership" details sidebar, using the drop-down next to the framework. If using headers from JavaScriptCore inside WebCore, you must also add a forwarding header in `Source/WebCore/ForwardingHeaders` in the appropriate mirrored directory structure.
 
+=== Adding code generators / generated files
+
+Aside from adding the build dependencies to `DerivedSources.make` (which is used by all ports), you may need to do the following:
+
+ * If the code generator from one framework is used by another, you will need to add it to the Private Headers group. For non-header files, temporarily set the file type to C Header, change the header group to Private, and then change back to the correct file type.
+ * If the rules added to `DerivedSources.make` rely on environment variables, you need to set those in `make-generated-sources.sh`.
+
 == Visual Studio (Windows)
 
@@ -25 +32 @@
 * Make a stub in `Project.vcxproj.filters` at the top.
 
-
 === Adding a file
 
  * Add a `CLInclude` command for a header file and `CLCompile` command for an implementation file.
  * It's recommended that you consult a build expert for anything more complicated, such as adding a new code generator (especially if you can't run Visual Studio yourself).
+
+=== Adding code generators / generated files
+
+ * Make sure that the rules in `copy-files.cmd` will properly copy any generated files you want to use from other frameworks.
+ * If you rely on environment variables inside `DerivedSources.make`, you will need to export them in `build-generated-files.sh`.
 
 == CMake (EFL)