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 w
ks for you...
Thanks,
David
On Tue, May 12, 2009 at 2:34 PM, Scott Gray <mailto:sg...@inventa.com>> wrote:
While trying to research the answer to my question about how to
make your test program locate its dependent DLL's (see my previous
posting entitled "add_test and
While trying to research the answer to my question about how to make
your test program locate its dependent DLL's (see my previous posting
entitled "add_test and locating dependent DLL's on Windows"), I decided
to try the recently added ENVIRONMENT property of set_tests_properties
to set the
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
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 DL
Tyler Roscoe wrote:
On Wed, May 06, 2009 at 03:53:10PM -0400, Scott Gray wrote:
My problem is that I need to both generate the DLL and declare it as an
imported library so that other programs can depend upon it. I think I'm
Maybe I'm missing something, but why do you need
Hello,
I've been working for a while to integrate the C/C++
internationalization library ICU with our cmake build process and I've
made some pretty good progress, but I'm currently kind of stuck.
During part of the ICU bundling process, it takes language resource
files (*.res files) and a p
