, Jun 26, 2008 at 4:12 PM, Eric Sokolowsky [EMAIL PROTECTED]
wrote:
I'm presently compiling the X11 path. Will let you know what happens.
Thanks, look forward to hearing how you get.
Just had a thought, is there a chance that the X11 path will work fine
as a 64bit build? X11 has supported
I have also used OSG on 64-bit Linux without any problems. I know nothing
about 64-bit Windows. On Mac OSX, OSG is not 64-bit capable because the
windowing functions used to glue OSG to the windowing system are
Carbon-based, and they are deprecated and are not available for 64-bit
programs. A few
.
As for a Cocoa implementation of GraphicsWindow and PixelBuffer, is
Cocoa fully threadable? Are there other constraints that it'll apply
to the way we open, render to, and get events from the windows?
Robert.
On Thu, Jun 26, 2008 at 1:42 PM, Eric Sokolowsky [EMAIL PROTECTED]
wrote:
I
?
Robert.
On Thu, Jun 26, 2008 at 1:42 PM, Eric Sokolowsky [EMAIL PROTECTED]
wrote:
I have also used OSG on 64-bit Linux without any problems. I know
nothing
about 64-bit Windows. On Mac OSX, OSG is not 64-bit capable because
the
windowing functions used to glue OSG to the windowing
I'm presently compiling the X11 path. Will let you know what happens.
On Fri, Jun 20, 2008 at 3:20 PM, Robert Osfield [EMAIL PROTECTED]
wrote:
Hi All,
To help out an present3D end working under OSX, who was having
problems with the Carbon version of osgViewer, I have added an option
This is a good point. I should have thought about this. I will for the
future. Thanks for testing!
I also agree that we should require CMake 2.6 for OSX platform.
-Eric
On Fri, Jun 20, 2008 at 11:02 PM, Jean-Sébastien Guay
[EMAIL PROTECTED] wrote:
Hi Eric,
I have named the files so that
other OSX users dive in here and
test out these changes, if things look OK I'll merge them tomorrow.
Could OSX users also try out the option to build against X11 I made
earlier.
Thanks,
Robert.
On Fri, Jun 20, 2008 at 10:07 PM, Eric Sokolowsky [EMAIL PROTECTED]
wrote:
I have made
Yes, the Xcode generator seems to have problems. I have been playing
with the cmake source code and many things are hard-wired and not
configurable. There are settings documented that are handled in the
cmake code but don't seem to have any effect on the xcode project
generated (notably
Stephen,
I have been working with Eric Wing here at WWDC to improve the CMake
generator for Xcode when compiling OSG. I noticed your question on the OSG
mailing lists:
* I need some CMake-advice. I found a solution for the linker-error, I**
have to add**
Loading a large number of images all at once might be overloading your
memory capacity. Even if you can fit all of the images in main memory at
once, doing it this way does not scale very well. Google Earth does it this
way and it chokes hard when loading larger animations.
Remember that even if
There is a build error (OSX tested) with latest svn (revision 8434), in the
DatabasePager (I don't have the exact error right now). Reverting to build
8425 seems to fix the problem:
svn update -r8425
It looks like the refactoring from RequestQueue to ReadQueue didn't get
finished or completely
The latest SVN of osg has a problem when generating xcode projects with
cmake. In the main directory, CMakeLists.txt on line 349, is the following:
ADD_DEFINITIONS(-DOSG_DEBUG_POSTFIX='\${CMAKE_DEBUG_POSTFIX}\')
This causes problems on OSX. I would like to change this line to:
Yes, I am using Cmake 2.6, with OSG svn, on the Mac. The symptoms of the
problem is that when Xcode tries to open a project generated by cmake, it
complains about syntax problems in the project file. Eric Wing worked around
the problem by not allowing a changed postfix.
Is there any reason we
On Thu, Jun 12, 2008 at 1:14 PM, Jean-Sébastien Guay
[EMAIL PROTECTED] wrote:
Hello Eric,
Is there any reason we shouldn't require CMake 2.6 when compiling the
latest OSG?
I don't think it's really that useful to require that everyone update their
CMake version to 2.6 just for this. We
I'm willing to help port bug fixes back to stable branches. I have an
ulterior motive though; I made a particular change in the Inventor
plugin that is now in SVN that I would like to see in a stable release.
I think that only bug fixes should be ported back; API changes would
have to wait for
/html
%{_libdir}/pkgconfig/producer.pc
%{_libdir}/libProducer.so
%{_includedir}/Producer
%changelog
* Wed Oct 11 2006 Eric Sokolowsky [EMAIL PROTECTED] 1.2
- Removed irrelevant build dependencies.
- Added requirement for libstdc++ version.
- Removed Introspection and glut.
- Compiles with -j 3
I'm porting my application from OSG 1.2 using osgProducer::Viewer to OSG
svn. Most of the port was straightforward, though I'm encountering some
strangeness.
My questions:
1. Is there a page on the wiki that covers porting OSG 1.2 to current
OSG? I'd like to add some of my notes to that page
I have been away from OSG development for some time and am getting back
into it. I'm trying to see if my application will port to OSG 2.4 using
the osgViewer instead of OSG 1.2 using osgProducer::Viewer. As I was
running the new osgviewer application I noticed that there are some
command-line
Eric Sokolowsky wrote:
The help is placed from the
osgviewer application and the place where the options are read is now in
the osgviewer application source. Both of these things should be in the
osgViewer::Viewer class source to ease maintainability and reusability.
Correction: The first
there:
Paul Martz
Bob Kuehne
Eric Sokolowsky
Donald Leich
Steve Satterfield
John Kelso
Glenn Waldron
Jean-Sebastien Guay
Paul Brewster
I think there were a couple of others there, but I don't know their names.
Paul showed his occluder work, and there were other presentations by
Donald Leich and J.S
OSG users,
At last night's OSG user meeting in Washington D.C., sponsored by Paul
Martz and Bob Kuehne, we discussed the possibility of submitting a
course again to Siggraph. We don't have much time (the deadline is
January 30), but I think that we can tweak last year's submission to be
ready
Craig, Joel S. (SED/TMI) wrote:
Classification: UNCLASSIFIED
Caveats: NONE
Greetings,
We use a ScalarBar in our app (OSG 2.0, x86-dual core, Red Hat). When it
is created, we get the warning that the file fonts/arial.ttf cannot be
found. We have our fonts files in a different
Robert Osfield wrote:
Hi John,
On 9/15/07, John Steinbis [EMAIL PROTECTED] wrote:
Thanks Robert,
I have this working now without rescaling the image. My solution was
to pad the image with zeros making it a power of two and then specify
the correct percentage of the image to use as 2D
Eric Wing and other OSX experts,
I used Xcode to compile OSG for my OSG 1.2 application that uses
osgProducer::Viewer. I just used the regular Producer.framework to
create my application. Is this the best solution, or should I be using
the Producer_X11.framework or Producer_AGL.framework? What
Ricko 3D wrote:
Just an idea (sorry if it was discussed previously - I'm new here)... how
about an actual discussion forum (like vBulletin) to compliment the wiki. No
offense intended but I haven't seen a mailing list used for all discussions
on a technical project since the late 90's (I
Once upon a time, I compiled my OSG application for the Mac. It never
worked quite right, but now I have time to get it right. However, since
I'm relatively new at Mac programming in general and Xcode in
particular, I'm encountering some obstacles.
My application is somewhat more complicated
Eric Sokolowsky wrote:
So I tried again, using the Xcode projects in the OSG repository. I
started with OpenThreads, but I got an error: Unable to create
directory
/Library/Caches/com.apple.Xcode.6060/SharedPrecompiledHeaders/OpenThreads_Prefix-blahblahblah
Ok, no problem I thought. I
Paul Martz wrote:
I'm not sure what specifically hurt our proposal last year. I know our
proposal contained little in the way of curriculum and course notes. For the
s2008 proposal, we'll have OSG books as course material, plus Bob and I will
probably contribute some of the curriculum we've
101 - 128 of 128 matches
Mail list logo