Trolltech Home | Qt-interest Home | Recent Threads | All Threads | Author | Date
All threads index page 1

Qt-interest Archive, May 2008
RE: QDesignerCustomWidgetInterface questions

• Subject: RE: QDesignerCustomWidgetInterface questions
• From: "Tony Rietwyk" <tony.rietwyk@xxxxxxxxxxxxxxxx>
• Date: Thu, 1 May 2008 11:01:19 +1000
• Delivered-to: qt-interest@trolltech.com
• Importance: Normal
• List-help: <mailto:qt-interest-request@trolltech.com?subject=help>
• List-post: <mailto:qt-interest@trolltech.com>
• List-subscribe: <mailto:qt-interest-request@trolltech.com?subject=subscribe>
• List-unsubscribe: <mailto:qt-interest-request@trolltech.com?subject=unsubscribe>
• Resent-from: qt-interest@xxxxxxxxxxxxx
• Resent-message-id: <hYiRw.A.xJG.7ZRGIB@esparsett>
• Resent-sender: qt-interest-request@xxxxxxxxxxxxx
• Thread-index: AciqxeP3WkbrGYydS+O4Ioi2BNq/5AAYL7wg
• To: <qt-interest@xxxxxxxxxxxxx>

Hi David, 

Using DESTDIR = $$[QT_INSTALL_PLUGINS]/designer  has fixed the problem. 

Thanks for the pointer. 

Tony Rietwyk

> David Boddie wrote:
> 
> > Tony Rietwyk wrote:
> > 
> >> Maybe the DEST_DIR or OBJECTS_DIR overrides the target.path?
> > 
> > I guess it's possible, but it's surprising that these would 
> affect the
> > install step. On Unix platforms, when building all this at 
> the command
> > line, typing "make install" would cause the libraries to be 
> installed
> > correctly. I'm not sure how the Visual Studio Integration 
> handles this.
> 
> Just to follow up, it seems that the installation procedure 
> for Designer
> plugins within Visual Studio is somewhat special:
> 
> http://trolltech.com/developer/knowledgebase/faq.2006-05-16.6272067269

--
 [ signature omitted ]