Dear Paul and al,

I answer to myself because I have located and corrected what is going
wrong. Ant is not to blame. The problem is in the build.el file that is
generated when building the configure-ebuild target.

When you replace @{build.lisp.dir} by ${build.lisp.dir} and
@{src.lisp.dir} by ${src.lisp.dir} then there are \ in a Lisp string
without escape. This is what causes the problem.

This does not happen for @{cedet.dir}, because it is read directly from
the build.properties file.

I propose to correct this by replacing \ to / by using some pathconvert
task like this:

     <pathconvert property="unix.build.lisp.dir" targetos="unix">
        <path path="${build.lisp.dir}"/>
        <mapper>
          <globmapper from="*" to="*"/>
        </mapper>
      </pathconvert>    

And then use ${unix.build.lisp.dir} instead of ${build.lisp.dir} in the
configure-ebuild target replacement.

I have attached a corrected build.xml. With this correction I can go
further, but there are still errors in the byte-compilation, please see log
file byte-compile.log.gz

Best regards,
   Vincent.

Attachment: build.el
Description: application/emacs-lisp

Attachment: build.xml
Description: Corrected build.xml

Attachment: byte-compile.log.gz
Description: compile log

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
jdee-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jdee-users

Reply via email to