--
You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To post to this group, send email to rubyin...@googlegroups.com.
To unsubscribe from this group, send email to rubyinstalle...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyinstaller?hl=en.
Ok I am doing
./configure.rb --with-apxs=/c/Users/zdavatz/software/httpd-2.2.17/
support
in
sh-3.1$ pwd
/c/Users/zdavatz/software/mod_ruby-1.3.0
but again it results in
``': Permission denied - c:/Users/zdavatz/software/httpd-2.2.17/
checking for dynamic Apache module support... ./configure.rb:518:in
support -q INCLUDEDIR (Errno::EACCES)
apache mod_ruby.c, you need to check if is compiled or not. Most likely is not.
--
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry
To build any apache modules you need to build apache too, and build
apache is not an easy task.
James suggestion was go on a different way, since ModRuby is dead and
been like that for long time.
Please, don't use 2008 article to back *your* need for something.
If you look at Rubyinstaller group and previous rubyinstaller-devel
and -users list, noone required this.
Passenger was created after that article, and for sure changed the way
people deploy Ruby applications behind Apache.
> Missing mod_ruby on Windows hurts Ruby.
>
That is your appreciation based on your needs.
> mod_php is all over the place. Why isn't mod_ruby?
>
Because nobody on Windows uses it?
mod_ruby hooks into your Apache process and there is no easy way to
track or restart individual processes. That is why mongrel_service
proven to be a more viable and useful solution for admins.
> Ruby_Installer on Windows is great! But with mod_ruby it would be
> Rocking!
>
RubyInstaller, don't add underscores where there is. And again, is
your need, not RubyInstaller project.
Please refer to the bundling policies related to RubyInstaller in our FAQ:
https://github.com/oneclick/rubyinstaller/wiki/FAQ
In all the years working and deploying applications on Windows never
used Apache, and will not start doing it now.
Again, it is time you get your hands dirty if you really need it. And
again, please restrict from posting emails on every pebble you find in
your way, mailing list is not IRC.
cl.exe is Visual Studio, You need exact same version of the one used
to compile Apache, and we start all over again since you need a Ruby
compiled with Visual Studio to be able to compile the extension...
Command line compilers and other very useful tools are now provided by MSFT as part of their Windows SDK.
A ton of links from Google, but here's a good start: http://msdn.microsoft.com/en-us/windows/bb980924
Jon
---
blog: http://jonforums.github.com/
change
CFLAGS = /nologo /MD /W3 /O2 /D WIN32 /D _WINDOWS /D NDEBUG
CXXFLAGS =
LTFLAGS =
LDFLAGS = kernel32.lib /nologo /subsystem:windows /dll /machine:I386
/libpath:"%APACHE2%\lib"
to something gcc unredstands, like:
CFLAGS = -Wall -O2 -D WIN32 -D _WINDOWS -D NDEBUG
CXXFLAGS =
LTFLAGS =
LDFLAGS = -lkernel32.lib -shared -Wl, -soname, mod_ruby.dll -o mod_ruby.dll
This is just a hint. Original uses cl.exe (MS VC Compiler) to build this dll,
which can't be done now, since ruby installers are compiled from mingw-gcc.
You will probably have to ask mod_ruby author to try port to mingw-gcc
compiler,
in a way that resulting dll can be loaded to msvc based apache. If it
can be done at all.
I think you're interpreting the information incorrectly.
Apache on Linux uses multiple threads *and* multiple process, but due
the nature of Ruby -- not been multi-thread friendly -- mod_ruby is
run across the processes and not across threads.
That is why you get concurrent request with mod_ruby on Linux but that
can't happen on Windos since Apache is single process and mod_ruby
can't spawn multiple Ruby VMs per-thread.
One thing I would recommend for your application is look at Rack, and
build your HTTP communication form your application to the world using
it:
When using Rack, you can leverage not only on FastCGI (which allow
multiple long lived processes) or in tools like Thin, Mongrel or even
Passenger (mod_rails) on Linux.
That will put your software up to this decade in tool strategies.