<div class="gmail_quote">On Wed, Jan 28, 2009 at 6:10 PM, Andreas Pakulat <span dir="ltr"><<a href="mailto:apaku@gmx.de">apaku@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Ih2E3d">On 28.01.09 23:58:26, Pau Garcia i Quiles wrote:<br>
> On Wed, Jan 28, 2009 at 11:41 PM, Andreas Pakulat <<a href="mailto:apaku@gmx.de">apaku@gmx.de</a>> wrote:<br>
> When I develop an application which uses Qwt5, Qt4 and OSG, it would<br>
> be convenient that a "nmake install" would install my application and<br>
> the Qwt5, Qt4 and OSG DLLs in the same directory (using RUNTIME<br>
> DESTINATION, LIBRARY DESTINATION, etc) without me having to INSTALL(<br>
> FILES ... ) or INSTALL( PROGRAMS ... ).<br>
<br>
</div></div>Why install those at all, you already have them on your disk, just use the<br>
one from the external. Thats convenient (and uses a lot less disk space,<br>
looking at the list of libs you have).<br>
<br>
Personally I'm using simple cmd files that set my env up for a particular<br>
compiler+libraries I want to use (when I have to work with that OS) and<br>
then just build+run projects from that environment.</blockquote><div><br>I can't speak for Pau, but we gave up a long time ago dealing with the headaches of trying to maintain batch files which manipulate the PATH environment variable. We currently use INSTALL(FILES) to install all of our DLL dependencies which makes it very easy to deploy the files to a network share and try them out on a variety of systems (without having to worry about an environmental issue causing something to work that otherwise wouldn't).<br>
</div></div><br>-- <br>Philip Lowman<br>