I didn't find anything about this when I googled so I guess I'll
check out their newsgroup. Both are evidently dependent on the same
package, for Video for Windows, so I removed it from the JVCL.
I've always thought Delphi Packages should work as DLL's do
now...that is, they should not conflict with each other. Instead of
being loaded and kept in a single directory, they should be in separate
directories named for each component set. That would also prevent
versioning problems.
Also, I don't much like the way Vista stores them, or for that
matter how its whole folder setup is organized. I did an upgrade from
XP Pro, and I now have four separate folders for my user name, all with
shortcuts that are inaccessible. So I work from an Explorer shortcut
that takes me right to my main C:\ drive and access my Document and
Settings folder only from there. But the bpl's don't even show up on my
drive! They're under a virtual "public" folder. Microsoft has really
over-complicated things!
from Robert Meek dba "Tangentals Design"
e-mail: [EMAIL PROTECTED]
Freelance Windows Programming for XP and Vista
Also proud to be a Moderator of the "Delphi-List" at elists.org
"Reality cannot be explained...only enjoyed or endured as your current
perspective allows!"
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Rob Kennedy
Sent: Wednesday, June 27, 2007 7:08 PM
To: Borland's Delphi Discussion List
Subject: Re: GLScene for Delphi
Robert Meek wrote:
> I didn't save the e-mail in which GLScene was mentioned, but you
> know who you are.
Perhaps Google can find it for you:
http://www.google.com/search?q=glscene+site%3Aelists.org
> If you or anyone else has installed it into D2007 did
> you have success compiling the packages? It seems like everything
goes
> okay until it errors out with a conflict due to a dependent package it
> says is also in the Jv Library I have installed. Is it possible to
get
> around that?
Do they both contain a unit by the same name? Or do they both require a
package of the same name?
Either way, the solution should be simple: Remove or rename the
offending module.
--
Rob
_______________________________________________
Delphi mailing list -> [email protected]
http://www.elists.org/mailman/listinfo/delphi
_______________________________________________
Delphi mailing list -> [email protected]
http://www.elists.org/mailman/listinfo/delphi
