On 9/11/06, Nicolas Lehuen <[EMAIL PROTECTED]> wrote:
Sorry I usually don't use the VS GUI to build mod_python, only the
dist/build_installer.bat script. I didn't even notice there was a VS
.vcproject file until now :). That's why I haven't noticed the problem.
Not your fault, probably mine for
Dan Eloff wrote:
Unrelated question, is it "ok" to use the trunk in a development
environment? It will usualy work, or should I expect it to blow up in
my face more often than not?
At this point in the development cycle you are fairly safe. As later
messages in this thread indicate you've been
Jorey Bump wrote ..
> Graham Dumpleton wrote:
>
> > The only area I guess one may have to be careful with is if you have
> used
> > PythonPath directive to extend module search path, especially if you
> > reference directories in the document tree. This may result in mod_python
> > complaining in
Graham Dumpleton wrote:
The only area I guess one may have to be careful with is if you have used
PythonPath directive to extend module search path, especially if you
reference directories in the document tree. This may result in mod_python
complaining in the Apache error log at you and in worst
Dan Eloff wrote ..
> I get the following linker errors when trying to compile mod_python as
> fetched from the svn tonight.
>
> mod_python error LNK2019: unresolved external symbol
> __imp__MpFinfo_FromFinfo referenced in function _getreq_rec_fi
> mod_python error LNK2019: unresolved external symb
