Yes. Try a decent operative system.
> Hello, maybe someone has already some experience with this, it's
> technical:
> I'm trying to install ECL lisp on windows using msys and mingw from
> the source files. It works very well with these commands from msys:
> ./configure
> make
> make install
> That generates the ecl.exe and all well, however this is creating an
> ecl.dll dynamic library that I prefer not to have, and would like to
> replace it by a static library using:
> ./configure --disable-shared
> but in this case the making of ecl fails completely! I read on another
> post that this was a problem but seeminly was solved:
> http://coding.derkeiler.com/Archive/Lisp/comp.lang.lisp/2006-01/msg00932.html
> But I don't think it was solved because it still fails to build.
> Anyone has any hints on any way to do this correctly? Thanks
>
That's the Linux build code. Get the windows version. It's devoid of that
primitive command line gibberish. Just dobble click the icon.
--------------
John Thingstad
> On Jan 7, 10:20 am, "John Thingstad" <jpth...@online.no> wrote:
>> På Tue, 06 Jan 2009 12:41:41 +0100, skrev Francogrex <fra...@grex.org>:
>>
>>
>>
>>
>>
>> > Hello, maybe someone has already some experience with this, it's
>> > technical:
>> > I'm trying to install ECL lisp on windows using msys and mingw from
>> > the source files. It works very well with these commands from msys:
>> > ./configure
>> > make
>> > make install
>> > That generates the ecl.exe and all well, however this is creating an
>> > ecl.dll dynamic library that I prefer not to have, and would like to
>> > replace it by a static library using:
>> > ./configure --disable-shared
>> > but in this case the making of ecl fails completely! I read on another
>> > post that this was a problem but seeminly was solved:
>> >http://coding.derkeiler.com/Archive/Lisp/comp.lang.lisp/2006-01/msg00...
>> > But I don't think it was solved because it still fails to build.
>> > Anyone has any hints on any way to do this correctly? Thanks
>>
>> That's the Linux build code. Get the windows version. It's devoid of
>> that
>> primitive command line gibberish. Just dobble click the icon.
>>
>> --------------
>> John Thingstad- Hide quoted text -
>>
>> - Show quoted text -
>
> Hi, can you show me where that is please? I am getting the source code
> from there:
> http://sourceforge.net/project/showfiles.php?group_id=30035&package_id=22059
> and as far as I know they are the only ones around. So I am building
> it from source and it works quite well when you do want to have the
> ecl.dll but fails when you ask instead for a statically linked library.
try this:
http://sourceforge.net/project/showfiles.php?group_id=30035
--------------
John Thingstad
I am not sure that the windows MSVC port was ever designed to be
statically linked. The Makefile is probably missing the appropriate
options, and since currently I have no Windows machine to fix this, it
will have to wait until I get a virtual environment up and running, or
until somebody adds the missing bits.
Juanjo
An "operative system?" You mean, like the CIA?
The sources do not need to be modified to get a statically linked
library: that is simply dictated by an option that is set when you
build ECL. What I meant is that the option is missing from the MSVC
makefiles.
In the Linux and similar versions (including mingw), you should simply
pass a configuration flag to "configure". Just do ./configure --
prefix=... --disable-shared ... The problem you will find is that
version 8.12.0 does not install the statically linked version
properly, but the executable gets built. I am working on a fix.
Please report if --disable-shared does not work in mingw so that I add
it to the list of things to be fixed.
Juanjo
Ok, sorry for the inconvencience. I will look into that.
Juanjo
Well, there are only two possible advantages: compact distribution and
hiding the actual implementation of a program.
BTW, could you send me by email the fix you used to build ECL
statically?
Juanjo