#109: QuteCom compiling
---------------------------+------------------------------------------------
  Reporter:  yakut         |       Owner:  laurent        
      Type:  defect        |      Status:  new            
  Priority:  major         |   Milestone:  QuteCom 2.2-RC2
 Component:  Build System  |     Version:  2.2-RC3        
Resolution:                |    Keywords:                 
---------------------------+------------------------------------------------

Comment(by laurent):

 Replying to [comment:6 yakut]:
 > Thanks a lot for the provided information- it was helpful. But I still
 have issue with QtUiToolsd.lib. How I can compile it? You advised to
 compile Qt for msvc:
 > configure -platform win32-msvc
 > But win32-msvc is available only for commercial license, I use free
 license. What can you advise?

 use qt-4.5.1 and configure it with -platform win32-msvc2005

 >
 > One more- when I compile project in VS2005 there are a lot of errors
 like:
 > Error copying file (if different) from
 "D:/ForQute/1/qutecom-2.2/build/wifo/phapi/phspeexplugin/phspeexplugin.dll"
 to "D:/ForQute/1/qutecom-2.2/build/debug/phapi-plugins/./".
 > 6>Error copying file (if different) from
 "D:/ForQute/1/qutecom-2.2/build/wifo/phapi/phspeexplugin/phspeexplugin.pdb"
 to "D:/ForQute/1/qutecom-2.2/build/debug/phapi-plugins/./".
 >
 > 1.The .pdb files are generated only in the Debug mode compilation.
 > 2.After the VS compiles .pdb and .dll it put them into
 path_to_project/Release(Debug)/ folder but your rules try to get such
 modules from folder path_to_project. So I need to modify each project
 (93!!!) to put files into the root directory or change your rules. But I
 don't see them.Please advise.

 Hum, you are using vcproj cmake generator ...
 take a look at owbuild/OWCreateProjectBinary.cmake

-- 
Ticket URL: <http://trac.qutecom.org/ticket/109#comment:8>
QuteCom <http://trac.qutecom.org>

_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev

Reply via email to