Hi JS,
On Thu, Feb 5, 2009 at 7:38 PM, Jean-Sébastien Guay
jean-sebastien.g...@cm-labs.com wrote:
Oh come on. Aren't you pushing this a bit too far? We're not playing
anyone's game, just using a tool that allows us to compile code on a given
platform. This platform choice (which is only one
Hi Robert,
Sigh. I have worked my bollocks off trying to reduce the number of
suppressed warnings in include/osg/Export. We have got as far as we
are going to get without holding back the release for many more weeks,
and without modifying many hundreds of files, needless changes too,
then
I am not sure if it's related or not but i tried to compile the trunk
this morning and here the warning i get.
[ 8%] Building CXX object src/osg/CMakeFiles/osg.dir/OcclusionQueryNode.o
/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include/g++-v4/i686-pc-linux-gnu/bits/c++locale.h:
In function ‘int
Hi Robert,
I use the gcc 4.1.2 i guess it's bogus on this version, i will try to
update.
Thank you
Cheers,
Cedric
Robert Osfield wrote:
HI Cendric,
The line that is trigger this warning is essentially of the form:
float myValue
ostream this is very silly, can't even write out a float
HI Cendric,
The line that is trigger this warning is essentially of the form:
float myValue
ostream this is very silly, can't even write out a float these
days myValuestd::endl;
This is of course perfectly valid C++, this screams out a bug in the
standard library, or the compiler, and not
Hi Robert,
Thanks for the warning fixes, I've merged about 2/3rds of them, but
will record some of the other ones. The server isn't accessible
right now so I'm not able to check in right now. I'll have bash
tomorrow morning.
The server is back up and I've been able to do an update. All
Hi JS,
On Thu, Feb 5, 2009 at 4:23 PM, Jean-Sébastien Guay
jean-sebastien.g...@cm-labs.com wrote:
The server is back up and I've been able to do an update. All warnings fixes
I sent are in except the one in src/osgPlugins/osga/OSGA_Archive.cpp. Is
there a reason or it just got forgotten in the
Hi Robert,
For specific headers I think push/pop is barely tolerable, but for a
.cpp I think it's a real waste of lines of code. Were are talking
about suppressing a warning in an example, and warning that is pretty
bogus w.r.t helping us detect and fix bugs.
That's your opinion but you
Hi JS,
On Thu, Feb 5, 2009 at 4:41 PM, Jean-Sébastien Guay
jean-sebastien.g...@cm-labs.com wrote:
That's your opinion but you shouldn't be making judgement calls like that
for other people's projects, which is why I think putting suppression in
include/osg/Export is a bad practice. But I know
Hi Robert,
push/pop adds a lot of extra syntax to headers for just one single
platform, it's not cross platform in any whatso ever.
I see things from the opposite perspective: if OSG wants to be used
multi-platform, it has to work well on each platform, the way that
platform works.
Skylark wrote:
Where:
HeaderStart:
#if defined(_MSC_VER) %% defined(OSG_DISABLE_MSVC_WARNINGS)
#pragma warning(push)
#pragma warning(disable: a b c d e f g)
#endif
HeaderEnd:
#if defined(_MSC_VER) %% defined(OSG_DISABLE_MSVC_WARNINGS)
#pragma warning(pop)
#endif
You can
On Thu, Feb 5, 2009 at 5:28 PM, Jean-Sébastien Guay
jean-sebastien.g...@cm-labs.com wrote:
I see things from the opposite perspective: if OSG wants to be used
multi-platform, it has to work well on each platform, the way that platform
works. Otherwise, just make VS unsupported and make everyone
Hi Robert,
Just because we use VS doesn't mean that we have to do everything the
MS way. The MS way is to code everything for Windows and Windows
only, cares for portability are very much against MS's strategic goals
of vendor lock-in. Play their game and you end up tied to just a
single
Hi Robert and JS,
I won't take part of this inflamed discussion, but I just want to add a little
technical note:
Whenever the #include osg/HeaderStart is worth trying or not, I guess there
is a way to avoid most missing headers by the way of defines, such as:
// Opening
#ifndef HEADER_OPENED
Humm can we remove the Export header ? just joking ;)
Sukender wrote:
Hi Robert and JS,
I won't take part of this inflamed discussion, but I just want to add a little
technical note:
Whenever the #include osg/HeaderStart is worth trying or not, I guess there
is a way to avoid most missing
Hi All,
On Tue, Feb 3, 2009 at 9:32 PM, Sukender suky0...@free.fr wrote:
My mistake, I meant that the volatile and should be removed (not the
whole static_cast).
May static_castunsigned int do it? (since I'm not certain volatile here
is useful, because we simply return a copy).
I've just
Hi All,
I have now made the OpenSceneGraph-2.8 branch, the svn entry for it is:
http://www.openscenegraph.org/svn/osg/OpenSceneGraph/branches/OpenSceneGraph-2.8/
If those don't CDash builds (as well as everyone else) move across to
using this branch as the base for testing the OSG-2.8
Hi Robert,
I checked out a fresh 2.8 source tree (rev 9648) and it built fine on
vs 2005 xp! But I still see a few warnings and they are attached.
cheers
Mattias
On 2/4/09, Robert Osfield robert.osfi...@gmail.com wrote:
Hi All,
I have now made the OpenSceneGraph-2.8 branch, the svn entry for
Hi Robert,
If those don't CDash builds (as well as everyone else) move across to
using this branch as the base for testing the OSG-2.8 release series.
Quick question about this: Since the Nightly build is still called
Nightly in the 2.8 branch, it will replace any result of a nightly
build
Hi Robert,
Just built a clean checkout of the 2.8 branch on Windows Vista, Visual
Studio 8 SP1. Apart from the std::list warning that we can't do much
about, there were 4 left in OSGA_Archive.cpp (below). I tested the
build in our app and everything worked as expected.
Cheers,
Morne
warning
Hi JS,
On Wed, Feb 4, 2009 at 2:32 PM, Jean-Sébastien Guay
jean-sebastien.g...@cm-labs.com wrote:
Quick question about this: Since the Nightly build is still called Nightly
in the 2.8 branch, it will replace any result of a nightly build of the
trunk right? So I don't have to schedule a
Hi Robert,
I'm terribly sorry, but I don't have the time right now. I just hope someone
else will do it.
PS: I launched an experimental build. I'll tell you about the results.
Sukender
PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/
Le Wed, 04 Feb 2009 15:57:45
Hi Robert,
Yes, move across to making the builds from the 2.8 banch till 2.8.0 is
out.
OK, I've disabled the nightly build of the branch for now.
Even after 2.8.0 is out, there is some value in having periodic
builds of the 2.8 branch as there may well be a 2.8.1+ later released,
although
Hi Robert,
I've tried really hard to fix all these Windows warnings, while most
seem now fixed/workaround/suppressed some have resisted my attempts to
remotely fix them, we me doing several unsuccessful attempts at this
last persistent warnings.
As I said on my other post, I don't seem to get
Hi Window's users,
I've tried really hard to fix all these Windows warnings, while most
seem now fixed/workaround/suppressed some have resisted my attempts to
remotely fix them, we me doing several unsuccessful attempts at this
last persistent warnings. A fundamental problem is that I can't make
Hi JS,
Thanks for the warning fixes, I've merged about 2/3rds of them, but
will record some of the other ones. The server isn't accessible
right now so I'm not able to check in right now. I'll have bash
tomorrow morning. These last warning fixes won't affect runtime at
all so the 2.8.0-rc1
Hi JS et. al,
On Mon, Feb 2, 2009 at 8:51 PM, Jean-Sébastien Guay
jean-sebastien.g...@cm-labs.com wrote:
Sooo... What are you planning as an upload area for packages? :-) You said
we'd put them into SVN, but do you plan to give all of us commit access to a
given area of the SVN? Perhaps an FTP
Hi,
svn rev 9631 builds correctly on CentOS 4.7:
- Kernel: 2.6.9-78.0.8.ELsmp
- gcc: 3.4.6-10
I have also setup a continuous build for trunk which will keep on
building until 2.8 is out! Appreciate everybody's effort in getting 2.8
out asap;)
Best regards,
John
Robert Osfield wrote:
Hi
Hi Melchoir,
On Tue, Feb 3, 2009 at 7:33 AM, Melchior FRANZ melchior.fr...@gmail.com wrote:
Just for the record: I've had several segfaults in OSG's
particle code (threading related) since I updated a few
days ago. I'll post a backtrace when I run into it again.
The particle code has changed
Hi Umit,
On Tue, Feb 3, 2009 at 3:58 AM, Ümit Uzun umituzu...@gmail.com wrote:
Sorry for late but I have already tried 2.8 :)
There are some problem, while using osgviewer sometimes there was a Error:
[Screen #0] GraphicsWindowWin32::swapBuffersImplementation() - Unable to
swap display
About the stats display problem, it's resolved here, thanks !
On Tue, Feb 3, 2009 at 10:15 AM, Robert Osfield robert.osfi...@gmail.comwrote:
Hi Umit,
On Tue, Feb 3, 2009 at 3:58 AM, Ümit Uzun umituzu...@gmail.com wrote:
Sorry for late but I have already tried 2.8 :)
There are some
Hi All,
So are we ready for the OSG-2.8 branch?? It looks like we are a good
position to tag. Please raise your hand now if there is something
amiss that I need to address.
Cheers,
Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
Hi Sukender,
On Tue, Feb 3, 2009 at 11:26 AM, Sukender suky0...@free.fr wrote:
Uh??? I sent you a 7z file... it's okay if it's binary, isn't it?
There wasn't an extension on the end of the file, I didn't get to find
out that it was a 7z file...
Here is a zip with only the CSV inside (the txt
Hi Sukender,
On Tue, Feb 3, 2009 at 11:41 AM, Robert Osfield
robert.osfi...@gmail.com wrote:
From looking at the file was is very clear is that
include\osgIntrospection\TypedMethodInfo generates almost all the
warnings. So I'd suggest we using a #pragma to disable the specific
C4121 warning
Building on Windows XP, Visual Studio 2008 sp1. All builds fine, but
getting same warnings as Sukender (haven't tried your latest updates
Robert...about to rebuild with latest revision).
Examples run good except getting crash in osgTexture2D with a map/set
iterator not incrementable error. This
Hi Donald,
This looks to be a threading issue with the text label being updated
while being rendered.
There was no text-setDataVariance(DYNAMIC) so I've added this, and
checked this change into svn/trunk. Could you please test. Modified
osgtexture2D.cpp also attached.
Robert.
On Tue, Feb 3,
Hi Sukender,
If we can't work out what it's on a bout and the warning looks benign,
should we just suppress it?
Robert.
On Tue, Feb 3, 2009 at 1:56 PM, Sukender suky0...@free.fr wrote:
Hi Robert,
Not many ideas, but:
- This may be related to the IC class used at this moment. Unfortunately,
Hi Robert, hi all,
const T *v: When T is a function, I guess the compiler reads pointer to a
const function instead of const pointer to a function. Thus the const
applied on a function has no meaning. I don't know, however, how to avoid this,
since const (T *) v will result in a parse error.
Hi Windows experts,
Here's another Windows warning that I'll like a hand resolving:
2..\common\Atomic.cpp(133) : warning C4239: nonstandard extension
used : 'static_cast' : conversion from 'volatile const long' to
'volatile const unsigned int '
The code is:
Atomic::operator unsigned() const
{
Hi Morne,
On Tue, Feb 3, 2009 at 2:54 PM, Morné Pistorius
mpistorius@googlemail.com wrote:
Hi Robert,
I think in VS, specifiying something as just unsigned causes the
compiler to read unsigned int.
If you change the line to
return static_castunsigned long const volatile (_value);
I
Sukender wrote:
Hi Robert, hi all,
const T *v: When T is a function, I guess the compiler reads pointer to a const function
instead of const pointer to a function. Thus the const applied on a function has no meaning. I don't know,
however, how to avoid this, since const (T *) v will result in
Hi Robert,
After the last discussion on this topic I end up leaning towards not
using svn for binaries. The server supports webdav as well as ftp.
I'll go an experiment with these routes and report back.
OK, let me know.
J-S
--
__
HI Window dev's,
I've now checked in fixes for the majority of the warnings that
Sukender reported, there are a few left:
2..\common\Atomic.cpp(133) : warning C4239: nonstandard extension
used : 'static_cast' : conversion from 'volatile const long' to
'volatile const unsigned int '
Robert,
That did indeed fix the issue.
Thanks,
Donny
On Tue, Feb 3, 2009 at 6:43 AM, Robert Osfield robert.osfi...@gmail.comwrote:
Hi Donald,
This looks to be a threading issue with the text label being updated
while being rendered.
There was no text-setDataVariance(DYNAMIC) so I've
On Tue, Feb 3, 2009 at 10:41 AM, Tony Horrobin
a.j.horro...@its.leeds.ac.uk wrote:
I believe it is due to virtual inheritence of Object as in CullCallback -
NodeCallback - Object.
Ahh... good clue... I've added an explicit initialization of the
osg::Object and checked it in, fingers crossed
Hi Guys,
Since I've had no feedback on the remaining WIndows warnings I've gone
ahead and added pragma's to suppress the following warnings that
seemed to be appropriate for supression given that fixes aren't
possible/don't look easily resolvable, and the warnings don't point to
a real problem in
Robert,
Removing the generates another warning:
warning C4197: 'volatile const unsigned int' : top-level volatile in cast is
ignoredc:\OpenSceneGraphSVN\src\OpenThreads\common\Atomic.cpp133
OpenThreads
However, changing line 133 to just
return _value;
generates no warnings on Visual
Hi Donald,
On Tue, Feb 3, 2009 at 5:03 PM, Donald Cipperly osgc...@gmail.com wrote:
Removing the generates another warning:
warning C4197: 'volatile const unsigned int' : top-level volatile in cast is
ignoredc:\OpenSceneGraphSVN\src\OpenThreads\common\Atomic.cpp133
OpenThreads
Hi All,
I can't quite fathom the following warning either...
164..\..\include\osgIntrospection/Value(373) : warning C4180:
qualifier applied to function type has no meaning; ignored
164..\..\include\osgIntrospection/TypedMethodInfo(84) : see
reference to function template instantiation
Hi,
I believe it is due to virtual inheritence of Object as in CullCallback -
NodeCallback - Object.
Cheers,
-Tony
[quote=Jeremy Moles]On Mon, 2009-02-02 at 17:32 +, Robert Osfield wrote:
[quote]HI Jeremy,
On Mon, Feb 2, 2009 at 5:19 PM, Jeremy Moles wrote:
The only MAJOR one I'm
Hi Ümit,
There are some problem, while using osgviewer sometimes there was a
Error: [Screen #0] GraphicsWindowWin32::swapBuffersImplementation() -
Unable to swap display buffers problem.
And almost all examples working on my system but osgprecipictation
example make my computer lock and
Sukender wrote:
Hi Robert, hi all,
const T *v: When T is a function, I guess the compiler reads pointer to a const function instead of const pointer to a function.
That's not specific to functions, as const C *c where C is a class
means the same: c is a pointer to a const instance of C. If
Hi Robert,
Not many ideas, but:
- This may be related to the IC class used at this moment. Unfortunately,
there is no clue in the log about which IC causes it, except it's in osgDB
wrapper. So this may be the DatabasePager. Perhaps is it linked to:
I_StaticMethod0(osgDB::DatabasePager
Hi All,
I'm look at the follow warning under Windows. I can't figure out why
there is a warning of this type:
152d:\prog\libs\openscenegraph\include\osgintrospection\typedconstructorinfo(36)
: warning C4702: unreachable code
The code is:
templatetypename C, typename IC
struct
Hi Robert,
I think in VS, specifiying something as just unsigned causes the
compiler to read unsigned int.
If you change the line to
return static_castunsigned long const volatile (_value);
I think the warning will disappear.
Cheers,
Morne
On Tue, Feb 3, 2009 at 2:48 PM, Robert Osfield
Hi Sukender,
Could you send the file as an ascii file, just came through as binary here.
W.r.t warnings, if we can't fix them easily and non-intrusively then
we'll have to suppress them.
Robert.
On Tue, Feb 3, 2009 at 10:12 AM, Sukender suky0...@free.fr wrote:
Hi Robert,
As the dashboard
Hi All,
I'm still waiting on feedback from a few emails regarding failed
builds reported on CDash, and email from Mathias Froehlich on the
Atomic.cpp volatile related warning, but as it's into the evening here
at the westerly end of Europe I'd guess we won't get a reply tonight.
I could press
Sukender wrote:
Hi Robert, hi all,
const T *v: When T is a function, I guess the compiler reads pointer to a
const function instead of const pointer to a function.
That's not specific to functions, as const C *c where C is a class
means the same: c is a pointer to a const instance of C. If
My mistake, I meant that the volatile and should be removed (not the
whole static_cast).
May static_castunsigned int do it? (since I'm not certain volatile here is
useful, because we simply return a copy).
Sukender
PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/
Hi Robert,
Sorry about not anwsering sooner, but I was very busy this late afternoon.
I sum up:
About the #1 and #3 warnings (C4239 nonstandard extension, and C4180), I
suggested in previous posts static_castunsigned int and an
add_const-like solution... does it make sense for you?
About
I don't even understand the reason of the static_cast... why it is there?
IMHO, it should be removed, but I'm no Atomic/Threads/etc expert.
Sukender
PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/
Le Tue, 03 Feb 2009 15:48:03 +0100, Robert Osfield
Hi Robert, STOP
Experimental build launched on rev. 9622 (trunk) STOP
Using VC8sp1 STOP
See results on dashboard when available (Machine's name is SUKENDER1) STOP
Should be finished in... err... when it's done! :)
STOP
Sukender STOP
PVLE - Lightweight cross-platform game engine -
On Mon, Feb 2, 2009 at 3:01 PM, Robert Osfield robert.osfi...@gmail.com wrote:
I will now go across the machines I have and test out the build with a
fresh checkout. I'll also do testing on an OSX box that I can
remotely log into - I'll test just the CMake/Makefile build though,
won't be able
Hi Morne,
On Mon, Feb 2, 2009 at 3:39 PM, Morné Pistorius
mpistorius@googlemail.com wrote:
I successfully built the current trunk on Windows, VS8. Attached are
more warnings if you are interested (about 71), they look to be mostly
benign.
Thanks, I'll do a review of the warnings and look
On Mon, 2009-02-02 at 15:01 +, Robert Osfield wrote:
Hi All,
I've now finished all the merges/bug/features fixes that is required
for OpenSceneGraph-2.8 branch. I had to do a few more changes since
2.7.9 than I would have liked due to resolve usage problems associated
with the
Hi all,
Here everything build fines under WinXP, VS8 SP1.
But I have a little question, when I call :
osviewer.exe --window 100 100 800 600 cow.osg
Then I try to display the stats, nothing appears before several hits on the
s button, and I just see some parts of the stats, is it normal ?
On
On Mon, 2009-02-02 at 17:20 +0100, Sukender wrote:
Hi Jeremy, hi Robert,
Robert: Dashboard updated.
Jeremy: What kind of machine do you have??? It seems to take ages to compile
on my computer (Core2Duo 2.5Ghz)! Or maybe you've compiled just before and
there was few to recompile...
I have
Hi Jeremy,
Could you please capture the warnings you are getting now. They are
almost certainly be the same set as the original warnings you sent as
I have fixed hundreds and hundreds and hundreds of warnings, having
spent well over a week of my life dedicated to just aggressive
warnings level.
Hi Sukender,
Alright... Strange thing it took 40 minutes on my machine (which is faster than
your laptop, and I had a few *.cpp already compiled). Or maybe you disable
compiling wrappers, examples, applications, plugins or such (I do compile them
all)?
If you don't use the wrappers,
Hi J-S,
Hem... I *do* use osgGA wrapper... And yes, I saw they cost much in compile
time. :)
Sukender
PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/
Le Mon, 02 Feb 2009 17:36:49 +0100, Jean-Sébastien Guay
jean-sebastien.g...@cm-labs.com a écrit:
Hi Sukender,
On Mon, 2009-02-02 at 17:44 +0100, Sukender wrote:
Hi J-S,
Hem... I *do* use osgGA wrapper... And yes, I saw they cost much in compile
time. :)
Yeah, I don't compile the introspection stuff because it makes it take
about 40 minutes here, too.
Sukender
PVLE - Lightweight cross-platform
Hi Serge,
On Mon, Feb 2, 2009 at 4:32 PM, Robert Osfield robert.osfi...@gmail.com wrote:
Ack... two steps forward, one step back... Looks like a bug fix for
another stats rendering problem broke this particular combination. I
see the problem under Linux as well so can chase it up personally.
Thanks Robert, I'll only be able to test tomorrow morning but i'll let you
know.
On Mon, Feb 2, 2009 at 6:13 PM, Robert Osfield robert.osfi...@gmail.comwrote:
Hi Serge,
On Mon, Feb 2, 2009 at 4:32 PM, Robert Osfield robert.osfi...@gmail.com
wrote:
Ack... two steps forward, one step back...
On Mon, 2009-02-02 at 16:23 +, Robert Osfield wrote:
Hi Jeremy,
Could you please capture the warnings you are getting now. They are
almost certainly be the same set as the original warnings you sent as
I have fixed hundreds and hundreds and hundreds of warnings, having
spent well over
HI Jeremy,
On Mon, Feb 2, 2009 at 5:19 PM, Jeremy Moles jer...@emperorlinux.com wrote:
The only MAJOR one I'm getting anymore is this:
In copy constructor
'osgViewer::InteractiveImageHandler::InteractiveImageHandler(const
osgViewer::InteractiveImageHandler, const osg::CopyOp)':
On Mon, 2009-02-02 at 17:32 +, Robert Osfield wrote:
HI Jeremy,
On Mon, Feb 2, 2009 at 5:19 PM, Jeremy Moles jer...@emperorlinux.com wrote:
The only MAJOR one I'm getting anymore is this:
In copy constructor
'osgViewer::InteractiveImageHandler::InteractiveImageHandler(const
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Osfield wrote:
On Mon, Feb 2, 2009 at 3:01 PM, Robert Osfield
robert.osfi...@gmail.com wrote:
I will now go across the machines I have and test out the build
with a fresh checkout. I'll also do testing on an OSX box that I
can remotely
Hi Jeremy,
On Mon, Feb 2, 2009 at 7:11 PM, Jeremy Moles jer...@emperorlinux.com wrote:
The warning remains with the latest revision; osg::Object must also be
initialized for this warning to go away. Why this is the case, I do not
know.
This class doesn't directly inherit from osg::Object, I
Hi Sukender (et. al)
On Mon, Feb 2, 2009 at 4:20 PM, Sukender suky0...@free.fr wrote:
Robert: Dashboard updated.
Jeremy: What kind of machine do you have??? It seems to take ages to compile
on my computer (Core2Duo 2.5Ghz)! Or maybe you've compiled just before and
there was few to
Hi All,
Thanks for the all the testing, a few more bugs and warnings have been
fleshed and should be now resolved, alas this has taken me pretty well
all the day, so it's now too late for me to go create the
OpenSceneGraph-2.8 today. What I'll do is leave svn/trunk to be
tested over night and in
Hi Robert,
Once 2.8.0-rc1 is done, it'll be time to even more build and runtime
testing, and for those planning to help out with packaging to start
creating packaging for the rc1.
Sooo... What are you planning as an upload area for packages? :-) You
said we'd put them into SVN, but do you
Hi Robert,
Second experimental build launched. (SUKENDER1 2009-02-02 on the dashboard, rev
9631, VC8sp1, all inclusive).
Maybe you'll have the result before going to sleep (= To all: this is a
joke... Robert NEVER sleeps! :D Even kill_and_go_to_bed -9 can't get rid of
him!!!)
Sukender
PVLE -
+1 :)
Sukender
PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/
Le Mon, 02 Feb 2009 21:51:05 +0100, Jean-Sébastien Guay
jean-sebastien.g...@cm-labs.com a écrit:
Hi Robert,
Once 2.8.0-rc1 is done, it'll be time to even more build and runtime
testing, and for
Robert Osfield wrote:
I've now finished all the merges/bug/features fixes that is required
for OpenSceneGraph-2.8 branch. I had to do a few more changes since
2.7.9 than I would have liked due to resolve usage problems associated
with the osg::TransferFunction1D class. TransferFunction1D has
Quick note: build is done, but most warnings are wrappers-related (and seem
harmless).
Sukender
PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/
Le Mon, 02 Feb 2009 21:54:34 +0100, Sukender suky0...@free.fr a écrit:
Hi Robert,
Second experimental build launched.
Hi Serge,
On Mon, Feb 2, 2009 at 4:21 PM, Serge Lages serge.la...@gmail.com wrote:
Here is a screenshot fo my bug.
Ack... two steps forward, one step back... Looks like a bug fix for
another stats rendering problem broke this particular combination. I
see the problem under Linux as well so
Alright... Strange thing it took 40 minutes on my machine (which is faster than
your laptop, and I had a few *.cpp already compiled). Or maybe you disable
compiling wrappers, examples, applications, plugins or such (I do compile them
all)?
Sukender
PVLE - Lightweight cross-platform game engine
On Mon, 2009-02-02 at 17:32 +, Robert Osfield wrote:
HI Jeremy,
On Mon, Feb 2, 2009 at 5:19 PM, Jeremy Moles jer...@emperorlinux.com wrote:
The only MAJOR one I'm getting anymore is this:
In copy constructor
'osgViewer::InteractiveImageHandler::InteractiveImageHandler(const
Hi Robert,
In tests with my app I found some curious behaviour with the
QOSGWidget (non-GraphicsWindowEmbedded) implementation.
Since moving from the GLWidget approach to this, the throwing
functionality of the TrackballManipulator disappeared. This is also
visible in the osgViewerQt
Hi Robert,
I successfully built the current trunk on Windows, VS8. Attached are
more warnings if you are interested (about 71), they look to be mostly
benign.
In tests with my app I found some curious behaviour with the
QOSGWidget (non-GraphicsWindowEmbedded) implementation.
Since moving from
Hi Jeremy, hi Robert,
Robert: Dashboard updated.
Jeremy: What kind of machine do you have??? It seems to take ages to compile on
my computer (Core2Duo 2.5Ghz)! Or maybe you've compiled just before and there
was few to recompile...
Sukender
PVLE - Lightweight cross-platform game engine -
Just for the record: I've had several segfaults in OSG's
particle code (threading related) since I updated a few
days ago. I'll post a backtrace when I run into it again.
m.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
92 matches
Mail list logo
