Hi Scott,
There is actually a possibility to tell Visual C++ directly where the
DLL is located (by changing the PATH variable for one configuration
inside VS), but I don't remember right now how and I'm just on the
wrong OS right now to have a look.
Obviously I want to avoid having the
Werner Smekal wrote:
Hi Scott,
There is actually a possibility to tell Visual C++ directly where the
DLL is located (by changing the PATH variable for one configuration
inside VS), but I don't remember right now how and I'm just on the
wrong OS right now to have a look.
Obviously I
Hi.
As I said, on Linux when I do make test, my_test gets run fine--I
think because rpath is properly recording the location of the shared
libraries. On windows (Visual Studio 2005), my_test will not run.
When I execute ctest by hand, I am told that it cannot locate
'util.dll' (as
Werner Smekal wrote:
Hi.
As I said, on Linux when I do make test, my_test gets run fine--I
think because rpath is properly recording the location of the shared
libraries. On windows (Visual Studio 2005), my_test will not run.
When I execute ctest by hand, I am told that it cannot locate
On Tue, May 12, 2009 at 11:18:32AM -0400, Scott Gray wrote:
1. I can copy the tests into a staging environment so that they are
sitting along side the DLL's prior to running them.
2. I saw that there is an upcoming feature in the CVS tree in which
environment variables can be set for tests.
All,
I currently have a test program that is used to test an API in shared
library that I am producing as part of the build. The build of the
shared library and running of the test program is working on Linux but
not on Windows because it appears to me that my test program cannot find
the
