FWIW. If using Windows Powershell the environment variable needs to be set as:

    $env:MOD_WSGI_APACHE_ROOTDIR="c:\Apache2”

Again set the location to what you are actually using.

Using ‘set’ does not export it such that a child process finds it. A double 
backslash is not required.

I have also updated version of mod_wsgi in develop branch of the GitHub repo to 
look for C:\Apache22 and C:\Apache2 automatically.

So try:

    pip install https://github.com/GrahamDumpleton/mod_wsgi/archive/develop.zip 
<https://github.com/GrahamDumpleton/mod_wsgi/archive/develop.zip>

But if your Apache is not in C:\Apache24, C:\Apache22 or C:\Apache2, set the 
environment variable.

The install script will also now generate better errors now if you specify a 
wrong location or default searches fail on Windows.

Graham

> On 30 Dec 2016, at 3:05 PM, Graham Dumpleton <[email protected]> 
> wrote:
> 
> BTW, where are you even finding an Apache binary which has been compiled with 
> VC14 compiler.
> 
> The latest I know of is compiled for VC10. As Python 3.5 requires VC14 
> compiler, there is no guarantee that Apache 2.2 compiled for VC10 will work.
> 
> Why must you use Apache 2.2? Why can’t you use Apache 2.4?
> 
> Graham
> 
>> On 30 Dec 2016, at 8:27 AM, Graham Dumpleton <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Try:
>> 
>> set MOD_WSGI_APACHE_ROOTDIR="c:\\Apache22 <smb://Apache22>
>> 
>> I don’t know how backslashes are handled in Windows environment variables 
>> and whether they need to be escaped.
>> 
>> Also ensure you are setting the correct path to where your Apache 
>> installation is. It must the directory which contains ‘include’ directory 
>> for Apache.
>> 
>> If you don’t set and export the environment variable it will keep 
>> complaining about APXS error as it falls back to that if it cannot find the 
>> Apache installation you are pointing at.
>> 
>> Graham
>> 
>>> On 30 Dec 2016, at 8:20 AM, ANANDA SHANKAR DAS <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> Graham,
>>> 
>>>   I   still get the  same error when I  try pip install mod-wsgi . I  have  
>>>  tried   both inside  and outside the   virtualenv   I created, same results
>>> 
>>> On Friday, December 30, 2016 at 2:45:06 AM UTC+5:30, Graham Dumpleton wrote:
>>> 
>>>> On 30 Dec 2016, at 8:06 AM, ANANDA SHANKAR DAS <[email protected] <>> 
>>>> wrote:
>>>> 
>>>> Hi Graham,
>>>> 
>>>>   I have   set   the  path to the  Apache  installation  "c:\Apache22"
>>>> 
>>>> C:\Users\Administrator>set MOD_WSGI_APACHE_ROOTDIR="c:\Apache22"
>>>> 
>>>> Please  let me know  about the  setup.py file   to  include  Apache2.2
>>>> 
>>>> and have   set the  path in windows 
>>> 
>>> After doing that did you then run:
>>> 
>>>     pip install mod_wsgi
>>> 
>>> Once you have done that, if it works, you should be able to run:
>>> 
>>>     mod_wsgi-express module-config
>>> 
>>> and it will output what you need to configure Apache with to load the 
>>> mod_wsgi module from where it is installed.
>>> 
>>> Then configure Apache for your WSGI application and check that it all works.
>>> 
>>> If you need a separate wheel file then do something like:
>>> 
>>>     pip wheel --wheel-dir=wheelhouse mod_wsgi
>>> 
>>> and that should give you a wheel file.
>>> 
>>> You do not need a wheel file if only installing for your own Apache as ‘pip 
>>> install’ does what is required.
>>> 
>>> Why do you specifically need a wheel file?
>>> 
>>> Even you did need a wheel file, when installed from the wheel file, still 
>>> use ‘mod_wsgi-express module-config’ to get what you need to configure 
>>> Apache with to load the mod_wsgi module.
>>> 
>>> Graham
>>> 
>>>> On Friday, December 30, 2016 at 1:18:47 AM UTC+5:30, Graham Dumpleton 
>>>> wrote:
>>>> Using the pip install method has only been tested with Apache 2.4. As a 
>>>> result it only looks for Apache 2.4 by default.
>>>> 
>>>> If you want to try with Apache 2.2, set the environment variable in your 
>>>> shell:
>>>> 
>>>>     MOD_WSGI_APACHE_ROOTDIR="c:\Apache22"
>>>> 
>>>> and do what ever you need to do on Windows to export it so it is visible 
>>>> to the pip command when run.
>>>> 
>>>> Set the path for your Apache 2.2 installation appropriately.
>>>> 
>>>> If that works let me know and I will update setup.py to look for both 
>>>> c:\Apache24 and c:\Apache22 directories.
>>>> 
>>>> Graham
>>>> 
>>>>> On 30 Dec 2016, at 2:10 AM, ANANDA SHANKAR DAS <asda...@ <>gmail.com 
>>>>> <http://gmail.com/>> wrote:
>>>>> 
>>>>> Hi Graham,
>>>>> 
>>>>> I need the mod_wsgi whl file for win 64 bit-Apache webserver 2.2 +Python 
>>>>> 3.5
>>>>> 
>>>>> I searched for it but could not get it. I have the one for apache version 
>>>>> 2.4
>>>>> 
>>>>> Where do I get it?
>>>>> 
>>>>> when I try pip install mod-wsgi I get error
>>>>> 
>>>>> (r_web) C:\Users\Administrator\r_web\RosterWeb>pip install mod-wsgi
>>>>> 
>>>>> Collecting mod-wsgi
>>>>>   Using cached mod_wsgi-4.5.11.tar.gz
>>>>>     Complete output from command python setup.py egg_info:
>>>>>     Traceback (most recent call last):
>>>>>       File "<string>", line 1, in <module>
>>>>>       File 
>>>>> "C:\Users\ADMINI~1\AppData\Local\Temp\2\pip-build-xybcspx9\mod-wsgi\s
>>>>> etup.py", line 150, in <module>
>>>>>         'missing Apache httpd server packages.' % APXS)
>>>>>     RuntimeError: The 'apxs' command appears not to be installed or is 
>>>>> not execu
>>>>> table. Please check the list of prerequisites in the documentation for 
>>>>> this pack
>>>>> age and install any missing Apache httpd server packages.
>>>>> 
>>>>> On Wednesday, April 27, 2011 at 4:16:54 PM UTC+5:30, Graham Dumpleton 
>>>>> wrote:
>>>>> On 27 April 2011 20:37, Hanson <[email protected] <>> wrote:
>>>>> > Please I have read the Quick Configuration Guide on
>>>>> > http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide 
>>>>> > <http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide> but I
>>>>> > seem not to understand. I have downloaded and copied mod_wsgi-win32-
>>>>> > ap22py27-3.3.so <http://ap22py27-3.3.so/> to the modules directory in 
>>>>> > my apache installation
>>>>> > path.
>>>>> >
>>>>> > Please how do I edit my httpd.conf, what and what will I add and where
>>>>> > will I add them?
>>>>> >
>>>>> > I will be very grateful if you help me succeed in this task.
>>>>> > Thank you.
>>>>> Where to put Windows binary and what to call it detailed in:
>>>>> 
>>>>> http://code.google.com/p/modwsgi/wiki/InstallationOnWindows 
>>>>> <http://code.google.com/p/modwsgi/wiki/InstallationOnWindows>
>>>>> What to put in Apache configuration to have module loaded detailed in 
>>>>> section:
>>>>> 
>>>>> http://code.google.com/p/modwsgi/wiki/QuickInstallationGuide#Loading_Module_Into_Apache
>>>>>  
>>>>> <http://code.google.com/p/modwsgi/wiki/QuickInstallationGuide#Loading_Module_Into_Apache>
>>>>> Once you have that LoadModule line in place and Apache appears to
>>>>> restart okay, then use hello world WSGI program in:
>>>>> 
>>>>> http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide 
>>>>> <http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide>
>>>>> along with the WSGIScriptAlias directive as explained to test simple
>>>>> script works.
>>>>> 
>>>>> For your actual application, how you configure things will depend on
>>>>> what it is and how you want to expose it. Further guidelines in:
>>>>> 
>>>>> http://code.google.com/p/modwsgi/wiki/ConfigurationGuidelines 
>>>>> <http://code.google.com/p/modwsgi/wiki/ConfigurationGuidelines>
>>>>> If this doesn't help, you will need to be more explicit about the
>>>>> actual problem you are having.
>>>>> 
>>>>> Remember, the Apache error log is your friend and you should keep a
>>>>> close eye on it for any sort of error message when you are having
>>>>> problems. Also ensure to increase the Apache error log level to get
>>>>> additional information out of mod_wsgi about what it is doing while
>>>>> you sort things out. See:
>>>>> 
>>>>> http://code.google.com/p/modwsgi/wiki/DebuggingTechniques 
>>>>> <http://code.google.com/p/modwsgi/wiki/DebuggingTechniques>
>>>>> Graham
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google Groups 
>>>>> "modwsgi" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>>> email to modwsgi+u...@ <>googlegroups.com <http://googlegroups.com/>.
>>>>> To post to this group, send email to mod...@ <>googlegroups.com 
>>>>> <http://googlegroups.com/>.
>>>>> Visit this group at https://groups.google.com/group/modwsgi 
>>>>> <https://groups.google.com/group/modwsgi>.
>>>>> For more options, visit https://groups.google.com/d/optout 
>>>>> <https://groups.google.com/d/optout>.
>>>> 
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "modwsgi" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to [email protected] <>.
>>>> To post to this group, send email to [email protected] <>.
>>>> Visit this group at https://groups.google.com/group/modwsgi 
>>>> <https://groups.google.com/group/modwsgi>.
>>>> For more options, visit https://groups.google.com/d/optout 
>>>> <https://groups.google.com/d/optout>.
>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "modwsgi" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to [email protected] 
>>> <mailto:[email protected]>.
>>> To post to this group, send email to [email protected] 
>>> <mailto:[email protected]>.
>>> Visit this group at https://groups.google.com/group/modwsgi 
>>> <https://groups.google.com/group/modwsgi>.
>>> For more options, visit https://groups.google.com/d/optout 
>>> <https://groups.google.com/d/optout>.
>> 
> 

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to