Carolyn Beeton wrote: >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of >> Krzeminski, Damian (BL60:9D30) >> >> I'll happily move to SIPX_BUILD_TOP and SIPX_SRC_TOP or >> something like that. >> If someone documents suggested Eclipse environment vars on >> wiki, I'll change sipXconfig Eclipse projects accordingly. > > I have changed all the project files which used to use SIPX-PROJECT-ROOT > to use SIPX_SRC_TOP instead. I have removed the references to BUILD1 > and replaced them with SIPX_BUILD_TOP. I have updated the EDE to > reflect this. At some point, we can change the other project files and > get rid of SIPX_CONFIG (replace with SIPX_SRC_TOP/sipXconfig) and > SIPX_BUILD (replace with SIPX_BUILD_TOP/sipXconfig) and possibly > SIPX_COMMONS (replace with SIPX_SRC_TOP/sipXcommons). >
Thanks - I'll change it in sipXconfig projects. If you were working on sipXconfig projects only until now, don't wait for that change: define SIPX_BUILD_TOP and SIPX_SRC_TOP today. >> Could we also agree on the directory for Eclipse compiler output. >> sipXconfig is using bin.eclipse. I noticed other projects >> using "classes" >> or "build". Having a single name will simplify management of >> .gitignore and svn:ignore. >> >> You can check what's used currently: >> >> find -name .classpath | xargs grep output >> >> >> I am OK with any name as long as it has reference to >> "eclipse" in it. As much as I like Eclipse there is no reason >> why we should hijack the namespace if someone wants to use >> another IDE. >> D. >> > > I have changed all projects to use bin.eclipse for the Eclipse output. > > I'm not sure when these changes take effect: is it enough to Refresh the > project, or relaunch Eclipse, or do you have to Delete the project and > import it again? But this should not cause too much of a problem as we > don't change these files very often. > Thank you! I think you need to "Clean" and "Rebuild" to make those effective. You might even need to remove old output directories manually. D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
