Re: Installing synopsis on Windows

David Genest wrote:

> Stefan, is there a document, or some kind of map that I can use to know
> where the different binaries should end up once built ? I know I could
> search the makefiles, but unfortunately, I have been spoiled by the
> Visual Studio project system and therefore am not that versed in
> makefiles. Autoconf and .configure scripts don't help me in that domain
> :-).

The current build system is a hybrid that mixes the python distutils
with some autoconf / make build system. I'm not sure exactly what your
MSVC harness would do, whether it would only replace the (embedded)
autoconf / make part or the entire build system.

It would be best (for multiple reasons) if we could first establish
the mingw-based build as a reference (that one triggers if you run
"/path/to/native/python setup.py build" on windows), and then make
the MSVC solution / project reproduce the result.

Let's assume for a moment that we build 'inplace' (an option to
the distutils build harness). This results in:

* libSynopsis.[so, dll] to end up in lib/
* C++ applets to end up in bin/
* Cpp, C, and Cxx parser to end up in Synopsis/Parsers/[Cpp, C, Cxx]

Does this answer your question ?

Regards,
		Stefan

PS: How much does your solution / project harness depend on the MSVC version
    to use ? Is there a way to have a single harness that works with multiple
    versions ?

-- 

      ...ich hab' noch einen Koffer in Berlin...