>>> "Nascif Abousalh-Neto" <[EMAIL PROTECTED]> 10-Nov-00 5:21:28 PM >>> >The relative path is a great idea. >The result is that we can't share prj.el files. Note that although this is an improvement this isn't *much* of a magic bullet for team based project files. We still have a problem that some things are dependant on the platform the developer is on. For example, one team I'm part of all use Emacs/JDE for development but some of us use Kaffe and some of us use Sun Java. When using Kaffe we have the bootclasspath for compilation set to the Klasses.jar that is supplied with Kaffe (it's the core java classes jar file). But the people using Sun don't have that file so they have to alter their copy of the project files. That's why what is needed is some way of having "system-dependant" config and "project-dependant" config. Nic
- project based compilation Nic Ferrier
- Re: project based compilation Paul Kinnucan
- Re: project based compilation Nic Ferrier
- Re: project based compilation EHusby
- Re: project based compilation Nic Ferrier
- Re: project based compilation Paul Kinnucan
- Re: project based compilation Nic Ferrier
- Re: project based compilation Paul Kinnucan
- RE: project based compilation Nascif Abousalh-Neto
- Re: project based compilation Nic Ferrier
- Re: project based compilation Nic Ferrier
- Re: project based compilation Louise Pryor
- Re: project based compilation Nic Ferrier
- Re: project based compilation Paul Kinnucan
- Re: project based compilation Paul Kinnucan
- RE: project based compilation Jeff Jensen
- Re: project based compilation Nic Ferrier
- Re: project based compilation Paul Kinnucan
- RE: project based compilation Jeff Jensen
- Re: project based compilation Nic Ferrier
- Re: project based compilation Paul Kinnucan
