Hi Martin, Hm.... I thought I had made those fixes and checked them in. Evidently not. They should be there now.
On 11/28/06, Martin Spott <[EMAIL PROTECTED]> wrote:
"Don Burns" wrote: > That fix _seems_ simple enough, but is complicated slightly by two issues. > 1) ConfigLexer.cpp (which contains the bracketed <FlexLexer.h> is a > generated file, which means that any changes I make to it will get reset the > next time I generate the file. 2) FlexLexer.h actually is a system file for > systems that have "flex" installed, and is only included in the current > directory for systems that do not have flex installed. Your auto-generated ConfigLexer.cpp requires a certain version of FlexLexer.h - otherwise the error would not have shown up (at least the last time I checked). If you require people to install a distinct version of system header files then you should probably mention this in the build notes the next time.
Noted. I'm not actually requiring any installation, however, similar to the request that users not need to install DWMake, the FlexLexer.h file is in the Producer distribution. All compilers that I know of will look in the directories specified by the -I flag before looking in system directories, so its presence in the source directory should be sufficient for a smooth build. Am I missing something?
Could we move discussion of Producer over to Producer-users? Honestly, I'm not inclined to subscribe to Yet Another Mailing List just to post reports to bugs that (I assume) affect other users on this list as well. Moving this sort of reports to "the other list" also doesn't match my understanding of your claims _not_ to develop the separation of Producer from OpenSceneGraph ....
Just to be clear, Producer and OpenSceneGraph are distinct and separate projects. What I've asserted is that, as far as my role is concerned, these will continue development in parallel cooperation, and I will take no action to divide the community. It has become very clear over the developments of the past year and a half that Producer and OSG will not be integrated. Developments in OSG have indicated that it is moving away from Producer. So, for Producer to continue development, it needs to do so in a separate venue. This does not imply in the least way, that Producer will discontinue support of OSG, but it does allow Producer to begin to grow without having to resolve conflicting design philosophies where they are not relevant. (We're all tired of the arguments and having two lists is a peaceful resolution to that problem). Also, I hear often, users say they don't use Producer for their projects. The choice for Producer issues to be discussed on the Producer-users list is a reasonable one and keeps those issues out of the hair of those who don't use Producer. There is a separate mailing list for OpenThreads as well. This has not been an issue there. Well, it's ok for me to send such reports via private EMail if you
don't want to monitor this list any more,
To administer proper support of OSG, I must continue to monitor this list. My role, however, has changed from maintainer-contributor to just-another-user. -don Martin.
-- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
