Le 04/11/2011 02:29, kcrisman a écrit :
On the other hand, it's also clear that without significantly more
help on the Cygwin port, it's not going to be there for a while. I
just messed with it today, and decided to uninstall my Cygwin instead
because of some weird sed problem Leif and I were trying to figure out
a few months ago... sigh.
Why do you want to use cygwin?
I ported ekiga (http://www.ekiga.org) to win32 some years ago, using
mingw. To that day, that is still how we have ekiga-on-win32 : it's
cross-compiled on a debian box.
Of course, that was made easier by having a good build system in place
already -- something I don't think all sage's spkg have.
I want as proof my still-in-the-works port of sage to ARM, which
basically fails because some build scripts don't work like :
- check feature 1
...
- check feature N
- if we don't have what we *really* need : FAIL explaining why.
but rather a more deliberately fragile one :
- check very-specific-arch1, and set magic options if so ;
...
- check very-specific-archN, and set magic options if so ;
- if we aren't on a known arch, or a fly farted too near a known one : FAIL.
Another problem on the way to cross-compilation is that some packages
want to run tests at compile-time to adjust settings : those tests will
have to be disabled when cross-compiling.
So to summarize what's above :
1) I can help with a win32 port, but by cross-compiling, as I know it's
efficient ;
2) in fact, helping with a win32 port would be a natural follow-up to my
current work on the ARM port ;
3) but that won't be an easy ride (especially if I'm all alone as for
the ARM port).
Snark on #sage-devel
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
