I think the time laps when CMake was generating erroneous Config file under
Windows was very short, and I had no luck by building at this moment.
But having the ability to force CMake to regenerate this kind of file should
be useful in the future if others modifications come.

On Fri, Jun 27, 2008 at 11:04 AM, Robert Osfield <[EMAIL PROTECTED]>
wrote:

> On Fri, Jun 27, 2008 at 9:49 AM, Serge Lages <[EMAIL PROTECTED]>
> wrote:
> > Thanks for the hint, it seems to be my fault. I opened the
> > OpenThreads/Config file to see the method used, and everything was
> > commented... I hade to remove my CMakeCache.txt to have the file
> generated
> > again and use the atomic pointers. Now it works like a charm !
>
> Good to hear things are working again.
>
> I wonder if the Config file generated initially was incorrect, then
> CMake just used this, even when later updates to the CMake build where
> checked in that fixed problems here the old erroneous Config was not
> replaced.
>
> It might be that others will come up against the same issue during
> this transition between pre Config/Atomic days and what we have now.
>
> Robert.
> _______________________________________________
> osg-users mailing list
> [email protected]
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>



-- 
Serge Lages
http://www.tharsis-software.com
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to