Hi Eric, all,
I am trying to follow the steps here http://quantlib.org/reposit/docs/latest/build_git_swig_windows.html In step 7 I get LNK2001 / unresolved external Symbol _Excel4. I am using MSVC 12. That's outside specification I know, but is it possible (after the obvious relabeling in the projects)? Or is the linker error coming from exactly the studio version? Any chance to get it run with 12? Thanks Peter ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 _______________________________________________ QuantLib-dev mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-dev |
Hi Peter,
My first guess would be that there is a problem linking the file xlcall32.lib in project xlsdk. There are two versions of that lib, one 32-bit and one 64-bit (the latter confusingly also called xlcall32.lib) with some logic in the project to switch between the two, maybe that´s not working? I do have the 32- and 64-bit builds working in VC9 but I have noticed that they use the same filenames at some point which causes a clash and results in a linker error - so if you have switched between these two builds then you would need to do a full rebuild. I am hoping to do a big push in July which would include cleaning these things up and implementing support for VC9-14. Kind Regards, Eric On Sat, 9 Apr 2016 21:29:32 +0200 Peter Caspers <[hidden email]> wrote: > Hi Eric, all, > > I am trying to follow the steps here > > http://quantlib.org/reposit/docs/latest/build_git_swig_windows.html > > In step 7 I get LNK2001 / unresolved external Symbol _Excel4. > > I am using MSVC 12. That's outside specification I know, but is it > possible (after the obvious relabeling in the projects)? Or is the > linker error coming from exactly the studio version? Any chance to get > it run with 12? > > Thanks > Peter > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications > Manager Applications Manager provides deep performance insights into > multiple tiers of your business applications. It resolves application > problems quickly and reduces your MTTR. Get your free trial! > http://pubads.g.doubleclick.net/ > gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 > _______________________________________________ QuantLib-dev mailing > list [hidden email] > https://lists.sourceforge.net/lists/listinfo/quantlib-dev ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 _______________________________________________ QuantLib-dev mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-dev |
Hi Eric,
thanks. I think I have tried the 32-bit build only, but I will check this point again. Otherwise it will have to wait until summer. Kind Regards Peter On 11 April 2016 at 01:57, Eric Ehlers <[hidden email]> wrote: > Hi Peter, > > My first guess would be that there is a problem linking the file > xlcall32.lib in project xlsdk. There are two versions of that lib, one > 32-bit and one 64-bit (the latter confusingly also called xlcall32.lib) > with some logic in the project to switch between the two, maybe that´s > not working? > > I do have the 32- and 64-bit builds working in VC9 but I have noticed > that they use the same filenames at some point which causes a clash and > results in a linker error - so if you have switched between these two > builds then you would need to do a full rebuild. > > I am hoping to do a big push in July which would include cleaning these > things up and implementing support for VC9-14. > > Kind Regards, > Eric > > On Sat, 9 Apr 2016 21:29:32 +0200 > Peter Caspers <[hidden email]> wrote: > >> Hi Eric, all, >> >> I am trying to follow the steps here >> >> http://quantlib.org/reposit/docs/latest/build_git_swig_windows.html >> >> In step 7 I get LNK2001 / unresolved external Symbol _Excel4. >> >> I am using MSVC 12. That's outside specification I know, but is it >> possible (after the obvious relabeling in the projects)? Or is the >> linker error coming from exactly the studio version? Any chance to get >> it run with 12? >> >> Thanks >> Peter >> >> ------------------------------------------------------------------------------ >> Find and fix application performance issues faster with Applications >> Manager Applications Manager provides deep performance insights into >> multiple tiers of your business applications. It resolves application >> problems quickly and reduces your MTTR. Get your free trial! >> http://pubads.g.doubleclick.net/ >> gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 >> _______________________________________________ QuantLib-dev mailing >> list [hidden email] >> https://lists.sourceforge.net/lists/listinfo/quantlib-dev > ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 _______________________________________________ QuantLib-dev mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-dev |
Free forum by Nabble | Edit this page |