i have tried dozens of different implementations. tricky issue print dialog show , work correctly on development machine, yet when build .msi file , deploy machine print button nothing. supposed render graph information appropriate ui , have ruled out using qwt library improperly because (even though can't seem install correctly on other machine other dev machine) graphs made using qwt libraries render after program installed, print button work.
here important lines .pro file pertain linking or possible printing issues far can tell:
qt += core gui sql printsupport network greaterthan(qt_major_version, 4): qt += widgets target = static-control-panel template = app symbian: libs += -lftd2xx else:unix|win32: libs += -l$$quote($$pwd/lib/) -lftd2xx \ -l$$quote($$pwd/lib/) -lqwt includepath += $$quote($$pwd/include) dependpath += $$quote($$pwd/include) config += qwt inside .cs file actual has print button have tried #include <qtprintsupport>, #include "qtprintsupport", #include "qtprintsupport/qprintdialog", #include <qtprintsupport/qprintdialog> , , every other possible variation.
i building project using wix , candle , light build it. wix simple markup language specify files include in .msi file , printsupport inclusion identical of other included libraries.
i have tried advancedinstaller , received same results.
i have tried replacing .dll files in install directory after application has been installed on machine newer versions of .dll files, , same old versions dev machine in case weren't making .msi. using old .dlls same unresponsive button. using new .dlls result in application complaining cannot find correct version of .dll , crashes, particularly relevant when replace qwindows.dll, guess .dlls not backwards compatible?
i see nothing specifying version of .dll files included in wix file when build either. versioning of qwt , qtprintsupport? insight problem extremely appreciated, , if unclear or more code examples or information needed, please don't hesitate ask, , thank consideration.
you can inspect version of files included in .msi package making use of tool called orca. orca part of windows installer sdk. install orca, have download latest windows sdk , choose specific optional component install(i dont recollect exact optional component choose orca, recall there no need install full windows sdk)
after install orca, open msi package in orca , navigate "file" table. search specific file , see version of files included.
-the other thing suggest generate verbose installer log . please take @
http://blogs.msdn.com/b/astebner/archive/2005/03/29/help-me-help-you-if-you-have-setup-bugs.aspx
the log give information whether files being copied , other information might you.
-the third thing, suggest figure out if of dependencies in place.
if familiar tool called "procmon" sysinternals suite, can set filters in tool dependent dll files. procmon can indicate if of dependencies not found.
-the 4th thing might want confirm if there special operations required work. such registering dll, creating special registry entries etc.
see if can figure out , can take forward.
Comments
Post a Comment