Serge,
I know that for my case I just set an windows environment variable to
the install directory where the dll's are located and then add this
variable to the windows path environment variable so that windows can
find all the dll's without having to move them to the directory of the
executable you are trying to run.
If you don't know how to do this and are interested please let me know
and I will write you on the process.
Thanks
Mike Hartman
Michael W Hartman
Senior Software Engineer
Supporting:
VP33 - Exploration Systems Development Office
Science & Missions Systems Office
Phone: (256) 544-5250
Email: [EMAIL PROTECTED]
<http://www.people-tec.com/>
People-Tec, Inc.
1900 Golf Rd., Suite A-B
Huntsville, AL 35802
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Serge Lages
Sent: Thursday, June 07, 2007 6:43 AM
To: osg users
Subject: Re: [osg-users] Here22 debug message and Cmake example
installation
On 6/7/07, Robert Osfield <[EMAIL PROTECTED]> wrote:
Hi Serge,
On 6/7/07, Serge Lages <[EMAIL PROTECTED]> wrote:
> Since yesterday, in the NOTICE verbose mode, I have a "Here22"
output
> message each time I launch an application, is it normal ?
> The message is in Viewer.cpp, line 598, in the viewer
constructor.
And this is why we have dev releases :-)
Now removed the debug message and checked in.
Thanks. :)
> On an other topic, I noticed that under Windows, when we
choose to build the
> examples and launch the INSTALL process, the examples are not
installed with
> the other binaries, is it the wanted behaviour ?
In general the examples are a bit different than the
applications in
that their only functions are to educate the developer and help
do
testing, they aren't something that a general user will user.
This
raises the issue of to install and if so where to?
I haven't tried the windows build for a number of years, let
alone
with CMake so can't comment on what is happening there right now
w.r.t
installs, I didn't even know that there was a VS install now
support
:-)
The problem that I see right now is :
- after building you have the dlls into lib/release(debug), and the
executables into bin/release(debug). From here you cannot launch the
executables without copying yourself the dlls into this folder.
- when you do the install process, it copies the dlls and the
applications executables (osgviewer, osgversion..) into the wanted
directory, and it put the dlls into bin/ instead of lib/ (and remove the
debug or release directories). So now you can launch without problem
osgviewer or any other applications.
But the examples stay alone into the first directory, and without
copying manually the dlls into the same folder, we cannot execute them
(it produces errors not finding osg.dll ect...)
For new users I think it will produce new mailing list entries with the
problem of the examples not finding the dlls. :)
--
Serge Lages
http://www.magrathea-engine.org
<<image003.jpg>>
<<image002.jpg>>
<<image001.gif>>
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
