From luislavena at gmail.com Mon Oct 8 23:52:59 2007 From: luislavena at gmail.com (Luis Lavena) Date: Tue, 9 Oct 2007 00:52:59 -0300 Subject: [Rubyinstaller-devel] Buildinf OCI and Ruby-ODBC problems? Message-ID: <71166b3b0710082052p4746e0acicbd4eb01b30f542d@mail.gmail.com> Curt, I'm in the middle of the rebuild process (with p111) and found the issue you're getting with ruby-odbc (0.9995). The following error, is part of the mkmf.log file: have_library_ex: checking for SQLAllocConnect() in -lodbc32... -------------------- no "cl -nologo -Feconftest -I. -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 -ID:/Users/Developer/code/OpenSource/installer-trunk/downloads/ruby-odbc-0.9995 -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 -MD -Zi -O2b2xg- -G6 conftest.c msvcrt-ruby18-static.lib odbc32.lib oldnames.lib user32.lib advapi32.lib ws2_32.lib -link -libpath:"." -libpath:"D:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib" -stack:0x2000000" conftest.c conftest.obj : error LNK2001: unresolved external symbol _SQLAllocConnect conftest.exe : fatal error LNK1120: 1 unresolved externals checked program was: /* begin */ 1: #define WIN32_LEAN_AND_MEAN 2: #include 3: #include 4: #include 5: 6: /*top*/ 7: int main() { return 0; } 8: int t() { void ((*volatile p)()); p = (void ((*)()))SQLAllocConnect; return 0; } /* end */ "cl -nologo -Feconftest -I. -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 -ID:/Users/Developer/code/OpenSource/installer-trunk/downloads/ruby-odbc-0.9995 -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 -MD -Zi -O2b2xg- -G6 conftest.c msvcrt-ruby18-static.lib odbc32.lib oldnames.lib user32.lib advapi32.lib ws2_32.lib -link -libpath:"." -libpath:"D:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib" -stack:0x2000000" conftest.c C:\VC\PSDK-preR2\Include\sqltypes.h(275) : error C2061: syntax error : identifier 'DWORD' C:\VC\PSDK-preR2\Include\sqltypes.h(276) : error C2061: syntax error : identifier 'Data2' C:\VC\PSDK-preR2\Include\sqltypes.h(276) : error C2059: syntax error : ';' C:\VC\PSDK-preR2\Include\sqltypes.h(277) : error C2061: syntax error : identifier 'Data3' C:\VC\PSDK-preR2\Include\sqltypes.h(277) : error C2059: syntax error : ';' C:\VC\PSDK-preR2\Include\sqltypes.h(278) : error C2061: syntax error : identifier 'Data4' C:\VC\PSDK-preR2\Include\sqltypes.h(278) : error C2059: syntax error : ';' C:\VC\PSDK-preR2\Include\sqltypes.h(278) : error C2059: syntax error : '[' C:\VC\PSDK-preR2\Include\sqltypes.h(279) : error C2059: syntax error : '}' conftest.c(5) : error C2198: 'SQLAllocConnect' : too few actual parameters checked program was: /* begin */ 1: #include 2: 3: /*top*/ 4: int main() { return 0; } 5: int t() { SQLAllocConnect(); return 0; } /* end */ -------------------- It seems that the test program is including sql.h with its pre-requisite: windows.h Adding it, I'm getting another error: have_library_ex: checking for SQLAllocConnect() in -lodbc32... -------------------- no "cl -nologo -Feconftest -I. -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 -ID:/Users/Developer/code/OpenSource/installer-trunk/downloads/ruby-odbc-0.9995 -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 -MD -Zi -O2b2xg- -G6 conftest.c msvcrt-ruby18-static.lib odbc32.lib oldnames.lib user32.lib advapi32.lib ws2_32.lib -link -libpath:"." -libpath:"D:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib" -stack:0x2000000" conftest.c conftest.obj : error LNK2001: unresolved external symbol _SQLAllocConnect conftest.exe : fatal error LNK1120: 1 unresolved externals checked program was: /* begin */ 1: #define WIN32_LEAN_AND_MEAN 2: #include 3: #include 4: #include 5: #include 6: 7: /*top*/ 8: int main() { return 0; } 9: int t() { void ((*volatile p)()); p = (void ((*)()))SQLAllocConnect; return 0; } /* end */ "cl -nologo -Feconftest -I. -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 -ID:/Users/Developer/code/OpenSource/installer-trunk/downloads/ruby-odbc-0.9995 -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 -MD -Zi -O2b2xg- -G6 conftest.c msvcrt-ruby18-static.lib odbc32.lib oldnames.lib user32.lib advapi32.lib ws2_32.lib -link -libpath:"." -libpath:"D:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib" -stack:0x2000000" conftest.c conftest.c(6) : error C2198: 'SQLAllocConnect' : too few actual parameters checked program was: /* begin */ 1: #include 2: #include 3: 4: /*top*/ 5: int main() { return 0; } 6: int t() { SQLAllocConnect(); return 0; } /* end */ I need to check "too few actual parameters" (the SQLAllocConnect signature) and see what I could do to fix it. But so far, it seems ruby-odbc is too old for latest SDKs... or we are doing something wrong. What was the error you got? -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From curt.hibbs at gmail.com Tue Oct 9 07:00:56 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Tue, 9 Oct 2007 06:00:56 -0500 Subject: [Rubyinstaller-devel] Buildinf OCI and Ruby-ODBC problems? In-Reply-To: <71166b3b0710082052p4746e0acicbd4eb01b30f542d@mail.gmail.com> References: <71166b3b0710082052p4746e0acicbd4eb01b30f542d@mail.gmail.com> Message-ID: <31d15f490710090400o35e3619g80f114e1974cc265@mail.gmail.com> When I gt the error I commented it out of the rake file just to move on and see if I was going to have any other problems -- I hadn't gone back yet to take a closer look at ruby-odbc. But, I'm pretty sure this is the same error. I upgraded ruby-ocbc for this build to version 0.9995. I haven't tried yet going back to 0.9994, but I'll bet this problem was introduced in 0.9995. I build ruby-odbc 0.9994 six months ago for the last release of OCI without any problems. Curt On 10/8/07, Luis Lavena wrote: > > Curt, > > I'm in the middle of the rebuild process (with p111) and found the > issue you're getting with ruby-odbc (0.9995). > > The following error, is part of the mkmf.log file: > > have_library_ex: checking for SQLAllocConnect() in -lodbc32... > -------------------- no > > "cl -nologo -Feconftest -I. > > -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 > -ID:/Users/Developer/code/OpenSource/installer-trunk/downloads/ruby- > odbc-0.9995 > > -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 > -MD -Zi -O2b2xg- -G6 conftest.c msvcrt-ruby18-static.lib odbc32.lib > oldnames.lib user32.lib advapi32.lib ws2_32.lib -link > -libpath:"." > -libpath:"D:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib" > -stack:0x2000000" > conftest.c > conftest.obj : error LNK2001: unresolved external symbol _SQLAllocConnect > conftest.exe : fatal error LNK1120: 1 unresolved externals > checked program was: > /* begin */ > 1: #define WIN32_LEAN_AND_MEAN > 2: #include > 3: #include > 4: #include > 5: > 6: /*top*/ > 7: int main() { return 0; } > 8: int t() { void ((*volatile p)()); p = (void > ((*)()))SQLAllocConnect; return 0; } > /* end */ > > "cl -nologo -Feconftest -I. > > -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 > -ID:/Users/Developer/code/OpenSource/installer-trunk/downloads/ruby- > odbc-0.9995 > > -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 > -MD -Zi -O2b2xg- -G6 conftest.c msvcrt-ruby18-static.lib odbc32.lib > oldnames.lib user32.lib advapi32.lib ws2_32.lib -link > -libpath:"." > -libpath:"D:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib" > -stack:0x2000000" > conftest.c > C:\VC\PSDK-preR2\Include\sqltypes.h(275) : error C2061: syntax error : > identifier 'DWORD' > C:\VC\PSDK-preR2\Include\sqltypes.h(276) : error C2061: syntax error : > identifier 'Data2' > C:\VC\PSDK-preR2\Include\sqltypes.h(276) : error C2059: syntax error : ';' > C:\VC\PSDK-preR2\Include\sqltypes.h(277) : error C2061: syntax error : > identifier 'Data3' > C:\VC\PSDK-preR2\Include\sqltypes.h(277) : error C2059: syntax error : ';' > C:\VC\PSDK-preR2\Include\sqltypes.h(278) : error C2061: syntax error : > identifier 'Data4' > C:\VC\PSDK-preR2\Include\sqltypes.h(278) : error C2059: syntax error : ';' > C:\VC\PSDK-preR2\Include\sqltypes.h(278) : error C2059: syntax error : '[' > C:\VC\PSDK-preR2\Include\sqltypes.h(279) : error C2059: syntax error : '}' > conftest.c(5) : error C2198: 'SQLAllocConnect' : too few actual parameters > checked program was: > /* begin */ > 1: #include > 2: > 3: /*top*/ > 4: int main() { return 0; } > 5: int t() { SQLAllocConnect(); return 0; } > /* end */ > > -------------------- > > > It seems that the test program is including sql.h with its > pre-requisite: windows.h > > Adding it, I'm getting another error: > > have_library_ex: checking for SQLAllocConnect() in -lodbc32... > -------------------- no > > "cl -nologo -Feconftest -I. > > -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 > -ID:/Users/Developer/code/OpenSource/installer-trunk/downloads/ruby- > odbc-0.9995 > > -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 > -MD -Zi -O2b2xg- -G6 conftest.c msvcrt-ruby18-static.lib odbc32.lib > oldnames.lib user32.lib advapi32.lib ws2_32.lib -link > -libpath:"." > -libpath:"D:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib" > -stack:0x2000000" > conftest.c > conftest.obj : error LNK2001: unresolved external symbol _SQLAllocConnect > conftest.exe : fatal error LNK1120: 1 unresolved externals > checked program was: > /* begin */ > 1: #define WIN32_LEAN_AND_MEAN > 2: #include > 3: #include > 4: #include > 5: #include > 6: > 7: /*top*/ > 8: int main() { return 0; } > 9: int t() { void ((*volatile p)()); p = (void > ((*)()))SQLAllocConnect; return 0; } > /* end */ > > "cl -nologo -Feconftest -I. > > -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 > -ID:/Users/Developer/code/OpenSource/installer-trunk/downloads/ruby- > odbc-0.9995 > > -ID:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib/ruby/1.8/i386-mswin32 > -MD -Zi -O2b2xg- -G6 conftest.c msvcrt-ruby18-static.lib odbc32.lib > oldnames.lib user32.lib advapi32.lib ws2_32.lib -link > -libpath:"." > -libpath:"D:/Users/Developer/code/OpenSource/installer-trunk/ruby/lib" > -stack:0x2000000" > conftest.c > conftest.c(6) : error C2198: 'SQLAllocConnect' : too few actual parameters > checked program was: > /* begin */ > 1: #include > 2: #include > 3: > 4: /*top*/ > 5: int main() { return 0; } > 6: int t() { SQLAllocConnect(); return 0; } > /* end */ > > > I need to check "too few actual parameters" (the SQLAllocConnect > signature) and see what I could do to fix it. > > But so far, it seems ruby-odbc is too old for latest SDKs... or we are > doing something wrong. > > What was the error you got? > > -- > Luis Lavena > Multimedia systems > - > Leaders are made, they are not born. They are made by hard effort, > which is the price which all of us must pay to achieve any goal that > is worthwhile. > Vince Lombardi > _______________________________________________ > Rubyinstaller-devel mailing list > Rubyinstaller-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071009/a060420d/attachment-0001.html From luislavena at gmail.com Tue Oct 9 10:39:09 2007 From: luislavena at gmail.com (Luis Lavena) Date: Tue, 9 Oct 2007 11:39:09 -0300 Subject: [Rubyinstaller-devel] Buildinf OCI and Ruby-ODBC problems? In-Reply-To: <31d15f490710090400o35e3619g80f114e1974cc265@mail.gmail.com> References: <71166b3b0710082052p4746e0acicbd4eb01b30f542d@mail.gmail.com> <31d15f490710090400o35e3619g80f114e1974cc265@mail.gmail.com> Message-ID: <71166b3b0710090739n3ed3d78djf10a6217333c1167@mail.gmail.com> On 10/9/07, Curt Hibbs wrote: > When I gt the error I commented it out of the rake file just to move on and > see if I was going to have any other problems -- I hadn't gone back yet to > take a closer look at ruby-odbc. But, I'm pretty sure this is the same > error. > > I upgraded ruby-ocbc for this build to version 0.9995. I haven't tried yet > going back to 0.9994, but I'll bet this problem was introduced in 0.9995. I > build ruby-odbc 0.9994 six months ago for the last release of OCI without > any problems. > I'll give it a whirl later today, since I'm leaving office to a customer meeting. I'll let you know the results. BTW, I'm thinking conducting a anonymous online survey (like the one railsforge ppl started, but it seems down right now). I want to gather more information about the platform (which version of windows), the average user and the commonly used tools with ruby (also if its a gem developer, etc.) That will give us a nice collection of information to analyze and determine the best way to implement the future version of OCI. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From luislavena at gmail.com Wed Oct 10 20:32:59 2007 From: luislavena at gmail.com (Luis Lavena) Date: Wed, 10 Oct 2007 21:32:59 -0300 Subject: [Rubyinstaller-devel] Buildinf OCI and Ruby-ODBC problems? In-Reply-To: <31d15f490710090400o35e3619g80f114e1974cc265@mail.gmail.com> References: <71166b3b0710082052p4746e0acicbd4eb01b30f542d@mail.gmail.com> <31d15f490710090400o35e3619g80f114e1974cc265@mail.gmail.com> Message-ID: <71166b3b0710101732u6b08c758u17f9580217f8ac1b@mail.gmail.com> On 10/9/07, Curt Hibbs wrote: > When I gt the error I commented it out of the rake file just to move on and > see if I was going to have any other problems -- I hadn't gone back yet to > take a closer look at ruby-odbc. But, I'm pretty sure this is the same > error. > > I upgraded ruby-ocbc for this build to version 0.9995. I haven't tried yet > going back to 0.9994, but I'll bet this problem was introduced in 0.9995. I > build ruby-odbc 0.9994 six months ago for the last release of OCI without > any problems. > 0.9994 or 0.9995 makes no difference. The problem still exist. The thing is that including sql.h default to ODBC 0x350 (3.5 of ODBC) and according to MSDN documentation, SQLAllocConnect has been deprecated: http://msdn2.microsoft.com/en-us/library//ms714852.aspx Errr... to confusing to get why the linking error is there, even when I'm linking with odbc32.lib "error LNK2001: unresolved external symbol _SQLAllocConnect" Tried with and without SDK set in INCLUDE and LIB, all without success. So far, the only condition failing is: have_library_ex("odbc32", "SQLAllocConnect", "sql.h") I'll try to find why isn't finding the function and reply here. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From luislavena at gmail.com Wed Oct 10 21:06:10 2007 From: luislavena at gmail.com (Luis Lavena) Date: Wed, 10 Oct 2007 22:06:10 -0300 Subject: [Rubyinstaller-devel] Buildinf OCI and Ruby-ODBC problems? In-Reply-To: <71166b3b0710101732u6b08c758u17f9580217f8ac1b@mail.gmail.com> References: <71166b3b0710082052p4746e0acicbd4eb01b30f542d@mail.gmail.com> <31d15f490710090400o35e3619g80f114e1974cc265@mail.gmail.com> <71166b3b0710101732u6b08c758u17f9580217f8ac1b@mail.gmail.com> Message-ID: <71166b3b0710101806m7177e42bje8581faf2e017beb@mail.gmail.com> On 10/10/07, Luis Lavena wrote: > So far, the only condition failing is: > > have_library_ex("odbc32", "SQLAllocConnect", "sql.h") > > I'll try to find why isn't finding the function and reply here. > Found the problem. Example program: /* begin */ #define WIN32_LEAN_AND_MEAN #include #include #include /*top*/ int main() { return 0; } int t() { void ((*volatile p)()); p = (void ((*)()))SQLAllocConnect; return 0; } /* end */ FAILS... missing _SQLAllocConnect Removing the WIN32_LEAN_AND_MEAN works... The problem is that WIN32_LEAN_AND_MEAN came from Config::CONFIG['COMMON_MACROS']: ruby -v -rrbconfig -e 'puts Config::CONFIG["COMMON_MACROS"]' ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] WIN32_LEAN_AND_MEAN Since adding the common macros is part of mkmf.rb, I can't change that without breaking everything. I'll post this to Ruby-Core looking for solutions. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From luislavena at gmail.com Wed Oct 10 22:07:48 2007 From: luislavena at gmail.com (Luis Lavena) Date: Wed, 10 Oct 2007 23:07:48 -0300 Subject: [Rubyinstaller-devel] Buildinf OCI and Ruby-ODBC problems? In-Reply-To: <71166b3b0710101806m7177e42bje8581faf2e017beb@mail.gmail.com> References: <71166b3b0710082052p4746e0acicbd4eb01b30f542d@mail.gmail.com> <31d15f490710090400o35e3619g80f114e1974cc265@mail.gmail.com> <71166b3b0710101732u6b08c758u17f9580217f8ac1b@mail.gmail.com> <71166b3b0710101806m7177e42bje8581faf2e017beb@mail.gmail.com> Message-ID: <71166b3b0710101907r1933fdacy96301995c617e5c@mail.gmail.com> On 10/10/07, Luis Lavena wrote: > > The problem is that WIN32_LEAN_AND_MEAN came from > Config::CONFIG['COMMON_MACROS']: > > ruby -v -rrbconfig -e 'puts Config::CONFIG["COMMON_MACROS"]' > ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] > WIN32_LEAN_AND_MEAN > > Since adding the common macros is part of mkmf.rb, I can't change that > without breaking everything. > > I'll post this to Ruby-Core looking for solutions. > Done. It seems was added in 1.8.6: D:\Users\Developer>ruby -v -rrbconfig -e 'puts Config::CONFIG["COMMON_MACROS"]' ruby 1.8.5 (2007-09-24 patchlevel 114) [i386-mswin32] nil D:\Users\Developer>ruby -v -rrbconfig -e 'puts Config::CONFIG["COMMON_MACROS"]' ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] WIN32_LEAN_AND_MEAN === I'll try to find where is defined (guess is part of the makefile). Two options: 1) Raise the attention of Ruby/ODBC developer and find a workaround (need more information about try_func and how to define my own C code). 2) Make Ruby-Core provide more information about the switch, since couldn't find it. Taking care of this tomorrow. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From curt.hibbs at gmail.com Wed Oct 10 23:37:20 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Wed, 10 Oct 2007 22:37:20 -0500 Subject: [Rubyinstaller-devel] Buildinf OCI and Ruby-ODBC problems? In-Reply-To: <71166b3b0710101907r1933fdacy96301995c617e5c@mail.gmail.com> References: <71166b3b0710082052p4746e0acicbd4eb01b30f542d@mail.gmail.com> <31d15f490710090400o35e3619g80f114e1974cc265@mail.gmail.com> <71166b3b0710101732u6b08c758u17f9580217f8ac1b@mail.gmail.com> <71166b3b0710101806m7177e42bje8581faf2e017beb@mail.gmail.com> <71166b3b0710101907r1933fdacy96301995c617e5c@mail.gmail.com> Message-ID: <31d15f490710102037ta833e47qae2c1ce862fd2bfa@mail.gmail.com> I still can't understand why it would have built ok back in March??? Oh well, thanks for looking in to this. Curt On 10/10/07, Luis Lavena wrote: > > On 10/10/07, Luis Lavena wrote: > > > > The problem is that WIN32_LEAN_AND_MEAN came from > > Config::CONFIG['COMMON_MACROS']: > > > > ruby -v -rrbconfig -e 'puts Config::CONFIG["COMMON_MACROS"]' > > ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] > > WIN32_LEAN_AND_MEAN > > > > Since adding the common macros is part of mkmf.rb, I can't change that > > without breaking everything. > > > > I'll post this to Ruby-Core looking for solutions. > > > > Done. > > It seems was added in 1.8.6: > > D:\Users\Developer>ruby -v -rrbconfig -e 'puts > Config::CONFIG["COMMON_MACROS"]' > ruby 1.8.5 (2007-09-24 patchlevel 114) [i386-mswin32] > nil > > D:\Users\Developer>ruby -v -rrbconfig -e 'puts > Config::CONFIG["COMMON_MACROS"]' > ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] > WIN32_LEAN_AND_MEAN > > === > > I'll try to find where is defined (guess is part of the makefile). > > Two options: > > 1) Raise the attention of Ruby/ODBC developer and find a workaround > (need more information about try_func and how to define my own C > code). > > 2) Make Ruby-Core provide more information about the switch, since > couldn't find it. > > Taking care of this tomorrow. > > -- > Luis Lavena > Multimedia systems > - > Leaders are made, they are not born. They are made by hard effort, > which is the price which all of us must pay to achieve any goal that > is worthwhile. > Vince Lombardi > _______________________________________________ > Rubyinstaller-devel mailing list > Rubyinstaller-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071010/4a8e43c7/attachment.html From luislavena at gmail.com Wed Oct 10 23:45:03 2007 From: luislavena at gmail.com (Luis Lavena) Date: Thu, 11 Oct 2007 00:45:03 -0300 Subject: [Rubyinstaller-devel] Buildinf OCI and Ruby-ODBC problems? In-Reply-To: <31d15f490710102037ta833e47qae2c1ce862fd2bfa@mail.gmail.com> References: <71166b3b0710082052p4746e0acicbd4eb01b30f542d@mail.gmail.com> <31d15f490710090400o35e3619g80f114e1974cc265@mail.gmail.com> <71166b3b0710101732u6b08c758u17f9580217f8ac1b@mail.gmail.com> <71166b3b0710101806m7177e42bje8581faf2e017beb@mail.gmail.com> <71166b3b0710101907r1933fdacy96301995c617e5c@mail.gmail.com> <31d15f490710102037ta833e47qae2c1ce862fd2bfa@mail.gmail.com> Message-ID: <71166b3b0710102045p7d46b882w94b13013584845@mail.gmail.com> On 10/11/07, Curt Hibbs wrote: > I still can't understand why it would have built ok back in March??? > > Oh well, thanks for looking in to this. > Curt, is confirmed: Is a problem of 1.8.6 and Platform SDK issues. 1.8.5 didn't show this since COMMON_MACROS wasn't set at all. This is the message I sent to Ruby-Core: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/12584 And Nobu reply: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/12586 I'll try that tomorrow since I'm at home right now. Regards, BTW: could you configure the mailing list to just reply to the list? I forget to remove you when I hit the reply button. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From curt.hibbs at gmail.com Thu Oct 11 09:26:53 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Thu, 11 Oct 2007 08:26:53 -0500 Subject: [Rubyinstaller-devel] Buildinf OCI and Ruby-ODBC problems? In-Reply-To: <71166b3b0710102045p7d46b882w94b13013584845@mail.gmail.com> References: <71166b3b0710082052p4746e0acicbd4eb01b30f542d@mail.gmail.com> <31d15f490710090400o35e3619g80f114e1974cc265@mail.gmail.com> <71166b3b0710101732u6b08c758u17f9580217f8ac1b@mail.gmail.com> <71166b3b0710101806m7177e42bje8581faf2e017beb@mail.gmail.com> <71166b3b0710101907r1933fdacy96301995c617e5c@mail.gmail.com> <31d15f490710102037ta833e47qae2c1ce862fd2bfa@mail.gmail.com> <71166b3b0710102045p7d46b882w94b13013584845@mail.gmail.com> Message-ID: <31d15f490710110626h6cc4637bl4130e629c6248f35@mail.gmail.com> On 10/10/07, Luis Lavena wrote: > > On 10/11/07, Curt Hibbs wrote: > > I still can't understand why it would have built ok back in March??? > > > > Oh well, thanks for looking in to this. > > > > Curt, is confirmed: > > Is a problem of 1.8.6 and Platform SDK issues. > > 1.8.5 didn't show this since COMMON_MACROS wasn't set at all. > > This is the message I sent to Ruby-Core: > http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/12584 > > And Nobu reply: > > http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/12586 > > I'll try that tomorrow since I'm at home right now. > > Regards, > > BTW: could you configure the mailing list to just reply to the list? I > forget to remove you when I hit the reply button. Done! BTW, the admin password for all the OCI mailing lists is "pancakes". Curt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071011/a2f5ece2/attachment.html From curt.hibbs at gmail.com Thu Oct 11 09:31:32 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Thu, 11 Oct 2007 08:31:32 -0500 Subject: [Rubyinstaller-devel] Buildinf OCI and Ruby-ODBC problems? In-Reply-To: <31d15f490710110626h6cc4637bl4130e629c6248f35@mail.gmail.com> References: <71166b3b0710082052p4746e0acicbd4eb01b30f542d@mail.gmail.com> <31d15f490710090400o35e3619g80f114e1974cc265@mail.gmail.com> <71166b3b0710101732u6b08c758u17f9580217f8ac1b@mail.gmail.com> <71166b3b0710101806m7177e42bje8581faf2e017beb@mail.gmail.com> <71166b3b0710101907r1933fdacy96301995c617e5c@mail.gmail.com> <31d15f490710102037ta833e47qae2c1ce862fd2bfa@mail.gmail.com> <71166b3b0710102045p7d46b882w94b13013584845@mail.gmail.com> <31d15f490710110626h6cc4637bl4130e629c6248f35@mail.gmail.com> Message-ID: <31d15f490710110631i69569bdcte95f9a06041ec263@mail.gmail.com> On 10/11/07, Curt Hibbs wrote: > > On 10/10/07, Luis Lavena wrote: > > > > On 10/11/07, Curt Hibbs wrote: > > > I still can't understand why it would have built ok back in March??? > > > > > > Oh well, thanks for looking in to this. > > > > > > > Curt, is confirmed: > > > > Is a problem of 1.8.6 and Platform SDK issues. > > > > 1.8.5 didn't show this since COMMON_MACROS wasn't set at all. > > > > This is the message I sent to Ruby-Core: > > http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/12584 > > > > And Nobu reply: > > > > http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/12586 > > > > I'll try that tomorrow since I'm at home right now. > > > > Regards, > > > > BTW: could you configure the mailing list to just reply to the list? I > > forget to remove you when I hit the reply button. > > > Done! BTW, the admin password for all the OCI mailing lists is "pancakes". > > I meant to send that only to Luis. :-( Luis, I just changed the password and I'll send it to you off list. Curt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071011/14a8aa01/attachment-0001.html From luislavena at gmail.com Fri Oct 12 00:29:16 2007 From: luislavena at gmail.com (Luis Lavena) Date: Fri, 12 Oct 2007 01:29:16 -0300 Subject: [Rubyinstaller-devel] The Future One-Click Ruby Installer In-Reply-To: <31d15f490710111907s577b045j262e6ec738b8bb7e@mail.gmail.com> References: <31d15f490710072030y6fdbc287n685175eb7b7fb64a@mail.gmail.com> <71166b3b0710080707s6b880a87ma6d714a09e1d900e@mail.gmail.com> <31d15f490710081011n14be7946l63cec0d27e3c143d@mail.gmail.com> <31d15f490710102039x3cd94214l6bfc0b513cf1cd13@mail.gmail.com> <1192112457.6702.9.camel@sohma> <31d15f490710111906v11fe4cf9p26a5e6709c7a6907@mail.gmail.com> <31d15f490710111907s577b045j262e6ec738b8bb7e@mail.gmail.com> Message-ID: <71166b3b0710112129w45d4d6a0ydb4717e8d53e12d2@mail.gmail.com> On 10/11/07, Curt Hibbs wrote: > I hit reply instead of reply-all, so you didn't get thos. > > curt > I was setting p111 locally, but didn't commit the change until workaround the ruby-odbc issue. It seems is fixed in the ruby-1.8 stable branch. In the mean time, I'm creating a patch for ruby-odbc 0.9995 to fix the extconf.rb issue. I'll try to commit the .diff tomorrow and continue testing the build process until I get it right. I guess will spend my weekend on this and start drafting what questions will contain the survey. Don't want to delay that too much after the OCI release next week. (I'm a very positive kind of person) ;-) Good weekend everybody. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From curt.hibbs at gmail.com Fri Oct 12 08:36:48 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Fri, 12 Oct 2007 07:36:48 -0500 Subject: [Rubyinstaller-devel] The Future One-Click Ruby Installer In-Reply-To: <71166b3b0710112129w45d4d6a0ydb4717e8d53e12d2@mail.gmail.com> References: <31d15f490710072030y6fdbc287n685175eb7b7fb64a@mail.gmail.com> <71166b3b0710080707s6b880a87ma6d714a09e1d900e@mail.gmail.com> <31d15f490710081011n14be7946l63cec0d27e3c143d@mail.gmail.com> <31d15f490710102039x3cd94214l6bfc0b513cf1cd13@mail.gmail.com> <1192112457.6702.9.camel@sohma> <31d15f490710111906v11fe4cf9p26a5e6709c7a6907@mail.gmail.com> <31d15f490710111907s577b045j262e6ec738b8bb7e@mail.gmail.com> <71166b3b0710112129w45d4d6a0ydb4717e8d53e12d2@mail.gmail.com> Message-ID: <31d15f490710120536p3f43e886ke29a65452c6a6943@mail.gmail.com> On 10/11/07, Luis Lavena wrote: > > On 10/11/07, Curt Hibbs wrote: > > I hit reply instead of reply-all, so you didn't get thos. > > > > curt > > > > I was setting p111 locally, but didn't commit the change until > workaround the ruby-odbc issue. > > It seems is fixed in the ruby-1.8 stable branch. In the mean time, I'm > creating a patch for ruby-odbc 0.9995 to fix the extconf.rb issue. > > I'll try to commit the .diff tomorrow and continue testing the build > process until I get it right. > > I guess will spend my weekend on this and start drafting what > questions will contain the survey. Don't want to delay that too much > after the OCI release next week. > > (I'm a very positive kind of person) ;-) > > Good weekend everybody. > Excellent! Curt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071012/e3d32875/attachment.html From luislavena at gmail.com Sat Oct 13 21:21:11 2007 From: luislavena at gmail.com (Luis Lavena) Date: Sat, 13 Oct 2007 22:21:11 -0300 Subject: [Rubyinstaller-devel] Ruby-ODBC issues fixed. Message-ID: <71166b3b0710131821h6b93a7fcvd8143ee473c84d6d@mail.gmail.com> Hello List, I've committed a patch to the rakefile (and the utils) that allow inline patching of files like the case we are dealing right now. Also, I'll like to point that Ruby Core developers fixed the issue we found in the stable and trunk branches, so these problems will go away in future releases. Curt, as you said before, the building process is too brittle and it requires more testing. I guess that RubyInstaller 3.0 (the successor after this) will be more modular allowing us extending and removing parts of it (like which version of ruby ship). All this process allow me gather information :-) Good weekend everybody. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From curt.hibbs at gmail.com Mon Oct 15 17:13:59 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Mon, 15 Oct 2007 16:13:59 -0500 Subject: [Rubyinstaller-devel] Ruby-ODBC issues fixed. In-Reply-To: <71166b3b0710131821h6b93a7fcvd8143ee473c84d6d@mail.gmail.com> References: <71166b3b0710131821h6b93a7fcvd8143ee473c84d6d@mail.gmail.com> Message-ID: <31d15f490710151413v64b77061u5980573c4808223d@mail.gmail.com> On 10/13/07, Luis Lavena wrote: > > Hello List, > > I've committed a patch to the rakefile (and the utils) that allow > inline patching of files like the case we are dealing right now. Excellent! I'll update my copy and do a build. If everything goes alright we can put out a release candidate. Also, I'll like to point that Ruby Core developers fixed the issue we > found in the stable and trunk branches, so these problems will go away > in future releases. > > Curt, as you said before, the building process is too brittle and it > requires more testing. > > I guess that RubyInstaller 3.0 (the successor after this) will be more > modular allowing us extending and removing parts of it (like which > version of ruby ship). Yes, yes, yes! I knew we'd have to deal with the compiler issue sometime, and figured that would be a good time to improve the build process. Curt All this process allow me gather information :-) > > Good weekend everybody. > > -- > Luis Lavena > Multimedia systems > - > Leaders are made, they are not born. They are made by hard effort, > which is the price which all of us must pay to achieve any goal that > is worthwhile. > Vince Lombardi > _______________________________________________ > Rubyinstaller-devel mailing list > Rubyinstaller-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071015/e2e08aa3/attachment.html From curt.hibbs at gmail.com Mon Oct 15 17:23:55 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Mon, 15 Oct 2007 16:23:55 -0500 Subject: [Rubyinstaller-devel] Ruby-ODBC issues fixed. In-Reply-To: <31d15f490710151413v64b77061u5980573c4808223d@mail.gmail.com> References: <71166b3b0710131821h6b93a7fcvd8143ee473c84d6d@mail.gmail.com> <31d15f490710151413v64b77061u5980573c4808223d@mail.gmail.com> Message-ID: <31d15f490710151423m67ad2043h2c84a4fac6de8208@mail.gmail.com> Also, I'm thinking that we might want to wait for RubyGems 0.9.5 before doing a final OCI release (it'd be nice to have the latest RubyGems release in there). Curt On 10/15/07, Curt Hibbs wrote: > > On 10/13/07, Luis Lavena wrote: > > > > Hello List, > > > > I've committed a patch to the rakefile (and the utils) that allow > > inline patching of files like the case we are dealing right now. > > > Excellent! I'll update my copy and do a build. If everything goes alright > we can put out a release candidate. > > Also, I'll like to point that Ruby Core developers fixed the issue we > > found in the stable and trunk branches, so these problems will go away > > in future releases. > > > > Curt, as you said before, the building process is too brittle and it > > requires more testing. > > > > I guess that RubyInstaller 3.0 (the successor after this) will be more > > modular allowing us extending and removing parts of it (like which > > version of ruby ship). > > > Yes, yes, yes! > > I knew we'd have to deal with the compiler issue sometime, and figured > that would be a good time to improve the build process. > > Curt > > All this process allow me gather information :-) > > > > Good weekend everybody. > > > > -- > > Luis Lavena > > Multimedia systems > > - > > Leaders are made, they are not born. They are made by hard effort, > > which is the price which all of us must pay to achieve any goal that > > is worthwhile. > > Vince Lombardi > > _______________________________________________ > > Rubyinstaller-devel mailing list > > Rubyinstaller-devel at rubyforge.org > > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071015/9bee1a90/attachment.html From luislavena at gmail.com Mon Oct 15 18:27:57 2007 From: luislavena at gmail.com (Luis Lavena) Date: Mon, 15 Oct 2007 19:27:57 -0300 Subject: [Rubyinstaller-devel] Ruby-ODBC issues fixed. In-Reply-To: <31d15f490710151423m67ad2043h2c84a4fac6de8208@mail.gmail.com> References: <71166b3b0710131821h6b93a7fcvd8143ee473c84d6d@mail.gmail.com> <31d15f490710151413v64b77061u5980573c4808223d@mail.gmail.com> <31d15f490710151423m67ad2043h2c84a4fac6de8208@mail.gmail.com> Message-ID: <71166b3b0710151527nc540f1ai44b157a7c17effa6@mail.gmail.com> On 10/15/07, Curt Hibbs wrote: > Also, I'm thinking that we might want to wait for RubyGems 0.9.5 before > doing a final OCI release (it'd be nice to have the latest RubyGems release > in there). > Yes, that's why I'm beta-testing and nuking my ruby installation here trying the new platform specs and building gems with it. We will require removing the patching of .cmd scripts for rubygems, since that method brakes IDE integrations like NetBeans and Aptana. (they are looking for "gem" and not gem.cmd). -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From curt.hibbs at gmail.com Mon Oct 15 19:35:29 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Mon, 15 Oct 2007 18:35:29 -0500 Subject: [Rubyinstaller-devel] Ruby-ODBC issues fixed. In-Reply-To: <71166b3b0710151527nc540f1ai44b157a7c17effa6@mail.gmail.com> References: <71166b3b0710131821h6b93a7fcvd8143ee473c84d6d@mail.gmail.com> <31d15f490710151413v64b77061u5980573c4808223d@mail.gmail.com> <31d15f490710151423m67ad2043h2c84a4fac6de8208@mail.gmail.com> <71166b3b0710151527nc540f1ai44b157a7c17effa6@mail.gmail.com> Message-ID: <31d15f490710151635u4cf54c7dm2edc847b0208dbe1@mail.gmail.com> On 10/15/07, Luis Lavena wrote: > > > We will require removing the patching of .cmd scripts for rubygems, > since that method brakes IDE integrations like NetBeans and Aptana. > (they are looking for "gem" and not gem.cmd). I already stopped doing that because of the IDE integration problem. The last release of OCI uses path-independent bat files (not cmd files) and on the original ruby files (without extentions). So, for example, in OCI 1/8/6-25 you'll find "gem" and "gem.bat". Curt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071015/e311dc91/attachment.html From luislavena at gmail.com Mon Oct 15 19:40:14 2007 From: luislavena at gmail.com (Luis Lavena) Date: Mon, 15 Oct 2007 20:40:14 -0300 Subject: [Rubyinstaller-devel] Ruby-ODBC issues fixed. In-Reply-To: <31d15f490710151635u4cf54c7dm2edc847b0208dbe1@mail.gmail.com> References: <71166b3b0710131821h6b93a7fcvd8143ee473c84d6d@mail.gmail.com> <31d15f490710151413v64b77061u5980573c4808223d@mail.gmail.com> <31d15f490710151423m67ad2043h2c84a4fac6de8208@mail.gmail.com> <71166b3b0710151527nc540f1ai44b157a7c17effa6@mail.gmail.com> <31d15f490710151635u4cf54c7dm2edc847b0208dbe1@mail.gmail.com> Message-ID: <71166b3b0710151640x726ab036te98d245a1997e35b@mail.gmail.com> On 10/15/07, Curt Hibbs wrote: > On 10/15/07, Luis Lavena wrote: > > > > We will require removing the patching of .cmd scripts for rubygems, > > since that method brakes IDE integrations like NetBeans and Aptana. > > (they are looking for "gem" and not gem.cmd). > > I already stopped doing that because of the IDE integration problem. The > last release of OCI uses path-independent bat files (not cmd files) and on > the original ruby files (without extentions). So, for example, in OCI > 1/8/6-25 you'll find "gem" and " gem.bat". > Great, I missed that part :-P Anyway, hope next rubygems sport a patch for the windows script stubs [1]. Let me know if ruby-odbc is ok and else is broken ;-) [1] http://rubyforge.org/tracker/index.php?func=detail&aid=14725&group_id=126&atid=577 -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From curt.hibbs at gmail.com Thu Oct 18 09:53:45 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Thu, 18 Oct 2007 08:53:45 -0500 Subject: [Rubyinstaller-devel] one click installer thoughts In-Reply-To: <966599840710180650t58d96636ta0fd0ce1f256398@mail.gmail.com> References: <966599840710180650t58d96636ta0fd0ce1f256398@mail.gmail.com> Message-ID: <31d15f490710180653t5ae614ebj20966cca23837248@mail.gmail.com> Thanks for your suggestions, I cc'd this to the developer's list. Curt On 10/18/07, Roger Pack wrote: > > Hi Curt. Thought I'd give some feedback stuffs on one-click after the > latest announcement on the ruby mailing list. > Some random thoughts: > One-click rocks! > It might be worth looking into compiling it with VC8, as apparently it is > speedier (see http://www.ruby-forum.com/topic/59411#new which seemed to > say so at the bottom). > > A suggestion--when it installs I'm still a little lazy and wish that there > were an option 'just overwrite everything in my ruby directory!' maybe with > a warning 'this is dangerous' and 'make sure to turn off any ruby programs' > and 'unspecified results,' or what not. I tried doing that recently (seeing > if ploughing over it resulted in a working distro) and it seems to work > fine. > > A note--it still says still says 185-24 in the folder under "program > files" (I believe). > > And a small suggestion--when I first started using one click I got > confused as to what 185-24 meant in comparison to the ruby core patch > level. "Were they the same?" "What patch level was 185-24 using, anyway?" > That type of thing. It might be helpful to newbies like me if the numbering > sequence were modified slightly, such as 186-26-111 or 186-111-26, so that I > don't get so confused. > > Anyway that's it! Thanks for your work. Worked well (didn't override my > path, and I had pre-existing Ruby). I'm glad to finally have a working ruby > again :) > -- > -Roger Pack > I like belief. http://www.google.com/search?q=free+bible > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071018/c6686936/attachment.html From curt.hibbs at gmail.com Thu Oct 18 14:03:00 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Thu, 18 Oct 2007 13:03:00 -0500 Subject: [Rubyinstaller-devel] Fwd: one click installer thoughts In-Reply-To: <966599840710181049y6e27982am5e0db9f9b5008df4@mail.gmail.com> References: <966599840710180650t58d96636ta0fd0ce1f256398@mail.gmail.com> <31d15f490710180653t5ae614ebj20966cca23837248@mail.gmail.com> <966599840710181049y6e27982am5e0db9f9b5008df4@mail.gmail.com> Message-ID: <31d15f490710181103q69ded3b8t6a5602eff99f8b86@mail.gmail.com> ---------- Forwarded message ---------- From: Roger Pack Date: Oct 18, 2007 12:49 PM Subject: Re: one click installer thoughts To: curt at hibbs.com Cc: RubyInstaller Developers Oops looks like the fastest win32 compiler is ruby 1.8.6 (2007-03-13 patchlevel 0) [i386-mingw32] (gcc 4.2.1-dw2-2) also cc'ed to devs--will probably bounce :) Take care. > It might be worth looking into compiling it with VC8, as apparently it is > > speedier (see http://www.ruby-forum.com/topic/59411#new which seemed to > > say so at the bottom). > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071018/9173a2a1/attachment.html From luislavena at gmail.com Fri Oct 19 00:58:12 2007 From: luislavena at gmail.com (Luis Lavena) Date: Fri, 19 Oct 2007 01:58:12 -0300 Subject: [Rubyinstaller-devel] Fwd: one click installer thoughts In-Reply-To: <31d15f490710181103q69ded3b8t6a5602eff99f8b86@mail.gmail.com> References: <966599840710180650t58d96636ta0fd0ce1f256398@mail.gmail.com> <31d15f490710180653t5ae614ebj20966cca23837248@mail.gmail.com> <966599840710181049y6e27982am5e0db9f9b5008df4@mail.gmail.com> <31d15f490710181103q69ded3b8t6a5602eff99f8b86@mail.gmail.com> Message-ID: <71166b3b0710182158q7ea7a4fejd4d4b54568696591@mail.gmail.com> On 10/18/07, Curt Hibbs wrote: > > > ---------- Forwarded message ---------- > From: Roger Pack > Date: Oct 18, 2007 12:49 PM > Subject: Re: one click installer thoughts > To: curt at hibbs.com > Cc: RubyInstaller Developers > > > Oops looks like the fastest win32 compiler is > ruby 1.8.6 > (2007-03-13 patchlevel 0) [i386-mingw32] (gcc 4.2.1-dw2-2) > > > also cc'ed to devs--will probably bounce :) > Take care. > > Thanks Curt for the update. The thing regarding gcc-4.2.1 is that is Technology Preview in MinGW. What does mean? The stable and inmediate candidates version of GCC under windows (mingw) are 3.x, no plan for inmediate jump/mark as stable the 4.x branch. Since we are trying ot get a better product build under Windows, we should avoid using too bleeding edge stuff. Trying to trace a bug when you don't know if it's the compiler, ruby or the steps you're doing. Anyway, there is a performance compromise like always, and I lested those in the ruby-core thread, but copy & paste here for the reference (since cannot find the ruby-core number for it:P Quote of what I replied to _why about the compilers and the options we have for Windows: ==== So, to summarize we have a few paths: - Keep using VC6 and find workarounds to compile extensions with other compilers (maybe with better documentation for this topic). Pro: we are already there. Con: bad performance and issues with the compiler- - Implement some sort of distutils for ruby Pro: will be good for ruby at the end. Con: will take time and much more to be integrated as part of ruby-core. - Switch to VC8/9. Pro: - Better performance, compiler freely available (in the shape of Visual Studio Express or Windows SDK). - Known x64 support availability, for future developments/switch to 64bits OS -- (There is a Ruby 1.9 build against VC8_x64.) Con: - Requires hacking and fixing of upstream libraries (dependencies) which aren't prepared for it. (gnu tools like readline, iconv, gettext, and so on as example). - Switch to MinGW Pro: will ease the path of getting dependencies build (like the ones cited before). It also link against already known runtime library (msvcrt.dll) which is available in every stable OS since Windows 2000 -- AFAIK. Con: This will also require maintain builds of upstream libraries, even are more simpler to them build. The support for x64 platforms is still under development -- is not part of stable either candidates of current MinGW releases... which is a problem (is another branch of project looking to get integrated). Ok, these are the scenarios, and their good and bad points. for those who every time just reply that "we should stick to MS compilers" in the field I haven't found (excluding the 64bits part) no differences from using MinGW. On the contrary, and thankfuly to the "simple installer" they have, get the correct dev environment is simpler than Microsoft tools. === -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From curt.hibbs at gmail.com Fri Oct 19 09:40:18 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Fri, 19 Oct 2007 08:40:18 -0500 Subject: [Rubyinstaller-devel] Fwd: one click installer thoughts In-Reply-To: <71166b3b0710182158q7ea7a4fejd4d4b54568696591@mail.gmail.com> References: <966599840710180650t58d96636ta0fd0ce1f256398@mail.gmail.com> <31d15f490710180653t5ae614ebj20966cca23837248@mail.gmail.com> <966599840710181049y6e27982am5e0db9f9b5008df4@mail.gmail.com> <31d15f490710181103q69ded3b8t6a5602eff99f8b86@mail.gmail.com> <71166b3b0710182158q7ea7a4fejd4d4b54568696591@mail.gmail.com> Message-ID: <31d15f490710190640t2f6c6f1pfbf099500b6f382e@mail.gmail.com> Good summary, Luis! On 10/18/07, Luis Lavena wrote: > > On 10/18/07, Curt Hibbs wrote: > > > > > > ---------- Forwarded message ---------- > > From: Roger Pack > > Date: Oct 18, 2007 12:49 PM > > Subject: Re: one click installer thoughts > > To: curt at hibbs.com > > Cc: RubyInstaller Developers > > > > > > Oops looks like the fastest win32 compiler is > > ruby 1.8.6 > > (2007-03-13 patchlevel 0) [i386-mingw32] (gcc 4.2.1-dw2-2) > > > > > > also cc'ed to devs--will probably bounce :) > > Take care. > > > > > > Thanks Curt for the update. > > The thing regarding gcc-4.2.1 is that is Technology Preview in MinGW. > > What does mean? > > The stable and inmediate candidates version of GCC under windows > (mingw) are 3.x, no plan for inmediate jump/mark as stable the 4.x > branch. > > Since we are trying ot get a better product build under Windows, we > should avoid using too bleeding edge stuff. > > Trying to trace a bug when you don't know if it's the compiler, ruby > or the steps you're doing. > > Anyway, there is a performance compromise like always, and I lested > those in the ruby-core thread, but copy & paste here for the reference > (since cannot find the ruby-core number for it:P > > Quote of what I replied to _why about the compilers and the options we > have for Windows: > > ==== > So, to summarize we have a few paths: > > - Keep using VC6 and find workarounds to compile extensions with other > compilers (maybe with better documentation for this topic). > Pro: we are already there. > Con: bad performance and issues with the compiler- > > - Implement some sort of distutils for ruby > Pro: will be good for ruby at the end. > Con: will take time and much more to be integrated as part of ruby-core. > > - Switch to VC8/9. > Pro: > - Better performance, compiler freely available (in the shape of > Visual Studio Express or Windows SDK). > - Known x64 support availability, for future developments/switch to > 64bits OS -- (There is a Ruby 1.9 build against VC8_x64.) > Con: > - Requires hacking and fixing of upstream libraries (dependencies) > which aren't prepared for it. > (gnu tools like readline, iconv, gettext, and so on as example). > > - Switch to MinGW > Pro: will ease the path of getting dependencies build (like the ones > cited before). It also link against already known runtime library > (msvcrt.dll) which is available in every stable OS since Windows 2000 > -- AFAIK. > Con: This will also require maintain builds of upstream libraries, > even are more simpler to them build. > The support for x64 platforms is still under development -- is not > part of stable either candidates of current MinGW releases... which is > a problem (is another branch of project looking to get integrated). > > > Ok, these are the scenarios, and their good and bad points. > > for those who every time just reply that "we should stick to MS > compilers" in the field I haven't found (excluding the 64bits part) no > differences from using MinGW. On the contrary, and thankfuly to the > "simple installer" they have, get the correct dev environment is simpler > than > Microsoft tools. > > === > > -- > Luis Lavena > Multimedia systems > - > Leaders are made, they are not born. They are made by hard effort, > which is the price which all of us must pay to achieve any goal that > is worthwhile. > Vince Lombardi > _______________________________________________ > Rubyinstaller-devel mailing list > Rubyinstaller-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071019/6195df62/attachment.html From curt.hibbs at gmail.com Sun Oct 21 21:20:28 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Sun, 21 Oct 2007 20:20:28 -0500 Subject: [Rubyinstaller-devel] Fwd: Ruby Installer Multi User Install In-Reply-To: <068e01c813c5$d470dab0$0403a8c0@douglasthrift.net> References: <068e01c813c5$d470dab0$0403a8c0@douglasthrift.net> Message-ID: <31d15f490710211820t293893c1n54c300d6b16c540d@mail.gmail.com> ---------- Forwarded message ---------- From: Douglas Thrift Date: Oct 21, 2007 4:36 AM Subject: Ruby Installer Multi User Install To: Curt Hibbs Hello, I noticed that the One-Click Ruby Installer for Windows installs its Start Menu items into the Start Menu of the installing user rather than into the All Users one. It looks like this has come up before: http://groups.google.com/group/comp.lang.ruby/msg/9c6e366f4151bb1f It seems that this hasn't been fixed in the current 1.8.6-26 Release Candidate 1 installer. Can it be bumped up on the todo list? I just think it's a minor but important thing. Thanks! _______________________________________________________________________ Douglas William Thrift -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071021/aed44fbf/attachment-0001.html From rogerpack2005 at gmail.com Mon Oct 22 06:11:38 2007 From: rogerpack2005 at gmail.com (Roger Pack) Date: Mon, 22 Oct 2007 04:11:38 -0600 Subject: [Rubyinstaller-devel] Did you succeed on Ruby-MinGW compilation? In-Reply-To: <71166b3b0710210621o7b05f511tb1d83b486bac983@mail.gmail.com> References: <71166b3b0710201431m50ccde4fu69ca9fee4547b6a6@mail.gmail.com> <966599840710201444m25a9ff34y73f63577b74e3aaa@mail.gmail.com> <71166b3b0710201522m2d53259eia97a363df2a9a745@mail.gmail.com> <966599840710202300x35902674ufc0b208c56dc4057@mail.gmail.com> <71166b3b0710210621o7b05f511tb1d83b486bac983@mail.gmail.com> Message-ID: <966599840710220311r400e203dx27a109acff1e9280@mail.gmail.com> For some reason the mingw gcc is having trouble with finding headers and libs. It is reasonably annoying :) $ cat test.c #include Melissa at MELISSA-PACK /c/take3/ruby/ext/zlib $ gcc test.c test.c:1:18: zlib.h: No such file or directory Melissa at MELISSA-PACK /c/take3/ruby/ext/zlib $ ls /usr/local/include GraphicsMagick iconv.h libcharset.h localcharset.h zconf.h zlib.h It's there! I see it! Anyway gcc is loading its own directories--I think the problem is that I unzip things within the 'msys' framework, when in reality I should unzip them all within the mingw subdirectory. Man that is so retarded! I am also having some serious difficulty getting openssl to compile, still. I honestly don't know how to do it! On yours does it actually compile anything after it says "compiling zlib" or what not? > > We used it at the office (my company) and for our consulting services. > > > Since last year I'm struggling to get a working, faster environment > > > for Ruby on Windows. Amen to that. > > Honestly I don't like this small struggling community of ruby for > > windows users split again, so I'll love have you on the team and get a > > faster product. I can help out in a limited way :) No problem, there are tools (free) that allow us create MSI installers. WiX and WiXTool. Nice. Does ruby actually run faster in 64 bit modes? I guess the good thing about it is that you can use more memory--like...you know...more than 4G or what not, so I guess being able to eventually compile in it would be nice. Do you think mingw will cut the bill for that? > > - Modular design: currently as I commented to Curt, the installer is a > > giant beast that lack testing and modularity -- even using the > > rakefile -- it is a huge one too difficult to debug. > > There would probably be the natural way of dividing it > to be 'main build' 'internal ext's' and > 'gems' (which is, of course, nuts since gems > is almost everything) >I was talking about the core of the installer, since beside Ruby it >needs the dependencies like OpenSSL, Zlib, Gettext, Iconv, readline, >etc. available at install time. So you want people to keep track of updates to these libraries and integrate them? Not too much problem. It seems like once you get a single build running (anywhere), then updating that build would be cake. >In that way, we could "modularize" or pluginize the installer and >create, without too much hassle new installers for the different >interpreters. >Simply the gem creation and building on Windows is one of the goals. One option is to include a limited build with the distro (like just gcc.exeor what have you), and then gem creators can have it build still. > > - Developer ecosystem friendliness: With the update to VC8 or MinGW, > > the new Ruby distro will be more friendly to developers, so you will > > need just a few instructions to get started, instead the whole problem > > we are dealing right now. > > I still like the 'one click installer' idea, at > least personally. Then tell them to use > gems (and how) and they are good to go :) The One Click installer idea is still present, I meant provide better documentation or support to Gem/Ruby developers with the new "distro". >The survey will cover a "User/Developer" profile, so we could get a >picture of the usage of Ruby on Windows. Asking for advice 'which do you prefer' would be nice, too. > 2) Have a working VC8, mingw, and VC6 (with extensions?) side by side. Err > rather maybe just VC6 and a mingw build side by side so that people can > download them and tell us which one they like more. Give them the choice to > experiment and see if they like one more than another, then pursue that > path. If no opinion then pick one :) >There is a official build with VC6... and is the one that powers OCI currently. >VC8 should be the option since is freely available (and VC6 no longer). Once I get one working with all the libs I'd be happy to post it. > Mingw feels faster than VC6--that I can tell. It does. I like it :) Of course, VC8 feels faster than VC6 too. We should considerer the whoe spectrum and not just the speed of things, stability is important. >A lot of improvements are made to the ruby trunk regarding VC8 >compatibility, and MinGW, on the contrary, haven't improveed (haven't >seen commits about it) for the past year. >That is a important thing, and shouldn't be ignored, since Reinventing >the wheel on a project like this is something huge. Either way's good for me. >Last, but no least, MinGW is more close to what vanilla-gcc is >available under Linux (and similar to OSX too -- afaik), we shouldn't >discard that knowledge neither... >Is a difficult choice, but someone must take it :-) > Also it would be nice to run some really nice tests between all the versions > to see what people are getting into :) I don't know what you imply with "nice tests". If you're just talking about performance, even is important, stability came first. Some tests that show file I/o and socket I/o would be nice. Of course it MUST be stable--any real distro. >(You already show me that RMagick is doing some weird things on MinGW). Yeah we need to resolve those things before maybe...even mentioning it as a real alternative? I can let you know when I finally get everything working. The learning curve is somewhat bad here. I don't understand exactly how this msys versus normal directory structure thing is actually supposed to work. I think that the msys people envision you only using their tools from the console window or something? Huh? I just don't get it. > If it were my personal choice I'd probably go for mingw, because then gem > creators in Linux aren't "shooting in the dark" for the windows side of > their gems. On every gem or lib that I use I provided patches to ease the problems with Windows platform, most due linux developers disregards things like cross-platform, and code things for their own distro. I sometimes have found code that couldn't get it working on other distro that wasn't the original used by the author's gem. > Of course, the real reason I'd suggest that is that I have an > (almost) working build of mingw, and not a VC environment at all (I wanted > speed!). Again, speed vs. stability. Getting the build environment for VC8 isn't too complicated either, but more complex than MinGW it is. A note: VC8 is free, as I commented before. The only drawback I see to mingw is that it probably ain't going to 64-bit anytime soon. And we need to make sure it works. Then again I've never even used it, so I have no point of reference. I'd say offer them both side-by-side for awhile (one for backwards compatibility), and see which one people like. I think after they see that mingw is faster they'll all just use it...like automatically. Good luck to all of us! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071022/2e4c2c26/attachment.html From rogerpack2005 at gmail.com Mon Oct 22 17:00:54 2007 From: rogerpack2005 at gmail.com (Roger Pack) Date: Mon, 22 Oct 2007 15:00:54 -0600 Subject: [Rubyinstaller-devel] Did you succeed on Ruby-MinGW compilation? In-Reply-To: <71166b3b0710221340o60e0cda9see9104d6e2d8a85a@mail.gmail.com> References: <71166b3b0710201431m50ccde4fu69ca9fee4547b6a6@mail.gmail.com> <966599840710201444m25a9ff34y73f63577b74e3aaa@mail.gmail.com> <71166b3b0710201522m2d53259eia97a363df2a9a745@mail.gmail.com> <966599840710202300x35902674ufc0b208c56dc4057@mail.gmail.com> <71166b3b0710210621o7b05f511tb1d83b486bac983@mail.gmail.com> <966599840710220311r400e203dx27a109acff1e9280@mail.gmail.com> <71166b3b0710220708v2864fca0v386c047734e6cfcb@mail.gmail.com> <966599840710221329tab27430u336f95e57b58d774@mail.gmail.com> <71166b3b0710221340o60e0cda9see9104d6e2d8a85a@mail.gmail.com> Message-ID: <966599840710221400u5e823ba7wbf8c23c767fa7fc5@mail.gmail.com> All right I finally hacked through to a working copy of mingw 'with all the fixings' of Ruby 1.8.6's "latest stable release" version. I have posted the final ruby executable with gems and zlib etc. etc. here http://doachristianturndaily.info/roger/ruby_distro/ If anybody wants to try it out and give feedback that would be great! I will try and post a smaller version of the existing downloadable zipfile soon (it may or may not be there by the time you read this email). Thanks for Luis for support, and for obscure emails in newslists around the world for tidbits of information. Wish I could say it had been easy. To install: unzip the ruby_mingw4.zip file to c:\ (or wherever) then make sure (in this example) c:\ruby_mingw4\bin is at the front of your path. Verify by running ruby -v -- should say mingw Now you can install gems by using gem list, gem install XXX (package name there). and see what's installed gem list There are a grundle of packages pre-installed, you may want to uninstall some, a la gem list gem uninstall rails -v 1.2.5 (or what not). gem install rails -v 1.2.3 (to install rails 1.2.3, and uninstall 1.2.5) You may also want to set the environment variable RUBY_OPT=rubygems (or whatever it is exactly) for it to execute "require 'rubygems'" before each script. This release appears to work with rails on windows, using a lot of libraries. Good luck! -Roger Sponsored in part by mokisystems.com web development and upillar.com online vehicle sales and doachristianturndaily.info Remember to have a great day! On 10/22/07, Luis Lavena wrote: > > On 10/22/07, Roger Pack wrote: > > Turns out that whenever you build anything within mingw, you must > specify > > "build it to /mingw" or "--prefix=c:/mingw" or it will install it as if > it's > > an internal MSYS library or something. Which was very surprising for a > > newbie. Ahh well. > > After finally hacking I figured out "wait a second! you can actually > copy > > extensions from the old msvc install into the new mingw one and they > work" > > (so I don't actually even "have" to compile everything now). And, > voila. > > Now I think everything works. > > I told you :-) > > > Turns out the rmagick bug is a 'legacy bug' that is avoided by > installing > > their binary rmagick for windows gem. Problem was theirs, and they > fixed > > it--I just didn't think it would still be there. Ahh well. > > Yeah, RMagick is a so darn beast, they should use the official > ImageMagick... still don't get why they didn't patched officially. > > > So now I finally have a working mingw! Rails works! And it's > faster! And > > doesn't seem to complicated to setup. > > Hehehe, again, I told you so... wasn't complicated, you just need to > invest some hours and get a nice speed (boost) ;-) > > > I'll finalize my notes probably sometime (and keep them online at the > > aforementioned wiki for now). > > > > That will be excellent. > > > I'll also post a copy of my win32 stuff--should I announce it on the > list so > > people can experiment with it? See if they like it? > > That will be good too, since recreating the whole thing is a pain, > sharing it with other win32-users will probably show up some failing > things that you didn't notice. > > > I also did notice that there are some experiment 64-bit stuff for mingw, > > which is...good, but...a little bit scary. > > Yeah, I commented that too. mingw-x64 is too experimental right now, > mostly the way Windows x64 do with signing and manifest things... > > But still, Ruby 1.8 isn't compatible with that, yet. > > > Anyway things are going well. > > I will post my stuff when it gets uploaded in about 30 minutes (turned > out > > rather large). > > Remove documentation! the RI and RDOC stuff eats a lot of space (I had > my distro under 8MB)... > > > Thanks for your help! > > No problem, you're welcome. > > Please share this back with the community. > > -- > Luis Lavena > Multimedia systems > - > Leaders are made, they are not born. They are made by hard effort, > which is the price which all of us must pay to achieve any goal that > is worthwhile. > Vince Lombardi > -- -Roger Pack I like belief. http://www.google.com/search?q=free+bible -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071022/c6851add/attachment.html From luislavena at gmail.com Mon Oct 22 23:40:20 2007 From: luislavena at gmail.com (Luis Lavena) Date: Tue, 23 Oct 2007 00:40:20 -0300 Subject: [Rubyinstaller-devel] .bat / .cmd patches are still there. Message-ID: <71166b3b0710222040h47c1eb86lbcd38ecb791ae905@mail.gmail.com> Curt, The patches for rubygems .cmd files are still present in the current Release Candidate (at least in the repo). I was about to add the libfcgi, ruby-cgi binaries... Just checking ;-) -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From luislavena at gmail.com Tue Oct 23 01:36:18 2007 From: luislavena at gmail.com (Luis Lavena) Date: Tue, 23 Oct 2007 02:36:18 -0300 Subject: [Rubyinstaller-devel] Bootstrapping Ruby and some questions. Message-ID: <71166b3b0710222236r15c784edh5236ba5475241463@mail.gmail.com> Hello fellow Developers! (I guess we aren't so many anyway) ;-) Excluding the debate on which compiler OCI should be based, I found that we need to "bootstrap" the whole process _in_ ruby and avoid the manual compile/patch task. Since the tool of choice for this is Rake, I was looking and playing with Exerb [1], but the lack of documentation of that project (and the manual compilation step) make me hold for a second (until I have much time to play with it). The idea is build a "rake executable" that could be downloaded and used to build ruby, extensions and the whole compile environment without requiring a previous Ruby installed. So far, the debate still remains: VC8 or MinGW. Even after the success of Roger getting Ruby and Rails running on Ruby-MinGW, the uncertain support of x64 for that project (MinGW) still remains as an important point and shouldn't be ignored. Comment: even that Ruby doesn't care about it right now. Anyway, getting back to the questions, we need to collect the average user profile of Ruby on Windows (a), and of course, evaluate other users (like the ones on OSX and Linux) that are interested in support the platform (or being supportive) (b). For the (a) option, I'll like to start asking about: - For what kind of task do you use Ruby? (checkbox) [ ] Learning [ ] Automating Tasks [ ] Desktop Applications [ ] Web Applications (Rails, Merb, Nitro, IOWA, other frameworks) - What is your primary OS? ( ) Linux or *nix derivatives (FreeBSD, Solaris, etc.) ( ) Mac OSX ( ) Windows ( ) Other: ____ - Which of the following architectures is compiled or support your OS? ... provide instructions for the average user gather the correct information (uname, system properties, etc. ... ( ) x86 (i386, i686) compatible ( ) AMD64/x64 ( ) Other: ____ - In your common use of Ruby, do you use: [ ] RubyGems? [ ] Database adapters (mysql, sqlite3, postgres)? [ ] WEBrick [ ] Rails [ ] Mongrel? - How often you update your development tool set? ... compiler, ruby interpreter, gems, libraries ... ( ) Once a month ( ) Every 6 months ( ) At least 1 time every year ( ) I just use it "as-is" - Are you familiar with Version Control Software? (Subversion, CVS, or distributed ones) ( ) Yes, use it for every project. ( ) Rarely ( ) No - As Ruby User/Developer, do you create Open Source Software (OSS) ( ) Yes ( ) No, just as end-user ( ) No, closed for the company I work for - Do you deploy your software to specialized servers? ... Internet hostings providers or locally inside your company ... ( ) Yes, manually by copy methods ( ) Yes, using automation tools like Capistrano ( ) Yes, using custom made Installer / Packages ( ) No - Are you interest to deploy your software in server with different OS/Architecture? ( ) Yes ( ) No - As Ruby Developer, what kind of software you create? [ ] Gems [ ] Ruby C Extensions [ ] Rails plugins [ ] Mongrel Handlers (GemPlugins) [ ] Plain, old-vanilla applications - If you checked one of the options in the previous question, are you interested in cross-platform compatibility? ( ) Yes ( ) No, the software is platform-specific. ( ) No, I really don't care other platforms. - On which platform are you most interested your software run smoothly? [ ] *nix (Linux, FreeBSD, Solaris) [ ] Mac OSX [ ] Windows [ ] Other: _____ - To which compiler are you most familiar? [ ] GCC [ ] Visual C++ [ ] Intel === Ok, So far, all these are the question. I left out a few regarding Zlib and OpenSSL, which must be rephrased. What do you think? Suggestions are welcome! Good nights. [1] http://exerb.sourceforge.jp/index.en.html -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From curt.hibbs at gmail.com Tue Oct 23 09:25:12 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Tue, 23 Oct 2007 08:25:12 -0500 Subject: [Rubyinstaller-devel] .bat / .cmd patches are still there. In-Reply-To: <71166b3b0710222040h47c1eb86lbcd38ecb791ae905@mail.gmail.com> References: <71166b3b0710222040h47c1eb86lbcd38ecb791ae905@mail.gmail.com> Message-ID: <31d15f490710230625l786d985cl2962b8b8213e5d5a@mail.gmail.com> On 10/22/07, Luis Lavena wrote: > > Curt, > > The patches for rubygems .cmd files are still present in the current > Release Candidate (at least in the repo). > > I was about to add the libfcgi, ruby-cgi binaries... > > Just checking ;-) Yeah, let's get rid of them before the next release. Curt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071023/5d2e274e/attachment.html From curt.hibbs at gmail.com Tue Oct 23 09:30:08 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Tue, 23 Oct 2007 08:30:08 -0500 Subject: [Rubyinstaller-devel] Bootstrapping Ruby and some questions. In-Reply-To: <71166b3b0710222236r15c784edh5236ba5475241463@mail.gmail.com> References: <71166b3b0710222236r15c784edh5236ba5475241463@mail.gmail.com> Message-ID: <31d15f490710230630l22469a3dxd739a3bc8cd27fa0@mail.gmail.com> This looks good. Once you've got the survey up, beside announcing it on the obvious ruby and rails MLs, I can post an announcement article to the O'Reilly Ruby blog. Curt On 10/23/07, Luis Lavena wrote: > > Hello fellow Developers! > > (I guess we aren't so many anyway) ;-) > > Excluding the debate on which compiler OCI should be based, I found > that we need to "bootstrap" the whole process _in_ ruby and avoid the > manual compile/patch task. > > Since the tool of choice for this is Rake, I was looking and playing > with Exerb [1], but the lack of documentation of that project (and the > manual compilation step) make me hold for a second (until I have much > time to play with it). > > The idea is build a "rake executable" that could be downloaded and > used to build ruby, extensions and the whole compile environment > without requiring a previous Ruby installed. > > So far, the debate still remains: VC8 or MinGW. > > Even after the success of Roger getting Ruby and Rails running on > Ruby-MinGW, the uncertain support of x64 for that project (MinGW) > still remains as an important point and shouldn't be ignored. > Comment: even that Ruby doesn't care about it right now. > > Anyway, getting back to the questions, we need to collect the average > user profile of Ruby on Windows (a), and of course, evaluate other > users (like the ones on OSX and Linux) that are interested in support > the platform (or being supportive) (b). > > For the (a) option, I'll like to start asking about: > > - For what kind of task do you use Ruby? (checkbox) > [ ] Learning > [ ] Automating Tasks > [ ] Desktop Applications > [ ] Web Applications (Rails, Merb, Nitro, IOWA, other frameworks) > > - What is your primary OS? > ( ) Linux or *nix derivatives (FreeBSD, Solaris, etc.) > ( ) Mac OSX > ( ) Windows > ( ) Other: ____ > > - Which of the following architectures is compiled or support your OS? > ... provide instructions for the average user gather the correct > information (uname, system properties, etc. ... > ( ) x86 (i386, i686) compatible > ( ) AMD64/x64 > ( ) Other: ____ > > - In your common use of Ruby, do you use: > [ ] RubyGems? > [ ] Database adapters (mysql, sqlite3, postgres)? > [ ] WEBrick > [ ] Rails > [ ] Mongrel? > > - How often you update your development tool set? > ... compiler, ruby interpreter, gems, libraries ... > ( ) Once a month > ( ) Every 6 months > ( ) At least 1 time every year > ( ) I just use it "as-is" > > - Are you familiar with Version Control Software? (Subversion, CVS, or > distributed ones) > ( ) Yes, use it for every project. > ( ) Rarely > ( ) No > > - As Ruby User/Developer, do you create Open Source Software (OSS) > ( ) Yes > ( ) No, just as end-user > ( ) No, closed for the company I work for > > - Do you deploy your software to specialized servers? > ... Internet hostings providers or locally inside your company ... > ( ) Yes, manually by copy methods > ( ) Yes, using automation tools like Capistrano > ( ) Yes, using custom made Installer / Packages > ( ) No > > - Are you interest to deploy your software in server with different > OS/Architecture? > ( ) Yes > ( ) No > > - As Ruby Developer, what kind of software you create? > [ ] Gems > [ ] Ruby C Extensions > [ ] Rails plugins > [ ] Mongrel Handlers (GemPlugins) > [ ] Plain, old-vanilla applications > > - If you checked one of the options in the previous question, are you > interested in cross-platform compatibility? > ( ) Yes > ( ) No, the software is platform-specific. > ( ) No, I really don't care other platforms. > > - On which platform are you most interested your software run smoothly? > [ ] *nix (Linux, FreeBSD, Solaris) > [ ] Mac OSX > [ ] Windows > [ ] Other: _____ > > - To which compiler are you most familiar? > [ ] GCC > [ ] Visual C++ > [ ] Intel > > === > > Ok, So far, all these are the question. I left out a few regarding > Zlib and OpenSSL, which must be rephrased. > > What do you think? > > Suggestions are welcome! > > Good nights. > > [1] http://exerb.sourceforge.jp/index.en.html > > -- > Luis Lavena > Multimedia systems > - > Leaders are made, they are not born. They are made by hard effort, > which is the price which all of us must pay to achieve any goal that > is worthwhile. > Vince Lombardi > _______________________________________________ > Rubyinstaller-devel mailing list > Rubyinstaller-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071023/32295d9f/attachment.html From rogerpack2005 at gmail.com Tue Oct 23 11:16:31 2007 From: rogerpack2005 at gmail.com (Roger Pack) Date: Tue, 23 Oct 2007 09:16:31 -0600 Subject: [Rubyinstaller-devel] mingw exceptions Message-ID: <966599840710230816y3e5d4ebbk250ed5cf0a7508de@mail.gmail.com> It would appear that it is possible to create a mingw build that does weird things (I'm not sure if a plain version exhibits these issues). I have one distro built in which rubygems refuses to work--throws weird errors (it may have been just a faux pas of mine--I messed around with it a LOT so it's like a hodge-podge of junk). Anyway if anyone has seen anything like this let me know: irb(main):001:0> require 'rubygems' => true irb(main):002:0> require 'sources' rescued exception no such file to load -- sourcesC:/ruby_mingw4/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:30:in `gem_original_require' (sources does exist). I go in there to see where the problem is, and add this code around "init_gemspecs" begin @gemspecs = init_gemspecs # this seems to throw some type of ephemeral exception or something rescue Exception => e print 'gotcha', e, e.backtrace.join("\n"), "\n" end An exception is raised, but this code doesn't catch it When I change it to "rescue Object," I can catch it, but the backtrace is empty, and it seems to be a copy of an exception thrown earlier. begin @gemspecs = init_gemspecs rescue Object => e print 'gotcha', e, e.backtrace.join("\n"), "\n" end If I do require 'rubygems' Gem.searcher require 'sources' It seems to do slightly diffferent things. There seems to possibly be confusion on exceptions--like that earlier exception is raised...again! So anyway I'm not sure if this is a 'real' problem or not or just one with because of carelessness on my part. Just reporting findings. Thoughts? -Roger -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071023/59ca19fa/attachment.html From luislavena at gmail.com Tue Oct 23 12:55:37 2007 From: luislavena at gmail.com (Luis Lavena) Date: Tue, 23 Oct 2007 13:55:37 -0300 Subject: [Rubyinstaller-devel] mingw exceptions In-Reply-To: <966599840710230816y3e5d4ebbk250ed5cf0a7508de@mail.gmail.com> References: <966599840710230816y3e5d4ebbk250ed5cf0a7508de@mail.gmail.com> Message-ID: <71166b3b0710230955v737fa096xee19c773af9d9fd7@mail.gmail.com> On 10/23/07, Roger Pack wrote: > It would appear that it is possible to create a mingw build that does weird > things (I'm not sure if a plain version exhibits these issues). I have one > distro built in which rubygems refuses to work--throws weird errors (it may > have been just a faux pas of mine--I messed around with it a LOT so it's > like a hodge-podge of junk). > > Anyway if anyone has seen anything like this let me know: > irb(main):001:0> require 'rubygems' > => true > irb(main):002:0> require 'sources' > rescued exception > no such file to load -- > sourcesC:/ruby_mingw4/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:30:in > `gem_original_require' > (sources does exist). > > > I go in there to see where the problem is, and add this > code around "init_gemspecs" > begin > @gemspecs = init_gemspecs # this seems to throw some type of ephemeral > exception or something > rescue Exception => e > print 'gotcha', e, e.backtrace.join("\n"), "\n" > end > > > An exception is raised, but this code doesn't catch it > When I change it to "rescue Object," I can catch it, but the backtrace is > empty, and it seems to be a copy of an exception thrown earlier. > You should check what init_gemspecs is doing. If you think is a Ruby problem, try to isolate a simple example and bounce that to ruby-core ;-) But I guess RubyGems is getting confused by the information in rbconfig and the one it generates. Try doing "gem env" and see where it's supposed to get the gems from. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From jan.dvorak at kraxnet.cz Tue Oct 23 18:31:06 2007 From: jan.dvorak at kraxnet.cz (Jan Dvorak) Date: Wed, 24 Oct 2007 00:31:06 +0200 Subject: [Rubyinstaller-devel] ruby-opengl update Message-ID: <200710240031.06241.jan.dvorak@kraxnet.cz> Hello, can you please update ruby-opengl for the next OCI release ? I've created package with the binaries and samples for version 0.50.0, and patch against current svn of rubyinstaller is attached to this mail. From usage and API point of view the 0.50.0 release should be 100% backwards compatible with the original Yoshi's 0.2x/0.3x bindings, the only difference is that 0.2x installs files 'opengl.so' and 'glut.so', while we use 'gl.so', 'glu.so', 'glut.so' and also 'opengl.rb' for backwards compatibility. Thanks, Jan -------------- next part -------------- A non-text attachment was scrubbed... Name: oci-ruby-opengl-0.50.diff Type: text/x-diff Size: 827 bytes Desc: not available Url : http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071024/474c9ea6/attachment.bin From luislavena at gmail.com Tue Oct 23 21:04:06 2007 From: luislavena at gmail.com (Luis Lavena) Date: Tue, 23 Oct 2007 22:04:06 -0300 Subject: [Rubyinstaller-devel] ruby-opengl update In-Reply-To: <200710240031.06241.jan.dvorak@kraxnet.cz> References: <200710240031.06241.jan.dvorak@kraxnet.cz> Message-ID: <71166b3b0710231804k69e41e11ud2d5af3fb392125c@mail.gmail.com> On 10/23/07, Jan Dvorak wrote: > Hello, > > can you please update ruby-opengl for the next OCI release ? I've created > package with the binaries and samples for version 0.50.0, and patch against > current svn of rubyinstaller is attached to this mail. > > From usage and API point of view the 0.50.0 release should be 100% backwards > compatible with the original Yoshi's 0.2x/0.3x bindings, the only difference > is that 0.2x installs files 'opengl.so' and 'glut.so', while we > use 'gl.so', 'glu.so', 'glut.so' and also 'opengl.rb' for backwards > compatibility. > Thank you Jan I'll review this tomorrow morning and post here the results. Regards, Luis -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From rogerpack2005 at gmail.com Thu Oct 25 11:00:27 2007 From: rogerpack2005 at gmail.com (Roger Pack) Date: Thu, 25 Oct 2007 09:00:27 -0600 Subject: [Rubyinstaller-devel] survey Message-ID: <966599840710250800r544c7b83id2bc01c4a6271000@mail.gmail.com> A couple thoughts: The real things we want to discover from this survey are: "Which ruby build distro would you prefer" So asking that up front would be nice. Another good question would be "which binary extensions do you use" so can we look at them to make sure that they work. Another would be "how important would ruby 64 bit be to you?" Also the survey seems a little bit long and wordy. Some of thiose things don't seem too important...might want to cull it down--people are less likely to do a survey that's ginormous. Take care! Ruby mingw is working pretty well! No fatal problems yet, and a noticeable speed increase. I'm working on optimizing the GC :) -- -Roger Pack I like belief. http://www.google.com/search?q=free+bible -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071025/d6c72b01/attachment.html From luislavena at gmail.com Thu Oct 25 13:23:56 2007 From: luislavena at gmail.com (Luis Lavena) Date: Thu, 25 Oct 2007 14:23:56 -0300 Subject: [Rubyinstaller-devel] survey In-Reply-To: <966599840710250800r544c7b83id2bc01c4a6271000@mail.gmail.com> References: <966599840710250800r544c7b83id2bc01c4a6271000@mail.gmail.com> Message-ID: <71166b3b0710251023w7d252485n46a2f027d5f0d57d@mail.gmail.com> On 10/25/07, Roger Pack wrote: > A couple thoughts: > The real things we want to discover from this survey are: > "Which ruby build distro would you prefer" > > So asking that up front would be nice. > Yeah, but the thing about that is some users really don't understand the implications of Cygwin vs VC6 vs VC8 vs MinGW. So put that decision in their hands bounds us con narrow our possibility to choose the best one. > Another good question would be "which binary extensions do you use" so can > we look at them to make sure that they work. > The problem with that is that sometimes, most of the Rails users, really don't know what they are using behind... except for mysql-sqlite3-postgres adapters and of couse, the dread RMagick. > Another would be "how important would ruby 64 bit be to you?" > Well, lot of users from *nix world (since the survey is aimed to every ruby developer, not just Windows) will argue that they use x64 linux distros and ruby build for that... but that doesn't meant they take advantage of 63bits pointers, which is useful if you handle process of 2GB+ RAM. I didn't want to make the survey Windows-only, since most of the gems developers work on OSX or Linux, and I'll love they want to support getting better cross-platform functionality for their gems. > Also the survey seems a little bit long and wordy. Some of thiose things > don't seem too important...might want to cull it down--people are less > likely to do a survey that's ginormous. Yeah, We need to discard things that could be repeated... I'll sent this to a couple of friends to get their opinions. > Take care! Ruby mingw is working pretty well! No fatal problems yet, and a > noticeable speed increase. I'm working on optimizing the GC :) Optimizing the GC? Hope you aren't going in the "tweak until it explodes" kind of optimization... Ruby is compiled with -O2 (size) since sometimes -O3 (speed) generates some wrong code that make Ruby crash... Regards and good week. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From celtic at sairyx.org Thu Oct 25 06:08:27 2007 From: celtic at sairyx.org (Arlen Christian Mart Cuss) Date: Thu, 25 Oct 2007 20:08:27 +1000 Subject: [Rubyinstaller-devel] Project work. Message-ID: <1193306907.7165.8.camel@sohma> Hi guys, I'm thinking I'll probably have to actually turn back this offer of working on the OCI, and if you need more help, then to perhaps ask around some more. Sorry for this inconvenience. Work and uni have turned out to be more of a burden than I can handle with this as well, so I can't give a serious commitment. Best of luck! Arlen From luislavena at gmail.com Mon Oct 29 14:34:17 2007 From: luislavena at gmail.com (Luis Lavena) Date: Mon, 29 Oct 2007 15:34:17 -0300 Subject: [Rubyinstaller-devel] No RubyGems 0.9.5 until RubyConf Message-ID: <71166b3b0710291134h70cde18eld843e094c6f7cdd5@mail.gmail.com> Hello List, Eric Hodel confirmed that RubyGems 0.9.5 will not be released officially until RubyConf, mostly due the changes introduced in the auto platform matching and the indexer [1] So, we will not hold the release of One-Click Installer anymore. I'm working right now on global fixes to be prepared for that and drop another RC with the OpenGL patches sent and some tweaks for the batch files. I'm patching also the bundled ri, testrb, erb, irb and rdoc batch files to match the ones of rubygems. This needs a bit more testing but I hope could commit the pending things tonight. Good week everybody. [1] http://rubyforge.org/pipermail/rubygems-developers/2007-October/003147.html -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From curt.hibbs at gmail.com Mon Oct 29 16:01:03 2007 From: curt.hibbs at gmail.com (Curt Hibbs) Date: Mon, 29 Oct 2007 15:01:03 -0500 Subject: [Rubyinstaller-devel] No RubyGems 0.9.5 until RubyConf In-Reply-To: <71166b3b0710291134h70cde18eld843e094c6f7cdd5@mail.gmail.com> References: <71166b3b0710291134h70cde18eld843e094c6f7cdd5@mail.gmail.com> Message-ID: <31d15f490710291301t75129176qf2b55b83740acbb@mail.gmail.com> On 10/29/07, Luis Lavena wrote: > > Hello List, > > Eric Hodel confirmed that RubyGems 0.9.5 will not be released > officially until RubyConf, mostly due the changes introduced in the > auto platform matching and the indexer [1] > > So, we will not hold the release of One-Click Installer anymore. > > I'm working right now on global fixes to be prepared for that and drop > another RC with the OpenGL patches sent and some tweaks for the batch > files. > > I'm patching also the bundled ri, testrb, erb, irb and rdoc batch > files to match the ones of rubygems. There has also been a new release of FXRuby since we put out RC1. It'd be good to upgrade FXRuby to that release also. Curt This needs a bit more testing but I hope could commit the pending > things tonight. > > Good week everybody. > > [1] > http://rubyforge.org/pipermail/rubygems-developers/2007-October/003147.html > > -- > Luis Lavena > Multimedia systems > - > Leaders are made, they are not born. They are made by hard effort, > which is the price which all of us must pay to achieve any goal that > is worthwhile. > Vince Lombardi > _______________________________________________ > Rubyinstaller-devel mailing list > Rubyinstaller-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071029/ab91f2bb/attachment.html From luislavena at gmail.com Mon Oct 29 16:34:32 2007 From: luislavena at gmail.com (Luis Lavena) Date: Mon, 29 Oct 2007 17:34:32 -0300 Subject: [Rubyinstaller-devel] ruby-opengl update In-Reply-To: <71166b3b0710231804k69e41e11ud2d5af3fb392125c@mail.gmail.com> References: <200710240031.06241.jan.dvorak@kraxnet.cz> <71166b3b0710231804k69e41e11ud2d5af3fb392125c@mail.gmail.com> Message-ID: <71166b3b0710291334n1e8a11e4k331dd2fd2038a2a2@mail.gmail.com> On 10/23/07, Luis Lavena wrote: > On 10/23/07, Jan Dvorak wrote: > > Hello, > > > > can you please update ruby-opengl for the next OCI release ? I've created > > package with the binaries and samples for version 0.50.0, and patch against > > current svn of rubyinstaller is attached to this mail. > > > > From usage and API point of view the 0.50.0 release should be 100% backwards > > compatible with the original Yoshi's 0.2x/0.3x bindings, the only difference > > is that 0.2x installs files 'opengl.so' and 'glut.so', while we > > use 'gl.so', 'glu.so', 'glut.so' and also 'opengl.rb' for backwards > > compatibility. > > > > Thank you Jan > > I'll review this tomorrow morning and post here the results. > Jan, sorry the delay on answering you. It seems the binary files you provide from the ruby-opengl site bundled in the zip listed in the patch are broken (is not a valid Win32 image). Maybe those are the linux ones? (found the ELF header instead of the WinPE one). Let me know so we could ship another RC after this. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From jan.dvorak at kraxnet.cz Mon Oct 29 17:23:50 2007 From: jan.dvorak at kraxnet.cz (Jan Dvorak) Date: Mon, 29 Oct 2007 22:23:50 +0100 Subject: [Rubyinstaller-devel] ruby-opengl update In-Reply-To: <71166b3b0710291334n1e8a11e4k331dd2fd2038a2a2@mail.gmail.com> References: <200710240031.06241.jan.dvorak@kraxnet.cz> <71166b3b0710231804k69e41e11ud2d5af3fb392125c@mail.gmail.com> <71166b3b0710291334n1e8a11e4k331dd2fd2038a2a2@mail.gmail.com> Message-ID: <200710292223.50288.jan.dvorak@kraxnet.cz> On Monday 29 October 2007 21:34, Luis Lavena wrote: > Jan, sorry the delay on answering you. > > It seems the binary files you provide from the ruby-opengl site > bundled in the zip listed in the patch are broken (is not a valid > Win32 image). > > Maybe those are the linux ones? (found the ELF header instead of the WinPE > one). > > Let me know so we could ship another RC after this. Aww, sorry about that. I've now replaced the file on web with the proper binaries. Speaking of that, perhaps it would be better to instead use the win32 binary gem directly from repository, but i'm not sure if i understand the OCI build scripts enough to make a patch. Thanks, Jan From luislavena at gmail.com Mon Oct 29 17:26:30 2007 From: luislavena at gmail.com (Luis Lavena) Date: Mon, 29 Oct 2007 18:26:30 -0300 Subject: [Rubyinstaller-devel] ruby-opengl update In-Reply-To: <200710292223.50288.jan.dvorak@kraxnet.cz> References: <200710240031.06241.jan.dvorak@kraxnet.cz> <71166b3b0710231804k69e41e11ud2d5af3fb392125c@mail.gmail.com> <71166b3b0710291334n1e8a11e4k331dd2fd2038a2a2@mail.gmail.com> <200710292223.50288.jan.dvorak@kraxnet.cz> Message-ID: <71166b3b0710291426o1eb61976u7d1a8a5161c34bdf@mail.gmail.com> On 10/29/07, Jan Dvorak wrote: > On Monday 29 October 2007 21:34, Luis Lavena wrote: > > Jan, sorry the delay on answering you. > > > > It seems the binary files you provide from the ruby-opengl site > > bundled in the zip listed in the patch are broken (is not a valid > > Win32 image). > > > > Maybe those are the linux ones? (found the ELF header instead of the WinPE > > one). > > > > Let me know so we could ship another RC after this. > > Aww, sorry about that. I've now replaced the file on web with the proper > binaries. > Thanks, I'll test it later. > Speaking of that, perhaps it would be better to instead use the win32 binary > gem directly from repository, but i'm not sure if i understand the OCI build > scripts enough to make a patch. > Oh, you have a pre-packaged gem? what compiler did you use? (since we are striclty using VC6 for all the builds). You can contact me online (gtalk) or #mongrel / #mongrel-dev at irc (where I usually hang). -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From jan.dvorak at kraxnet.cz Mon Oct 29 17:44:11 2007 From: jan.dvorak at kraxnet.cz (Jan Dvorak) Date: Mon, 29 Oct 2007 22:44:11 +0100 Subject: [Rubyinstaller-devel] ruby-opengl update In-Reply-To: <71166b3b0710291426o1eb61976u7d1a8a5161c34bdf@mail.gmail.com> References: <200710240031.06241.jan.dvorak@kraxnet.cz> <200710292223.50288.jan.dvorak@kraxnet.cz> <71166b3b0710291426o1eb61976u7d1a8a5161c34bdf@mail.gmail.com> Message-ID: <200710292244.11991.jan.dvorak@kraxnet.cz> On Monday 29 October 2007 22:26, Luis Lavena wrote: > > Speaking of that, perhaps it would be better to instead use the win32 > > binary gem directly from repository, but i'm not sure if i understand the > > OCI build scripts enough to make a patch. > > Oh, you have a pre-packaged gem? what compiler did you use? (since we > are striclty using VC6 for all the builds). VC6 as well, if fact the only reason i use VC6 is to build the bindings to be compatible with OCI :) (fortunately the company i work for had some spare VC6 licenses). > You can contact me online (gtalk) or #mongrel / #mongrel-dev at irc > (where I usually hang). I'll do Thanks, Jan From luislavena at gmail.com Mon Oct 29 17:56:49 2007 From: luislavena at gmail.com (Luis Lavena) Date: Mon, 29 Oct 2007 18:56:49 -0300 Subject: [Rubyinstaller-devel] ruby-opengl update In-Reply-To: <200710292244.11991.jan.dvorak@kraxnet.cz> References: <200710240031.06241.jan.dvorak@kraxnet.cz> <200710292223.50288.jan.dvorak@kraxnet.cz> <71166b3b0710291426o1eb61976u7d1a8a5161c34bdf@mail.gmail.com> <200710292244.11991.jan.dvorak@kraxnet.cz> Message-ID: <71166b3b0710291456x6b7ed5eo219a86b84dc0183@mail.gmail.com> On 10/29/07, Jan Dvorak wrote: > On Monday 29 October 2007 22:26, Luis Lavena wrote: > > > Speaking of that, perhaps it would be better to instead use the win32 > > > binary gem directly from repository, but i'm not sure if i understand the > > > OCI build scripts enough to make a patch. > > > > Oh, you have a pre-packaged gem? what compiler did you use? (since we > > are striclty using VC6 for all the builds). > VC6 as well, if fact the only reason i use VC6 is to build the bindings to be > compatible with OCI :) (fortunately the company i work for had some spare VC6 > licenses). > Hope you don't missed the previous mails about the possible version switch for next RubyInstaller. Still lot of points (good and bad) should be taked in consideration to take the final decision. Regards, -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi