1st of all many thanks for your great dedication, I really appreciate
your effort to work on mine and the other issues listed here. And now
I'll try to clarify, sorry for the confusion:
- The ~/ just marks the root dir of my ECL sources (in fact
F:\usr\src\ecls-cvs\) and I also used the flatinstall (to
- As far as I understand, the ASDF compile process uses the C compiler
command as defined by c::*cc-format* in compile.lsp.in and this only
includes a link to the @true_builddir@, which will become '~/msvc//h' in
- The missing include 'ecl-cmp.h' would in my case happen to be in
F:\usr\src\ecls-cvs\src\h oder in D:\usr\local\ecl-0.9\h but none of
these is listed in c::*cc-format*.
- The compilation works, when I set the INCLUDE environment variable (to
include F:\usr\src\ecls-cvs\src\h) but I guess that it's the very idea
of the c::*cc-format* to allow compilation w/o this. What I'm compiling
is the split-sequence library in directory
F:\usr\src\cl-libs\split-sequence using the following compile code:
(make-build :split-sequence :type :fasl)
This is started in directory F:\usr\src\cl-libs\split-sequence.
- I don't see how compilation should work if the header directory
~\src\h which holds files NOT available in ~\msvc\h is not in the
include path, so my proposal was to add this, either from below the
@true_srcdir@ or from the target path of the flatinstall.
btw.: the 2nd issue has been "solved" by a 'nmake clean' and a complete
Hope that helps - otherwise just forget my complaints, and I'll stick
with my INCLUDE environment variable ;)
Juan Jose Garcia Ripoll wrote:
>On Fri, 2005-11-11 at 23:47 -0800, fBechmann@... wrote:
>>while trying an external library using the proposed asdf hack
>>(http://sourceforge.net/forum/forum.php?forum_id=504868) I always
>>receive an compile error because of the missing include 'ecl-cmp.h'.
>>this file is really not in the include path used by the compile command,
>>since this only contains '~/msvc//h', whereas the requested include file
>>is in '~/src/h'.
>>I guess that it should be OK and enough to add '-I\"@true_srcdir@...'
>>to the 'c::*cc-flags*' as defined in compile.lsp.in. I even tried that
>>fix, re-build compile.lsp, ecl2.exe, and called nmake flatinstall - but
>>I still don't see the changed include path when starting the compile for
>>the external library.
>I do not understand very well what happens in your setup. ECL is not
>designed to be run from the build directory. You should first install
>it. But it seems you did it.
>Let us say that you do a flat install specifying the destination
> nmake flatinstall prefix=d:\ecl
>Now, when installed, the file ecl-cmp.h should be copied to
>$(prefix)/h/ecl-cmp.h, and the path $(prefix)/h should be part of the
>Now, in your email you mention ~/msvc. Is this where you install ECL? Is
>ecl-cmp.h installed? If not this is a bug.
>>so 2 issues:
>>- is it OK to add '~/msvc/h' to the include path in compile.lsp.in? if
>>so, couldn't it go to CVS?
>Definitely one cannot include fixed paths in the CVS :-/
>>- why doesn't the re-compile described above help me to use the changed
>The paths and flags in compile.lsp[.in] are only used at build time --
>i.e. when constructing the ecl.exe and ecl.dll files --. The permanent
>settings are part of cmpmain.lsp and cmpcfg.lsp. That is where the C/C++
>compile and link flags are determined.
>SF.Net email is sponsored by:
>Tame your development challenges with Apache's Geronimo App Server. Download
>it for free - -and be entered to win a 42" plasma tv or your very own
>Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
>Ecls-list mailing list