Hi! On Nov 12, 2007 2:38 PM, <[EMAIL PROTECTED]> wrote: > I'm trying to convert existing erlang project structure to make it work with > Erlide (using new Erlang project that works as a reference). > I did following in my existing project: > - Toggled Erlang nature and Erlang make nature (That made .project files look > the same in new and existing projects, > only project name differs) > - Copied .codepath from new to existing project and added additional entries > to include_dirs and external_includes. > I ended up doing manual edits since UI didn't seem to work.
Maybe it would be better to try this instead (after deleting .project and .codepath): create a new Erlang project and in the wizard point it to the directory where you have the code. You can then type the source/include/ebin directories or let the wizard find them by pressing "discover paths". This is better than editing the project files by hand. best regards, Vlad ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Erlide-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/erlide-devel
