Edwin, It doesn't do this right now. There is a reason for that. In current Erlang semantics multilevel source directories indicate the use of packages. Packages in Erlang are not first class features of the language and may be depricated at any time (not that that is all that likely, really). On top of that a lot of the erlang tools just don't support packages, or at least they haven't in the past. I haven't looked at that lately. So I, explicitly, didn't support directories in the src because I didn't want to support packages in general.
Now, it sounds like you aren't actually using packages. You just want multiple levels of source that will all build into the ebin directory. If that is the case its fairly easy to support that. I could probably put together a patch to do that in short order. However, if you are actually using packages that may be a different story. Eric On Sun, Jun 14, 2009 at 11:37 AM, Edwin<[email protected]> wrote: > > Often I need to "projectize" an existing Erlang package that is well- > formed, other than having a multi-level src directory structure (i.e. > subdirectories under src, each having some of the src). I don't know > how to get Sinan to do that, and I can't find an answer searching. > Copying all the files from the subdirectories to the src level is not > an option, and turning each of the subdirectories into an app is just > wrong. > > Doesn't Sinan recurse into subdirectories of the source directory? Is > there a way/command-line option/_build.cfg setting to force it to? How > do I solve this? It's really holding me up. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en -~----------~----~----~----~------~----~------~--~---
