[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] Chicken 4.5.0 on Windows?
From: |
Felix |
Subject: |
Re: [Chicken-users] Chicken 4.5.0 on Windows? |
Date: |
Fri, 14 May 2010 13:57:20 +0200 (CEST) |
From: Jeronimo Pellegrini <address@hidden>
Subject: Re: [Chicken-users] Chicken 4.5.0 on Windows?
Date: Wed, 12 May 2010 13:23:45 -0300
> On Wed, May 12, 2010 at 04:42:14PM +0200, Felix wrote:
>> Can you run "make ... confclean" and try again, sending me the output?
>
> Ops. That was the problem! Cleaning the configuration first was
> necessary.
>
> So, I actually managed to generate Windows binaries in two ways:
>
> 1) Cross-compiling, up to some point:
>
> $ make PLATFORM=linux clean
> $ make PLATFORM=linux confclean
> $ RC_COMPILER=i586-mingw32msvc-windres LIBRARIAN=i586-mingw32msvc-ar make \
> PLATFORM=cross-linux-mingw CHICKEN=./chicken-boot-4.3.7-linux-x86 \
> C_COMPILER=i586-mingw32msvc-gcc-4.4.2
>
> (I found these variables in defaults.make, so I used them. They're not
> described in the README)
Yes, that's the correct settings. I'll add a chapter for cross-compilation
to the manual and will try to document all this properly.
>
> I'm not sure how the cross-compilation process would proceed, and how
> I'd install the binaries and DLLs on the target machine.
>
Pass DESTDIR when running the "install" target and the installation
tree should end up there. Zipping up the tree would give you a working
binary distribution, provided the tree is located at the root directory
(or set the environment variable CHICKEN_PREFIX, but I'm not completely
sure whether it works - I'll have to test this)
>
> 2) Directly from Windows:
>
> c:\> mingw32-make PLATFORM=mingw PREFIX=c:/mingw confclean
> c:\> mingw32-make PLATFORM=mingw PREFIX=c:/mingw
> c:\> mingw32-make PLATFORM=mingw PREFIX=c:/mingw install
>
> The first line was not in the instructions in the wiki,
> http://chicken.wiki.br/compiling-chicken-on-windows-xp-with-mingw
> (I'll add it).
It should not be necessary. Did you invoke the build process
before, perhaps aborting it? Where did you obtain the sources,
was there a chicken-config.h included?
cheers,
felix