Compatibility with Sinan directory structure
I would like to be able to create a directory structure using Sinan, and then attach to that directory structure using Erlide.
The issue arises when I set the workspace root as the Sinan root. Erlide expects any projects to be located directly beneath that dir. But, Sinan places individual application directories in a 'lib' subdirectory. Erlide doesn't like this.
In addition - I'd really like to be able to build using Sinan, so that my beam files are in the std Sinan dir '_build'.
I guess this means I want to be able to configure Erlide to provide editing and debugging facilities, but let it delegate building, testing, and packaging to Sinan (or some other build tool) instead.
The issue arises when I set the workspace root as the Sinan root. Erlide expects any projects to be located directly beneath that dir. But, Sinan places individual application directories in a 'lib' subdirectory. Erlide doesn't like this.
In addition - I'd really like to be able to build using Sinan, so that my beam files are in the std Sinan dir '_build'.
I guess this means I want to be able to configure Erlide to provide editing and debugging facilities, but let it delegate building, testing, and packaging to Sinan (or some other build tool) instead.
Leave a comment
on 2011-03-03 12:16 *
By Vlad Dumitrescu
I'm not sure I understand all the requirements:
a) should there be a single erlide project that refers to all the applications in the lib directory?
b) or do you want a separate project for each application in lib, without needing to manually create a project for each?
c) is the '_build' directory a sibling of 'lib'?
d) or is there one '_build' per application in 'lib'?
For (a), you can create a project in the top directory and use the "discover paths" button on the second page of the wizard. It might not discover everything, some manual tweaking might be needed.
For (b), we don't have a "multiple projects import", it's probably not difficult to add.
For (c+a) and (d+b), it's just a matter of configuring the project to use _build instead of ebin and disable the automatic build in eclipse (in the 'project' menu).
(c+b) might work, but the _build dir is outside the projects' area and I'm not sure if Eclipse likes that.
(d+a) is tricky, we don't have support for that yet.
a) should there be a single erlide project that refers to all the applications in the lib directory?
b) or do you want a separate project for each application in lib, without needing to manually create a project for each?
c) is the '_build' directory a sibling of 'lib'?
d) or is there one '_build' per application in 'lib'?
For (a), you can create a project in the top directory and use the "discover paths" button on the second page of the wizard. It might not discover everything, some manual tweaking might be needed.
For (b), we don't have a "multiple projects import", it's probably not difficult to add.
For (c+a) and (d+b), it's just a matter of configuring the project to use _build instead of ebin and disable the automatic build in eclipse (in the 'project' menu).
(c+b) might work, but the _build dir is outside the projects' area and I'm not sure if Eclipse likes that.
(d+a) is tricky, we don't have support for that yet.
on 2011-03-03 16:39 *
By Vlad Dumitrescu
Updating tickets (#737, #242, #364, #373, #411, #473, #561, #218, #339, #358, #422, #423, #424, #425, #428, #432, #535, #543, #599, #636, #671, #684, #693, #694, #699, #41, #52, #64, #83, #93, #120, #149, #157, #163, #177, #179, #194, #195, #219, #222, #228, #261, #274, #281, #283, #285, #298, #318, #335, #349, #351, #375, #379, #383, #401, #405, #409, #412, #413, #434, #442, #449, #450, #451, #454, #460, #471, #492, #523, #537, #555, #559, #574, #577, #581, #598, #603, #615, #619, #632, #634, #639, #640, #641, #642, #643, #645, #658, #660, #662, #664, #665, #667, #673, #674, #679, #685, #695, #696, #700, #705, #707, #709, #716, #719, #720, #722, #728, #736, #738, #741, #743, #744, #746, #759, #760, #761, #762, #766, #767, #768, #769, #770, #771, #772, #773, #774, #775, #776, #779, #780, #786, #788, #789, #790, #791, #159, #372, #443, #479, #564, #601, #610, #622, #677, #429, #489)
on 2011-03-03 16:41 *
By Vlad Dumitrescu
Updating tickets (#560, #613, #737, #41, #52, #64, #83, #93, #120, #149, #157, #159, #163, #177, #179, #194, #195, #218, #219, #222, #228, #242, #261, #274, #281, #283, #285, #298, #318, #335, #339, #349, #351, #358, #364, #372, #373, #375, #379, #383, #401, #405, #409, #411, #412, #413, #422, #423, #424, #425, #428, #429, #432, #434, #442, #443, #449, #450, #451, #454, #460, #471, #473, #479, #489, #492, #523, #535, #537, #543, #555, #559, #561, #564, #574, #577, #581, #598, #599, #601, #603, #610, #615, #619, #622, #632, #634, #636, #639, #640, #641, #642, #643, #645, #658, #660, #662, #664, #665, #667, #671, #673, #674, #677, #679, #684, #685, #693, #694, #695, #696, #699, #700, #705, #707, #709, #716, #719, #720, #722, #728, #736, #738, #741, #743, #744, #746, #759, #760, #761, #762, #766, #767, #768, #769, #770, #771, #772, #773, #774, #775, #776, #779, #780, #786, #788, #789, #790, #791)
on 2011-09-27 16:01 *
By Vlad Dumitrescu
Component changed from None to project model
Component changed from None to project model
on 2013-10-08 12:56 *
By Vlad Dumitrescu
Found in version changed from 0.10.0 to -none-
Status changed from New to Invalid
Found in version changed from 0.10.0 to -none-
Status changed from New to Invalid