> > Just as you we put OSG under source control, although only
> the include files. But the OpenThreads/Config file is NOT
> under source control.
>
> Ok, just as I suspected.
>
> > I have built OSG with CMAKE "out of source" and if I check
> the OpenThreads/Config file on each computer I can clearly
> see that they are diffrent.
> > The Windows machine is using:
> _OPENTHREAD_ATOMIC_USE_WIN32_INTERLOCKED
> > The Ubuntu machine is using: _OPENTHREAD_ATOMIC_USE_GCC_BUILTINS
> > And the OpenSuse machine is using: _OPENTHREAD_ATOMIC_USE_MUTEX
>
> So in your case, since you have different settings, you'll
> need to use different OpenThreads/Config files on different
> machines. One way to do it would be to check them all in,
> using for example a suffix ("-windows", "-mutex",
> "-gcc-builtins") to differentiate them, and then copy for
> example Config-mutex to Config on your SUSE machine and so on.
But this is what we do. Since we only have the include files for OSG under
source control. And these are NOT affected (at least as far as I can see,
please correct me if I am wrong) by what cmake does with the ATOMIC option.
The only reason for us to have OSG include file under source control is for
convienance. (On windows we also check in the .dll files)
We actually build OSG out-of-source on each machine. So the OpenTreads/Config
file is generated and used on each computer.
So the problem seems to be something else...
/Björn
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
