Re: [mail] Re: Windows Build System

I think I have sorted through the confusion.

Looks like the only thing cygwin might be used for is a client. Here's what
the manual that comes with the 4.0.9gamma source says:

There are two versions of the MySQL command-line tool: Binary Description
mysql Compiled on native Windows, which offers
very limited text editing capabilities.
mysqlc Compiled with the Cygnus GNU compiler
and libraries, which offers readline editing.

If you want to use mysqlc.exe, you must copy `C:\mysql\lib\cygwinb19.dll' to
your Windows system directory (`\windows\system' or similar place).

I don't see a msqlc.exe below, but it is in the released binary
distribution, along with the cygwinb19.dll. (kinda strange having a mismatch
between source and binary distributions).

The server appears to be entirely native.

andrew

----- Original Message -----
From: "Dann Corbit" <DCorbit(at)connx(dot)com>
To: "Christopher Browne" <cbbrowne(at)cbbrowne(dot)com>; "Greg Copeland"
<greg(at)CopelandConsulting(dot)Net>
Cc: "Justin Clift" <justin(at)postgresql(dot)org>; "Jeff Davis"
<jdavis-pgsql(at)empires(dot)org>; "PostgresSQL Hackers Mailing List"
<pgsql-hackers(at)postgresql(dot)org>
Sent: Friday, January 31, 2003 8:22 PM
Subject: Re: [mail] Re: [HACKERS] Windows Build System

> For MySQL:
> There is no Cygwin needed. Period.
>
> I did a build last night. Using nothing but Visual Studio with the
> Intel C++ compiler for Win32.
> Here is what got built:
> E:\mysql-3.23.55>dir /s *.dll, *.exe
> Volume in drive E has no label.
> Volume Serial Number is 7496-C335
>
> Directory of E:\mysql-3.23.55\client_debug
>
> 31/01/03 11:36a 557,115 isamchk.exe
> 31/01/03 11:37a 733,247 myisamchk.exe
> 31/01/03 11:37a 602,175 myisamlog.exe
> 31/01/03 11:37a 487,480 mysql.exe
> 31/01/03 11:37a 458,813 mysqladmin.exe
> 31/01/03 11:37a 479,299 mysqlbinlog.exe
> 31/01/03 11:38a 4,296,758 mysqld.exe
> 31/01/03 11:37a 598,076 mysqldump.exe
> 31/01/03 11:37a 446,526 mysqlimport.exe
> 31/01/03 11:37a 573,500 mysqlshow.exe
> 31/01/03 12:48a 45,056 mysqlshutdown.exe
> 31/01/03 11:38a 618,559 pack_isam.exe
> 31/01/03 11:38a 307,200 replace.exe
> 13 File(s) 10,203,804 bytes
>
> Directory of E:\mysql-3.23.55\client_release
>
> 31/01/03 11:36a 327,680 isamchk.exe
> 31/01/03 11:37a 458,752 myisamchk.exe
> 31/01/03 11:37a 372,736 myisamlog.exe
> 31/01/03 11:37a 323,642 mysql.exe
> 31/01/03 11:37a 274,432 mysqladmin.exe
> 31/01/03 11:37a 278,528 mysqlbinlog.exe
> 31/01/03 11:37a 270,336 mysqlcheck.exe
> 31/01/03 12:35a 3,002,368 mysqld-max-nt.exe
> 31/01/03 12:48a 2,994,176 mysqld-max.exe
> 31/01/03 11:38a 2,564,096 mysqld-nt.exe
> 31/01/03 11:37a 2,560,000 mysqld-opt.exe
> 31/01/03 11:37a 286,720 mysqldump.exe
> 31/01/03 11:37a 266,240 mysqlimport.exe
> 31/01/03 11:37a 270,336 mysqlshow.exe
> 31/01/03 12:48a 45,056 mysqlshutdown.exe
> 31/01/03 12:48a 49,152 mysqlwatch.exe
> 31/01/03 11:38a 274,432 pack_isam.exe
> 31/01/03 11:38a 167,936 perror.exe
> 31/01/03 11:37a 188,416 replace.exe
> 19 File(s) 14,975,034 bytes
>
> Directory of E:\mysql-3.23.55\COMP_ERR\Release
>
> 31/01/03 11:36a 167,936 comp-err.exe
> 1 File(s) 167,936 bytes
>
> Directory of E:\mysql-3.23.55\libmysqltest\debug
>
> 31/01/03 11:37a 122,943 myTest.exe
> 1 File(s) 122,943 bytes
>
> Directory of E:\mysql-3.23.55\libmysqltest\release
>
> 31/01/03 11:37a 49,152 myTest.exe
> 1 File(s) 49,152 bytes
>
> Directory of E:\mysql-3.23.55\lib_debug
>
> 31/01/03 11:37a 467,005 libmySQL.dll
> 1 File(s) 467,005 bytes
>
> Directory of E:\mysql-3.23.55\lib_release
>
> 31/01/03 11:36a 278,528 libmySQL.dll
> 1 File(s) 278,528 bytes
>
> Directory of E:\mysql-3.23.55\myisampack\debug
>
> 31/01/03 11:37a 553,025 myisampack.exe
> 1 File(s) 553,025 bytes
>
> Directory of E:\mysql-3.23.55\myisampack\release
>
> 31/01/03 11:37a 311,296 myisampack.exe
> 1 File(s) 311,296 bytes
>
> Directory of E:\mysql-3.23.55\my_print_defaults\Debug
>
> 31/01/03 11:37a 319,567 my_print_defaults.exe
> 1 File(s) 319,567 bytes
>
> Directory of E:\mysql-3.23.55\my_print_defaults\Release
>
> 31/01/03 11:37a 180,224 my_print_defaults.exe
> 1 File(s) 180,224 bytes
>
> Directory of E:\mysql-3.23.55\PERROR\Debug
>
> 31/01/03 11:38a 294,969 perror.exe
> 1 File(s) 294,969 bytes
>
> Directory of E:\mysql-3.23.55\THR_TEST\debug
>
> 31/01/03 11:37a 127,037 thr_test.exe
> 1 File(s) 127,037 bytes
>
> Directory of E:\mysql-3.23.55\THR_TEST\release
>
> 31/01/03 11:37a 53,248 thr_test.exe
> 1 File(s) 53,248 bytes
>
> Total Files Listed:
> 44 File(s) 28,103,768 bytes
> 0 Dir(s) 24,246,353,920 bytes free
>
> E:\mysql-3.23.55>
>
> In the morning, I started the server Daemon
> (E:\mysql-3.23.55\client_release>mysqld-max-nt.exe in my case).
>
> You can connect to it. You can query it. Whatever. No cygwin needed.
> No Mingw. No nothing. Build in Win32. Run in Win32. It's a pure,
> native Win32 application.
>
> Just so that everyone understands about MySQL --> the [current release]
> Windows port is definitely, positively a native Win32 application that
> needs no outside utilities to build, setup, run, or administrate. You
> can all stop guessing.
>
> Now, as far as the Win32 animosity goes, I think that is a natural thing
> too. There is a culture clash between the Linux camps and the Win32
> camps. Typically, it's the highly intelligent kids recently out of
> college that are in love with Linux, and the [usually older] corporate
> types that know nothing but Win32. But realize that both sets of people
> have real problems to solve and a free, high quality database will be a
> great help to anyone.
>
> Microsoft *has* done some really scuzzy things (STAK springs to mind).
> But the people who just want to use the MS tools to get work done are
> usually pretty well innocent of misbehavior. They just want to solve
> their business problems. I think it would be good to keep that sort of
> separation in mind.
>
> IMO-YMMV.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)