Re: Batch of unsolved external symbols

[Barry S. <ba...@ba...>]

On Thursday 05 November 2015 21:52:44 Ilçeren Inçelami Çadormoç wrote:
> I see, I didn't get the feeling it was necessary since the documentation
> stated what source files you needed for each header.

You are right it is missing from both the py2 and py3 docs. I have fixed
that are r311. It will be in the new release.

> I'll try that as soon
> as I get to work tomorrow. I normally prefer Visual Studio to do the
> compiling and linking, but that may be useful when I port it to Linux.

<personal-option>

The problem with the Visual Studio stuff is controlling the compiler options
on the sources files. There used to be bugs where setting options in the GUI
would not result in them being used in the compile correctly. I have lost too
much time to VS bugs that it made sense to write the setup_makefile.py.

With setup_makefile.py the time spent maintain the build systems has
gone down to almost nothing. (I use the same method on pysvn and
Barry's Emacs).

Trying to go from win32 to win64 was a night mare in VS last time I tried.

I also like to have a set of build files that can be compared textually to
see what changes have been made. VS reorders sections in its project
files making that hard.

I also want to do builds that can be 100% automated and error checked
by computer with full logs to prove it. That is hard to do with VS.

With nmake/make I can build on all lots of OS with 100% reproducible
results, automatically.

I do use the VS debugger when that is needed.

</personal-option>

> Thank you very much. Ilceren
> 
> > From: ba...@ba...
> > To: cxx...@li...
> > CC: il...@ho...
> > Subject: Re: Batch of unsolved external symbols
> > Date: Thu, 5 Nov 2015 20:12:43 +0000
> > 
> > The missing symbols are in IndirectPythonInterface.cxx
> > It is not optional.
> > 
> > You can generate a windows make file using the following:
> > 
> > c:\python27\python.exe setup_makefile.py win32 example.mak
> > 
> > change the path to python to suit your needs.
> > 
> > If you have nmake on the path you can then build the examples
> > 
> > nmake -f example.make
> > 
> > Barry