oship-dev team mailing list archive

[Roger Erens <roger.erens@xxxxxxxxx>]

Hi,

I updated the installation instructions for MS Windows XP and Vista in
FAQ664 [1] and put them into FAQ574 [2].

To summarize the changes:

1)
For the plain vanilla installation of OSHIP, a compiler is not needed,
in principle. Principles aside: having the compiler in Microsoft's
Visual Studio 2003 on your system comes in handy because of:

2)
The use of egenix's mxDateTime product causes some problems. Buildout
cannot handle it (I think) without Microsoft's compiler mentioned
above. But I suspect there are not many people that have that compiler
lying around.
So, for the time being, setup.py has to be hand-edited, and the mxBase
product installed manually.
--
When Grok/Oship's code is upgraded to Python2.6, I think the problem
can be tackled by just requiring the user to install the paid (Visual
Studio) or free (Visual Express) C++ 2008 compiler beforehand. Another
solution might be that the buildout recipe for mxbase gets to work
again.

3)
The stuff about uncommenting/commenting a line containing the phrase
"eggs-directory" is not needed anymore, nor creating such a directory,
right?
I think that using an eggs-directory should be explained in FAQ575
(How do I speed up subsequent installations).

4)
Notes about DSE wrt to the compiler should be in the separate
installation doc for the Decision Support Engine, as long as it is not
a default part of OSHIP, and are thus removed from this installation
document.

Do other Windows users, especially the XP-users, agree that the
instructions in FAQ574 can also be put in FAQ664 instead of the
current ones (after renumbering, of course)?

[1] https://answers.launchpad.net/oship/+faq/664
[2] https://answers.launchpad.net/oship/+faq/574

Cheers,

Roger