Re: Installing synopsis on Windows

David Genest wrote:

>     While I can believe that an MSVC 'solution' would be convenient for
>     those
>     people used to MSVC, I still wonder whether it might be possible to add
>     the required flexibility to the existing build system to invoke MSVC's
>     tools (cl.exe, link.exe, etc.) via their command-line interface
>     directly.
>     That is what boost.build is doing, and what I'm doing for other projects
>     (such as http://www.codesourcery.com/vsiplplusplus) successfully.
> 
>     Do you think this may be a viable way forward ?
> 
> 
> Yes I believe it is. It will only take a little more time for me to
> learn and tap into the synopsis build system. I was in the impression
> that synopsis relied a lot on autoconf and similar scripts that cannot
> be ported easily. Where would the cl.exe and link.exe calls be placed in
> the existing toolchain ?

python's distutils is the embedding wrapper, which invokes the various
configure scripts, as well as 'make', for each of the 'subprojects'.

While such an adjustment requires a number of changes at different places,
I believe it would be easiest for you to try making local changes to a
single Makefile. Here is the procedure I'd suggest:

* run "path/to/native/python setup.py config", which generates various
  build directories, with multiple 'Makefile' files in them.

* pick the one for libSynopsis (in "build/ctemp-win32/src") and modify
  it, such as setting "CC := cl.exe", and setting compile and link commands
  appropriately.

* make sure "/path/to/native/python setup.py build" works fine, up to the
  compilation of the applets in src/tools.

* Submit a patch for your changes, at which point we can try to apply similar
  changes to the parser backend Makefiles.

Let me know how this sounds.

Thanks,
		Stefan

-- 

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