stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Sebor <se...@roguewave.com>
Subject copying .dll to project directories (was Re: [Fwd: Solution generartion script for Intel 9.0 compiler])
Date Thu, 15 Dec 2005 19:24:32 GMT
Anton Pevtsov wrote:
[...]
> Martin Sebor wrote:
> 
>>Also, if we are still copying the .dll to the example and test 
>>directories as I noticed the script was some time back I would like to
> 
> 
>>change this to make sure no such copying takes place. Instead > we 
>>should modify the PATH variable or do whatever else is normally done 
>>within the IDE to get this to work.
> 
> 
> As far as I know IDE does the same. And it cannot run .exe file if the
> required .dll is absent in the current directory and in the PATH's
> directories. Could you please explain why you don't like the copiyng?
> This is the post-build step and it is executed automatically when you
> build the project (from IDE or via build.bat).

I don't like copying the .dll (or any duplication in general) because
it increases the chances of things getting out of sync when the user
rebuilds the library some other way other than through the IDE (e.g.,
via a makefile). They'll have to remember to copy it to all the right
places.

If appending $BUILDDIR/lib to PATH is too difficult to do in the IDE
I would prefer to require users to set it on the command line before
invoking Visual Studio rather than do the copying. But I recognize
that others may feel differently :) How about making the copying an
option (say, /COPYDLL) to the generate script?

Martin

Mime
View raw message