Thread: Re: [mail] Re: 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, *.exeVolume 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.
On Friday 31 January 2003 20:22, Dann Corbit wrote: > 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. :-) The *BSD, Solaris, AIS, HP-UX, IRIX, SCO, and other unixoid partisans out there will just love this statement. The linux community here is in the minority, more than likely, to the *BSD camp. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11
Like it or not, if PG releases a very good Win32 port, ALL the unixoids combined will be out numbered by the windoze users. Lamar Owen wrote: >On Friday 31 January 2003 20:22, Dann Corbit wrote: > > >>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. >> >> > >:-) > >The *BSD, Solaris, AIS, HP-UX, IRIX, SCO, and other unixoid partisans out >there will just love this statement. > >The linux community here is in the minority, more than likely, to the *BSD >camp. > >
mlw <pgsql@mohawksoft.com> writes:
> Like it or not, if PG releases a very good Win32 port, ALL the unixoids
> combined will be out numbered by the windoze users.
A lot of us are *not* looking forward to that prospect.
regards, tom lane
Tom Lane wrote: >mlw <pgsql@mohawksoft.com> writes: > > >>Like it or not, if PG releases a very good Win32 port, ALL the unixoids >>combined will be out numbered by the windoze users. >> >> > >A lot of us are *not* looking forward to that prospect. > > regards, tom lane > > > No doubt to that, but, depending on how good "the" PG guys are, it is either a blessing or a curse. I think that PG has a REAL chance to be one of "THE" breakthrough open source technologies. With the exception of OpenOffice, I don't think there is a more important open source project than PG. Simply because SQL databases are a cooperative monopoly. MS, Oracle, and DB2 are like the record companies. They have a cooperative monopoly. Yea, they will seem to compete on price, but none of them really whant to know how low the other will go. Some may argue that Apache or PHP may take second place, but I submit that Apache and PHP are, by and large, much less expensive and much less generic products as an ACID compliant SQL databases. That being said, if a good Win32 port is made, AND it becomes common knkowledge, the use count may square.
On Fri, 31 Jan 2003, mlw wrote: > Like it or not, if PG releases a very good Win32 port, ALL the unixoids > combined will be out numbered by the windoze users. Now that's certainly something to look forward to. Vince. -- Fast, inexpensive internet service 56k and beyond! http://www.pop4.net/ http://www.meanstreamradio.com http://www.unknown-artists.com Internet radio: It's not file sharing, it's just radio.
On Fri, 2003-01-31 at 19:22, Dann Corbit wrote: > For MySQL: > There is no Cygwin needed. Period. > Any idea as to why we seem to be getting such a conflicting story here? By several accounts, it does. Now, your saying it doesn't. What the heck is going on here. Not that I'm doubting you. I'm just trying to figure out which side of the coin is the shinny one. ;) There's a tool that comes with either the resource kit or the VC++ stuff that will tell you information like what ldd does. I don't recall the name of the tool. Can anyone comment if cygwin (or equivalent) is being linked in (statically or dynamically)? -- Greg Copeland <greg@copelandconsulting.net> Copeland Computer Consulting
IMHO, replication, performance improvements, cross-db queries, etc is much better use of time than Windows port. --- Dann Corbit <DCorbit@connx.com> wrote: > For MySQL: > There is no Cygwin needed. Period. > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
On Fri, 2003-01-31 at 19:22, Dann Corbit wrote: > For MySQL: > There is no Cygwin needed. Period. Sorry to followup again, but I did want to point out something. I'm assuming you actually installed it. Please take note that the cygwin dll is normally installed into one of the window's directories (system, windows, etc). My point being, just because you didn't find it in the mysql directory, doesn't mean it wasn't installed system-wide. Not saying it does or doesn't do this. Just offering something else that may need to be looked at. Regards, -- Greg Copeland <greg@copelandconsulting.net> Copeland Computer Consulting
On Fri, Jan 31, 2003 at 22:30:45 -0800, ow <oneway_111@yahoo.com> wrote: > IMHO, replication, performance improvements, cross-db queries, etc is > much better use of time than Windows port. Welcome to open source where individual people get to decide what is most important to spend their time on.
> IMHO, replication, performance improvements, cross-db queries, etc is > much better use of time than Windows port. Because you don't use Windows. On a personal level, I couldn't agree more. But I have been in a project where they chose MySQL because it had to run on Windows. I would like to be able to propose a free alternative. -- Kaare Rasmussen --Linux, spil,-- Tlf: 3816 2582 Kaki Data tshirts, merchandize Fax: 3816 2501 Howitzvej 75 Åben 12.00-18.00 Email: kar@kakidata.dk 2000 Frederiksberg Lørdag 12.00-16.00 Web: www.suse.dk
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@connx.com>
To: "Christopher Browne" <cbbrowne@cbbrowne.com>; "Greg Copeland"
<greg@CopelandConsulting.Net>
Cc: "Justin Clift" <justin@postgresql.org>; "Jeff Davis"
<jdavis-pgsql@empires.org>; "PostgresSQL Hackers Mailing List"
<pgsql-hackers@postgresql.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@postgresql.org)
Andrew Dunstan wrote: > 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 am using SRA's Win32 port here on XP, and it doesn't use readline. It does have arrow handling for psql, but does not do Control-A/E handling, nor keep the history between psql invocations. I assume this is what the limited command-line handling they are talking about. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania19073
From: "Bruce Momjian" <pgman@candle.pha.pa.us> > > I am using SRA's Win32 port here on XP, and it doesn't use readline. > > It does have arrow handling for psql, but does not do Control-A/E > handling, nor keep the history between psql invocations. I assume this > is what the limited command-line handling they are talking about. > Probably. But readline is GPL'd (not LGPL'd), so my company can't bundle it or anything that uses it with any non-GPL software we distribute. Similar arguments probably apply to a cygwin based port (not one built using cygwin, but requiring it to run) - IANAL but the company has to err on the side of caution here. andrew