Re: Updated procrun binaries
Konstantin Kolinko wrote: so -win32-x86-native, -win32-x64 and -win32-ia64 would make perfect sense. Fine with me. 32 in -win32-x64 looks odd. Right win64-x64 would make more sense. In the /bin folder there is now a /bin/procrun subfolder, that contains /bin/procrun/amd64/ and /bin/procrun/ia64/ subfolders with a tomcat6.exe file in each of them. If we remain with this, there is no need to create separate zips that Mladen proposed. The main point is to create a separate .zip files that user can directly uncompress inside existing tomcat layout without worrying to copy files from /bin/procrun/amd64 to /bin. Also we constantly point our users to download files from SVN (?) and do manual replacement of files. Regards -- ^(TM) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Updated procrun binaries
Mladen Turk wrote: Konstantin Kolinko wrote: so -win32-x86-native, -win32-x64 and -win32-ia64 would make perfect sense. Fine with me. 32 in -win32-x64 looks odd. Right win64-x64 would make more sense. Irrelevant. There is no win64, but there could be. Linux and most Unicies use 64ILP architecture, where ints, longs and *'s are all 64 bits. The 64 bit Win32 API eg win32-x64 reflects Windows' choice to use 64P architecture; 32 bit windows ints and longs, with 64 bit pointers (e.g. including handles, etc). Do not start notating win64 until it exists; it certainly could in the future; MS could begin shipping a 64 ILP OS. Until then, this is the same API as post-windows 3.x. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Updated procrun binaries
William A. Rowe, Jr. wrote: Right win64-x64 would make more sense. Irrelevant. win32-x64 means nothing to an ordinary user. There is no win64, but there could be. What are u talking about? http://technet.microsoft.com/en-us/library/bb496995.aspx MS clearly distinguishes Win32 and Win64 Regards -- ^(TM) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Updated procrun binaries
Hi, As you could see from the SVN log I've updated procrun binaries to 2.0.5 version (Tagged as COMMONS_DAEMON_2_0_5 in commons) It contains a fix that might help XP/SP1 and later using Java6 on systems that do not have msvcrt71.dll in the PATH (Something Sun refuses to fix) by using the SetDllDirectory API. (Like mentioned present on XP with SP1 and later). Also I've removed the 64-bit GUI (tomcat(X)w.exe) because the 32-bit version can manage both 32 and 64 bit tomcat(X).exe Now, IIRC Mark enabled .zip release so it'll contain both 32 and 64 bit binaries from 6.0.21 and later? If not we should really make some more user friendly link on the download section so those files can be picked up for 64-bit JVM users. Regards -- ^(TM) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Updated procrun binaries
2009/5/29 Mladen Turk mt...@apache.org: Hi, As you could see from the SVN log I've updated procrun binaries to 2.0.5 version (Tagged as COMMONS_DAEMON_2_0_5 in commons) It contains a fix that might help XP/SP1 and later using Java6 on systems that do not have msvcrt71.dll in the PATH (Something Sun refuses to fix) by using the SetDllDirectory API. (Like mentioned present on XP with SP1 and later). Good. Also I've removed the 64-bit GUI (tomcat(X)w.exe) because the 32-bit version can manage both 32 and 64 bit tomcat(X).exe Now, IIRC Mark enabled .zip release so it'll contain both 32 and 64 bit binaries from 6.0.21 and later? Yes, he did. It is already applied to trunk and tc6.0: http://svn.apache.org/viewvc?view=revrevision=777624 http://svn.apache.org/viewvc?view=revrevision=770876 and proposed for 5.5 (see STATUS). Your removal of 64-bit GUI files broke the build scripts there. Thought it will be easy to fix. If not we should really make some more user friendly link on the download section so those files can be picked up for 64-bit JVM users. Regards -- ^(TM) Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Updated procrun binaries
Konstantin Kolinko wrote: Your removal of 64-bit GUI files broke the build scripts there. Sorry ;) Thought it will be easy to fix. Is suppose the copy task should just use the *.exe instead referencing the files directly (more reusable) Nevertheless, how about creating separate .zips that would contain tomcat(X)w.exe tomcat(X).exe service.bat and tcnative-1.dll eg. apache-tomcat-6.0.21-win32-native.zip apache-tomcat-6.0.21-win64-native.zip apache-tomcat-6.0.21-win64-ia64-native.zip they would contain apache-tomcat-6.0.21/bin service.bat tomcat6.exe- depending on the arch tomcat6w.exe - always the same tcnative-1.dll - depending on the arch This way the master .zip can contain only java code, and user would pick the native .zip according to the JVM arch. Regards -- ^(TM) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Updated procrun binaries
Mladen Turk wrote: Nevertheless, how about creating separate .zips that would contain tomcat(X)w.exe tomcat(X).exe service.bat and tcnative-1.dll eg. apache-tomcat-6.0.21-win32-native.zip apache-tomcat-6.0.21-win64-native.zip apache-tomcat-6.0.21-win64-ia64-native.zip ia64 != x64, you realize? there isn't such an architecture as win64. so -win32-x86-native, -win32-x64 and -win32-ia64 would make perfect sense. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Updated procrun binaries
William A. Rowe, Jr. wrote: Mladen Turk wrote: Nevertheless, how about creating separate .zips that would contain tomcat(X)w.exe tomcat(X).exe service.bat and tcnative-1.dll eg. apache-tomcat-6.0.21-win32-native.zip apache-tomcat-6.0.21-win64-native.zip apache-tomcat-6.0.21-win64-ia64-native.zip ia64 != x64, you realize? there isn't such an architecture as win64. Yes, I know that. However win64 in 99% is win64-x64 so -win32-x86-native, -win32-x64 and -win32-ia64 would make perfect sense. Fine with me. Regards -- ^(TM) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
