* Automated build script for Windows builds
@ 2016-01-04 2:27 Mads Elvheim
0 siblings, 0 replies; 2+ messages in thread
From: Mads Elvheim @ 2016-01-04 2:27 UTC (permalink / raw)
To: guile-devel
I made an hacky shell script to automatically build guile from the git
repo for Windows.
I have only tested it on Ubuntu 14.04 with MinGW-w64, but it should be
easy to get working
on multiple systems with some small changes.
Repo on github: https://github.com/Madsy/guile-automatic-build
Win32 binaries people can use: http://www.mechcore.net/files/guile/win32/
In addition to building guile, I made some Windows scripts for starting
guile
with the correct search paths, and to run the test suite.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Automated build script for Windows builds
@ 2016-01-11 19:09 Peter TB Brett
0 siblings, 0 replies; 2+ messages in thread
From: Peter TB Brett @ 2016-01-11 19:09 UTC (permalink / raw)
To: guile-devel
Hi Mads,
Glad to see I'm not the only person who's building Guile for Windows!
For the gEDA project, which uses Guile quite extensively, we've for
quite some years had a recipe-based cross-build system called "minipack"
that's use for cross-compiling Guile and the geda-gaf electronic design
package.
https://github.com/peter-b/minipack
Do you think that there might be some scope for collaboration around
minipack? It might be a good approach for avoiding duplication of
effort in this area, and would mean that more time can be spent on
improving Guile on Windows rather than just getting it working.
I've identified two things that I'd really like to get some help with:
* Guile is happy to be built with an i686-w64-mingw32 compiler, but it
fails to build with an x86_64-w64-mingw32 compiler. This is because
of the implementation of scm_i_inum2big(). This is happy to be
compiled on LP64 systems (where sizeof(long) == 8). However, Windows
x64 is an LLP64 system where sizeof(int) == sizeof(long) == 4, meaning
that scm_i_inum2big() doesn't work. I'm not sure what would be
involved with addressing this, but until it is fixed, it's not
possible to compile a 64-bit Guile for Windows.
* Currently, it's necessary to define the GUILE_LOAD_COMPILED_PATH,
GUILE_LOAD_PATH and (optionally) GUILE_SYSTEM_EXTENSIONS_PATH
environment variables before guile.exe will run on a Windows systems.
Ideally, I'd like to be able to provide a relocatable Windows build
that could be provided as an archive that could be extracted anywhere
and run with no additional configuration. What would be involved in
enabling libguile to guess appropriate load paths on Windows without
having to faff around with Windows' awkward environment variable
configuration UI?
Thanks in advance to anyone who can help me out with these two issues!
Peter
--
Dr Peter Brett <peter@peter-b.co.uk>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-01-11 19:09 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-01-11 19:09 Automated build script for Windows builds Peter TB Brett
-- strict thread matches above, loose matches on Subject: below --
2016-01-04 2:27 Mads Elvheim
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).