Bug 4647 – Generate JS Bindings should build a build rule

• Component: SVG
• Status: RESOLVED INVALID

[Eric Seidel (no email)]

Generate JS Bindings is the current (hackish) way of generating KDOM's automatic JavaScript bindings.  It's 
a small perl script run as part of the build process.

This reallly should be a build rule, keyed off of the idl files included in the project.

It also should at least generate the files into the DerivedSources directory, instead of modifying the source 
root.

[Eric Seidel (no email)]

Created attachment 3622 [details]
Replaces build phase with build rule, moves generated files to DerivedSources

[Eric Seidel (no email)]

Comment on attachment 3622 [details]
Replaces build phase with build rule, moves generated files to DerivedSources

This turns the previous "Generate JS Bindings" build phase into a really nifty
idl -> cpp/h build rule, removes the generated files from the xcode project as
well as moves the generated files out of the source root and into
DerivedSources.

[Darin Adler]

Comment on attachment 3622 [details]
Replaces build phase with build rule, moves generated files to DerivedSources

Seems good. r=me

[Eric Seidel (no email)]

Comment on attachment 3622 [details]
Replaces build phase with build rule, moves generated files to DerivedSources

It turns out that this only works due to the fact that I had "continue after
errors" set, and was building twice (w/o realizing).  There are header
dependencies in the generated .cpp files which this build rule approach
exposes.  Until I can find a workaround in Xcode I'm going to need to roll this
back out.

[Eric Seidel (no email)]

autobinding is now done as a makefile.  Thsi bug is no longer needed.