I'm curious about the naming convention for the snippet files. fm_IDL.d/aou.xml? Or something more verbose?
The IDL-compiler script will need to be functional from within the repo without any assumptions about files getting installed. IIUC, the i18n code and certainly the Angular/Karma unit test data collector (staff/test/data/idl2js.pl) require access to a compiled IDL regardless of whether Evergreen is locally installed. Maybe that just means running the compiler during 'make' (at least before 'make install') or teaching these scripts to invoke the compiler themselves.
Not to muddy the waters, but while we're in there, should we move the IDL data from 'examples' and into a new 'src' directory (src/IDL/* or similar)? Low priority, obviously.
+1.
I'm curious about the naming convention for the snippet files. fm_IDL.d/aou.xml? Or something more verbose?
The IDL-compiler script will need to be functional from within the repo without any assumptions about files getting installed. IIUC, the i18n code and certainly the Angular/Karma unit test data collector (staff/ test/data/ idl2js. pl) require access to a compiled IDL regardless of whether Evergreen is locally installed. Maybe that just means running the compiler during 'make' (at least before 'make install') or teaching these scripts to invoke the compiler themselves.
Not to muddy the waters, but while we're in there, should we move the IDL data from 'examples' and into a new 'src' directory (src/IDL/* or similar)? Low priority, obviously.