Re: [ft-devel] Freetype 2.4.10 MSVC++ / Cygwin Compile fails

2012-09-20 Thread mpsuzuki
On Wed, 19 Sep 2012 11:07:02 -0500 RMWChaos rmwch...@thedarklands.com wrote: On 2012-09-19 10:30, suzuki toshiya wrote: [...snip...] Ahh, I see. I will try. Using autoconf for Cygwin/MSVC is pretty common in my (albeit limited) experience. You can refer to various libs to see this for

Re: [ft-devel] Freetype 2.4.10 MSVC++ / Cygwin Compile fails

2012-09-20 Thread RMWChaos
Now we're no longer top-posting. :) On 2012-09-20 07:18, mpsuz...@hiroshima-u.ac.jp wrote: I don't think ICU is good example, but anyway I will try some libraries using genuine autoconf only. I may be able to save you the trouble of testing further with cygwin bash / MSVC unless you truly want

Re: [ft-devel] Freetype 2.4.10 MSVC++ / Cygwin Compile fails

2012-09-19 Thread suzuki toshiya
RMWChaos wrote: On 2012-09-18 23:26, mpsuz...@hiroshima-u.ac.jp wrote: $ /cygdrive/e/MSVC2005/VC/bin/cl.exe /? /cygdrive/e/MSVC2005/VC/bin/cl.exe: error while loading shared libraries: MSVCR80.dll: cannot open shared object file: No such file or directory I don't have this

Re: [ft-devel] Freetype 2.4.10 MSVC++ / Cygwin Compile fails

2012-09-19 Thread RMWChaos
On 2012-09-18 23:26, mpsuz...@hiroshima-u.ac.jp wrote: Hmm. My concerns about Cygwin + MSVC cross compiling are following 2 points: * The compiler linker of MSVC are dependent with many MSDOS environmental variables designed for MSVC (to make compiler/linker search appropriate SDK directories

Re: [ft-devel] Freetype 2.4.10 MSVC++ / Cygwin Compile fails

2012-09-19 Thread RMWChaos
On 2012-09-19 10:30, suzuki toshiya wrote: [...snip...] Ahh, I see. I will try. Using autoconf for Cygwin/MSVC is pretty common in my (albeit limited) experience. You can refer to various libs to see this for yourself. An example is lib ICU, which has a CYGWIN/MSVC option in its configure

Re: [ft-devel] Freetype 2.4.10 MSVC++ / Cygwin Compile fails

2012-09-19 Thread RMWChaos
On 2012-09-19 11:07, RMWChaos wrote: If I remove cygwin from my path statement first, it then defaults to the dos/windows setup, which is an improvement. Unfortunately, something else is now failing... process_begin: CreateProcess(NULL, type builds\newline, ...) failed. make (e=2): The

[ft-devel] Freetype 2.4.10 MSVC++ / Cygwin Compile fails

2012-09-18 Thread RMWChaos
*ENVIRONMENT:* MS Windows 7 x64 MSVC 2008 / SDK 7.0 -or- 2010 / SDK 7.1 Cygwin bash GNU make 3.8.1 *PREAMBLE:* Ultimately, this might turn out to be one build 'bug' and one build feature 'enhancement / change request', and perhaps I should submit this as two separate issues; however, they

Re: [ft-devel] Freetype 2.4.10 MSVC++ / Cygwin Compile fails

2012-09-18 Thread suzuki toshiya
Today I don't have my machine with MSVC in my hand... I think make setup visualc is not designed for the combination of Cygwin bash/make + MSVC. It would be suitable for MinGW make + MSVC. The binaries you want to build are those running on Windows platform WITHOUT cygwin? Or, those running

Re: [ft-devel] Freetype 2.4.10 MSVC++ / Cygwin Compile fails

2012-09-18 Thread mpsuzuki
On Tue, 18 Sep 2012 16:40:24 -0500 RMWChaos rmwch...@thedarklands.com wrote: Mpsuzuki, Thanks for your response. Running without Cygwin dependency. Cygwin bash is just used during the ./configure process; otherwise, I wouldn't even use it. I see. Most other libs' configure processes that I've

Re: [ft-devel] Freetype 2.4.10 MSVC++ / Cygwin Compile fails

2012-09-18 Thread RMWChaos
Mpsuzuki, Thanks for your response. Running without Cygwin dependency. Cygwin bash is just used during the ./configure process; otherwise, I wouldn't even use it. Specifically, I'm expanding on the planned official auto-build process for Mapnik, which currently is just a list of steps for