the main reason I would want to go in this way... is to offer a
solution that could benefit many.
- Original Message -
From: "Jean-Sébastien Guay"
To: "OpenSceneGraph Users"
Sent: Thursday, June 04, 2009 3:28 PM
Subject: Re: [osg-users] Can I change the plugin
Hi James,
In short... I do not want to challenge the current workflow of either
paradigms, but rather describe how both are well-defined, and maybe
there are others out there who would like to see how we are doing it,
when/if we offer a submission.
Thanks for explaining where you're coming f
Hi Rick,
> I even gave you a batch file that would do some of that
automatically, and it's easy to supplement that with a couple more
commands that will do it all automatically (see below).
You did? Maybe I missed it. Could you please send it again? This does
not look nearly as hard as I
Oh, and about being apologetic; I have seen posts on the forum where people
are grousing that make me feel that people are just not thankful for how
great this all is. I never wanted anyone to think I am not grateful for OSG
(or your time for trying to explain it to me). I can see that there mos
> I even gave you a batch file that would do some of that automatically, and
it's easy to supplement that with a couple more commands that will do it all
automatically (see below).
You did? Maybe I missed it. Could you please send it again? This does not
look nearly as hard as I had imagined. P
Hi Rick,
I just want to be clear: I am not saying the way it is now is the only
way. I'm just saying that it works well enough for lots (and lots, and
lots) of people. I don't want to start a tug of war of whose way is
better...
The fact is, in my personal situation, the version numbers on e
t;OpenSceneGraph Users"
Sent: Tuesday, June 02, 2009 6:12 PM
Subject: Re: [osg-users] Can I change the plugin directory structure?
Hi Rick,
I don't think I quite communicated what I meant to say in the end there.
I am not super bothered by the whole naming thing, just a bit irritate
If the switch were the default sure. Right now there IS a switch with a
name that infers it would do what I want, but it just doesn't work and in
fact breaks other things. That switch is off by default (or ON I should
say, adding versioning info to the DLL's). It is even an advanced switch
that
Hi Rick,
I don't think I quite communicated what I meant to say in the end
there. I am not super bothered by the whole naming thing, just a bit
irritated and in my organization I think it causes more problems that it
is worth. I was hoping that perhaps with the power of CMake that
someone h
Hi Rick,
It seems like there is all this effort going towards just keeping people
from picking up the wrong version of the DLLs. How often does that
happen anyway?
Until these mechanisms were put into place, every week there would be
several reports of crashes and other weird behavior that
I don't think I quite communicated what I meant to say in the end there. I
am not super bothered by the whole naming thing, just a bit irritated and in
my organization I think it causes more problems that it is worth. I was
hoping that perhaps with the power of CMake that someone had already
prov
> With the command line SVN it's easy to script whatever you want. I really
> think you're making a mountain out of an ant hill. It's useful
> functionality, and all it takes on your side is a few more steps (not that
> often, unless you recompile OSG extremely often) or a little scripting.
>
> But
Hi Rick,
History is not all that helpful anyway since they are binaries.
I didn't mean the diff between files, but the update history. It's
useful to know that this file was updated from OSG 2.6 to OSG 2.8 on a
given date. That way if you started having problems with a given loader
on a gi
> So yes, either delete the old one and add the new one or rename the
directory and then checkin the updated plugin DLLs over the old ones...
That is unfortunate :(
> (which is not exactly the same thing, it preserves history, so SVN will
know they're actually the same files).
History is not all t
Hi Rick,
Well, which Plugin directory am I supposed to add? If I add a
particular plugin directory with a given name, and then I do an update
and the plugin version changes, then the folder name is not the same
anymore. Do I add the new plugin folder and delete the old one?
Perhaps use SVN
> Why is it hard? Just svn add the whole directory, that should add all
contents and subdirectories by default... Unless I'm missing something?
Well, which Plugin directory am I supposed to add? If I add a particular
plugin directory with a given name, and then I do an update and the plugin
versi
Hi Rick,
So for the examples, is there any way to set the Working Directory for
debugging? It is actually pretty easy to select all of the apps and
examples and then set properties for all configurations at one time, so
that is not such a big deal, but I was curious.
I don't know of any way
> You say your examples are in bin\Release. This is not the case for me;
there
> is no bin\Release in my build dir. The release build of my osganimate.exe
> file is in "\bin". Not sure why yours would be elsewhere,
but
> this appears to be the source of your problem. What CMake variables did
you
>
Hello Rick,
> Once you've run the ALL_BUILD target (or INSTALL, which depends on
ALL_BUILD) then the examples will find the plugins just fine, you can
run them with F5 no problem.
I am not finding this to be the case. When running with F5 or Ctrl-F5,
VS runs the example from where it compi
> I am not finding this to be the case. When running with F5 or Ctrl-F5,
> VS runs the example from where it compiled to, NOT where the INSTALL
> project sends it. In my case, "bin\Release\".
I'm not able to reproduce this problem, Rick. To test, I blew away my
installed OSG (deleted C:\Progr
> I have recopied email in plain text below:
>
> James Killian
> - Original Message - From: "James Killian" <
> james_kill...@hotmail.com>
> To: "OpenSceneGraph Users"
> Cc: "Rick Pingry"
> Sent: Thursday, May 28, 2009 10:25 PM
>
> Subjec
microsoft to do something about it) : (
I have recopied email in plain text below:
James Killian
- Original Message -
From: "James Killian"
To: "OpenSceneGraph Users"
Cc: "Rick Pingry"
Sent: Thursday, May 28, 2009 10:25 PM
Subject: Re: [osg-users] Can I ch
Hi James,
Again with the black background and black text in your message... very
hard to read. I thought you'd fixed this? :-)
J-S
--
__
Jean-Sebastien Guayjean-sebastien.g...@cm-labs.com
http://www.cm-labs.
Re: [osg-users] Can I change the plugin directory structure?
Hello Rick,
> I have noticed that for the past little while the plugins are compiled
> to their own directory with the version number. I am not quite sure why
> this is beneficial, it seems like you would
Hi Paul,
You don't have to be on this list very long to see the same question pop up
multiple times. I'm guilty of it myself. :-)
Sure, but I prefer to remind people that the archives exist, while at
the same time giving answers to their questions, rather than "let it
slide". I figure it's m
> Incidentally, this has been discussed a lot in the past, so searching the
> archives would have turned up all this info
You don't have to be on this list very long to see the same question pop up
multiple times. I'm guilty of it myself. :-)
-Paul
_
Hello Rick,
I have noticed that for the past little while the plugins are compiled
to their own directory with the version number. I am not quite sure why
this is beneficial, it seems like you would always want the plugins
compiled with the version of OSG you have compiled, and it seems that
Hello All,
I have noticed that for the past little while the plugins are compiled to
their own directory with the version number. I am not quite sure why this
is beneficial, it seems like you would always want the plugins compiled with
the version of OSG you have compiled, and it seems that havin
28 matches
Mail list logo
