PyQL building issues about pyql HOT 7 OPEN

@mtrstudio multiple things:

1. can you verify that the missing simbol exists in the .def file?
   • ??0Date@QuantLib@@QEAA@XZ
   • ??0SimpleCashFlow@QuantLib@@QEAA@NAEBVDate@1@@Z
     (are you sure you point to the latest version of the generate .lib file from MSVC?)
2. you're can't build QL with MSC 2012 and planning to use it with Python 2.7. Python 2.7 "can only use" extensions built with MSVC 2008.

from pyql.

Hey I actually just ran into the same exact error. I compiled QL in Visual Studio 2013 express are you saying I'll need to compile in an older Microsoft compiler? i.e. VS2008

from pyql.

@charles-peter yes, you should be either using VS2008 or the free C++ compiler for Python 2.7: http://www.microsoft.com/en-us/download/details.aspx?id=44266

from pyql.

Hey, indeed I can't find

1. ??0Date@QuantLib@@qeaa@XZ
2. ??0SimpleCashFlow@QuantLib@@qeaa@NAEBVDate@1@@z
   in the .def file (which is of size 42257K), could it be that something is missing when I generate the .def file. Which object files after building quantlib are responsible for the two symbols?

It seems the .def is not properly generated, I have 288340 lines in .def, subtracting the first two lines which are
LIBRARY "QuantLib"
EXPORTS
then there are 288338 functions are generated in .def, is that right?

By the way I am using quantlib-1.5, I saw some other guys in previous posts were also using this version.

from pyql.

Yes, that looks like a .def file generation issue.

I don't have much time right now to dig into the details. You cand find the symbols, .dll and .lib + built library here to compare: https://www.dropbox.com/sh/rul49lx01hxjlua/AACi1kLqD10ff0ALo6vX_zaha?dl=0 That was for QL 1.4. I can try to update it to 1.5 but can't promise anything in the coming days. It should not be an issue though.

from pyql.

Hey thanks a lot~ But exactly the same errors occurred even after using the libs you sent to me. Maybe it really has something to do with the compiler itself.

On the other hand, I noticed, my .def file (I changed to quantlib1.4) is different from yours, so I think there are two possibilities here:

1. the objects files are dependent on the compiler, i.e. msvc2012 and msvc2008 give different object files
2. the symbol generation function has some kind of bugs

Just some guess, hopefully it will be useful for your development

from pyql.

Symbols are definitely compiler specific.

! As stated before, you won't get PyQL to run with Python 2.7. if you use msvc2012. It has to be msvc2008 or the MSFT C++ compiler for Python 2.7

from pyql.