search

stoneCC / serf

Automatically exported from code.google.com/p/serf
Apache License 2.0
0 stars 0 forks source link

Not possible to build Serf under MinGW! #142

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi.

I've tried to build Serf under Windows using MinGW toolchain. It's impossible - 
the build fails with various errors. Why did you choose that SCons? I've tried 
to debug it and wasn't very impressed by the code - it's very complex and 
tightly coupled. And by the way, APR, APU, and OpenSSL build without problem 
under MinGW with their autotools. And all these libraries are way more complex 
than serf.

The problem is: as you know, MSYS terminal is launched from something like 
"chroot" - i.e. / is in fact C:\MinGW\msys\1.0\ and you can't get out of it, 
you access C:\ as /c/. And SCons gets mad about this fact - it tries to 
normalize all paths, so for example it changes /usr/include/apr-1 to 
C:\usr\include\apr-1, and that's not correct, / isn't C:\! / is 
C:\MinGW\msys\1.0!

Can you fix this problem in some way? I want to build Subversion using a free 
software toolchain, without using msvc.

Original issue reported on code.google.com by vita...@yourcmc.ru on 18 Feb 2014 at 1:03

GoogleCodeExporter commented 9 years ago 
I seriously doubt you'll find one of the serf developers take the time to fix 
this issue, most of us use Visual Studio on Windows or Mac's/Linux.
We'll accept patches though. Scons itself supposedly supports MingW, so my 
guess is that you'll have to add MingW as (another) special case in serf's 
SConstruct.
L.

Original comment by lieven.govaerts@gmail.com on 28 Jun 2014 at 9:31

GoogleCodeExporter commented 9 years ago 
I've tried once, but I don't have experience in SCons, it seems rather 
complicated to me, and I failed to fix it... Maybe you can help me?

Original comment by vita...@yourcmc.ru on 28 Jun 2014 at 6:09

GoogleCodeExporter commented 9 years ago 
Hi,

this looks like you're trying to run SCons under Cygwin. Did you install SCons 
under Cygwin as well ("python setup.py install" with the Cygwin-Python), or did 
you use the provided MSI installer?
If you mixed things (Cygwin vs. plain Windows) up, this would explain the path 
issues you seem to experience.

Original comment by dl9...@darc.de on 25 Aug 2014 at 10:44