I've never tested under Cygwin emacs, but there are lots of problems
that come the way it treats DOS paths in a UNIX like way.
Support for XEmacs, GNU Emacs, then (X)Emacs built for cygwin starts
to get out of hand.
In your own environment, you could start using things like `cygpath'
to make these path conversions but I think you're time is better spent
using the GNU build of Emacs under NT.
On Mar 17, 2010, at 8:14 AM, Troy Daniels wrote:
>
>
> On Sun, Mar 14, 2010 at 5:24 PM, Paul Landes <landes@...> wrote:
> Please send the error message it complains with when compiling.
>
>
> With the standard build file, it fails with
>
> ant -emacs
> Searching for build.xml ...
> Buildfile: C:\cygwin\home\udalrich\jdee\2.4.0\jde\build.xml
>
> init:
>
> prepare-lisp-build:
>
> configure:
>
> configure-ebuild:
>
> BUILD FAILED
> C:\cygwin\home\udalrich\jdee\2.4.0\jde\build.xml:103: exec returned:
> 255
>
> Total time: 2 seconds
>
> This fails at
>
> <exec outputproperty="build.lisp.is-xemacs"
> executable="${build.bin.emacs}" failonerror="true">
> <arg value="--no-site-file"/>
> <arg value="--batch"/>
> <arg value="--eval"/>
> <arg value="(message "%S" (if (featurep 'xemacs)
> 'true 'false))"/>
> </exec>
>
> If the last arg is replaced with
>
> <arg value="(message \"%S\" (if (featurep 'xemacs)
> 'true 'false))"/>
>
> it gets further, since the command that gets to emacs is (message
> "%S" ...) instead of (message %S ...).
>
> When I fix that, it fails with
>
> $ ant
> Searching for build.xml ...
> Buildfile: C:\cygwin\home\udalrich\jdee\2.4.0\jde\build.xml
>
> init:
>
> prepare-lisp-build:
>
> configure:
>
> configure-ebuild:
>
> build-lisp:
> [exec] Cannot open load file: C:/cygwin/home/udalrich/jdee/
> 2.4.0/jde/build/
> config/build.el
>
> BUILD FAILED
> C:\cygwin\home\udalrich\jdee\2.4.0\jde\build.xml:149: exec returned:
> 255
>
> Total time: 4 seconds
>
>
> build.el exists and is readable. However, the cygwin version of
> emacs can't handle the windows version of the path.
>
> Troy
>
>
> Thanks Troy.
>
>
> On Mar 13, 2010, at 9:52 AM, Troy Daniels wrote:
>
>> I'm trying to make some changes to JDE, but I'm running into
>> problems just using emacs. I'm using cygwin on Windows NT.
>>
>> I was able to get the emacs that comes with cygwin to run using
>> XWin as an X server. However, I think I recall that that version
>> doesn't interface well with JDE. In particular, the build file has
>> quoting issues when execing emacs. If I fix that, it complains
>> that it can't load a window's style path.
>>
>> I've also tried using the version from http://ftp.gnu.org/gnu/emacs/windows/
>> . That fails to create a window and just hangs at the command
>> prompt.
>>
>> I managed to get this working on my work computer years ago with a
>> non-cygwin version, but I can't seem to get it to work on my home
>> laptop (which is where I can access the JDE svn repository.)
>>
>> What configuration are people using? Any suggestions on what I can
>> try to figure out the problems?
>>
>> Troy
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>>
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev_______________________________________________
>>
>> jdee-devel mailing list
>> jdee-devel@...
>> https://lists.sourceforge.net/lists/listinfo/jdee-devel
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> jdee-devel mailing list
> jdee-devel@...
> https://lists.sourceforge.net/lists/listinfo/jdee-devel
>
>
|