Hi all!
For those who wishes to use picolisp in Windows: try to use coLinux instead of
Cygwin (see also "andLinux"),
coLinux seems to work fine, and you can compile "native" linux version of
picolisp
Homepage of coLinux: http://www.colinux.org/
1) Download coLinux kernel from http://sourceforge
Hi Alex,
Yes, I think we should stay with the #ifdef patch for a while
The case with dlopen("lib1") seems not to be used, but I checked it just in case
Best regards,
Mansur
> Hi Mansur,
>
> thanks for the info!
>
> > > > /home/me/project/myexe.exe
> > > > /home/me/project/lib1.dll
> > > > /h
Some things you don't bring from Windows. Then you bring Unix to Windows
instead.
There is a market for it, or Cygwin nor Services For Unix would not exist.
("Services For Unix" being Microsofts strange name for their Cygwin-like
offering.)
On Thu, Apr 29, 2010 at 04:32:07PM +0200, Henrik Sarv
Please explain to me, why are you guys spending time trying to fix Cygwin? I
really want to know, am I missing something fundamental here?
Cygwin is the reason I went all out Linux some 5 years ago when I tried to
develop an SMS gateway with Linux as the target, on Win in Cygwin, too many
problems
Hi Mansur,
thanks for the info!
> > > /home/me/project/myexe.exe
> > > /home/me/project/lib1.dll
> > > /home/me/project/subdir/lib2.dll
> > > /home/me/project/subdir/lib3 (without .dll)
> > > ...
> > > 1) dlopen("subdir/lib2") - NOT FOUND (If this OK, then why failed
> > > dlopen("subdir/lib3")?
Thu, 29 Apr 2010 15:04:47 +0200 Corinna Vinschen :
> On Apr 29 12:39, Mansur Mamkin wrote:
> > Hello,
> >
> > As I see in source of dlfcn.cc, dlopen() should override LoadLibrary's
> > automatic adding of a ".dll" suffix,
> > but it's behaving strangely
> >
> > I have such files:
> > /home/me
