Hi Paul,
no I haven't and you might be right in your assumption. But I
generally do not like to influence and environment with variables
related to libraries that can't be kept on the latest status. In this
case gdal is at version 1.4somthing, so changes are quite impacting.
It may even be that one has two versions of udig running with
different imageio-ext versions, which would cause problems. Or maybe
QGis uses the same variables or maybe some other project we do not
know.
Maybe it is just paranoia, but I stick on the choice.
Andrea
On Tue, Aug 11, 2009 at 11:07 PM, Paul Ramsey<pramsey@xxxxxxxxxxxxxxxxx> wrote:
Have you confirmed that FWTools actually sets those environment
variables globally? I think it might just set them in it's command
shell environment.
P
On Tue, Aug 11, 2009 at 1:13 AM, andrea
antonello<andrea.antonello@xxxxxxxxx> wrote:
I would suggest to do the less invasive, i.e. run the bat.
I don't want to incurr in the wrats of a bunch of angry FWToolsFans,
because they have libs conflicts.
Andrea
On Tue, Aug 11, 2009 at 12:56 AM, Jody Garnett<jody.garnett@xxxxxxxxx> wrote:
Hi Emily:
You got the two options correct; the udig.bat is a way for us to fake
the env variables for a session.
As for which option (a or b) to choose; that depends on you and what
you have time for today - I am happy with either.
Jody
On Tue, Aug 11, 2009 at 2:21 AM, Emily Gouge<egouge@xxxxxxxxxxxxxxx> wrote:
Between these emails and the other ones I've seen from Jody I'm a little
confused :)
What I *think* I can do is:
a) Make an installer that points to the udig.bat file instead of the
udig_private.exe file.
OR
b) Make the installer set the system environment variables GDAL_DATA &
GDAL_DRIVER_PATH. However, this will overwrite these environment variables
if they exist causing conflicts with existing installations of GDAL_DATA and
GDAL_DRIVER_PATH.
I don't think I can make an installer that sets the environment variables of
a program for each "session". I think that would have to be done when the
udig.exe file is created. I could be totally wrong as I don't have that
much experience with NSIS - if you know otherwise please let me know.
So which of the above two do you think are best?
Emily
andrea antonello wrote:
Opps we are talking in Circles :-)
Indeed :)
Emily is making an installer; and thus she can set the variables at a
global level :-)
Aha, I didn't know that. I guessed there would be a way to set them
just for the process. Emily, do you have any idea if that is possible?
I would not want to break anyones Gdal related software, which might
be of several types.
Andrea
Jody
On Mon, Aug 10, 2009 at 8:12 PM, andrea
antonello<andrea.antonello@xxxxxxxxx> wrote:
In an installer we have a chance to set the system environmental
variables. This would allow the udig.exe to work correctly; at the
cost of possible a version conflict with FWTools or anything else
using GDAL.
Don't think that would conflict. We are not setting the vars at global
level. So they would only be available to the launched process, which
is what we want.
Andrea
Jody
On Mon, Aug 10, 2009 at 6:38 PM, andrea
antonello<andrea.antonello@xxxxxxxxx> wrote:
I had a chance to try out the installer you made for 1.2-M6 - it
seems
we missed something in the installer (and it is probably our fault
for
not sending enough email to the list). For this release of uDig we
are
trying to have:
- udig.bat <--- this is what the start menu entry should point to
- udig_private.exe
The idea is that the bat file sets the required environmental
variables (pointing to the included gdal_data folder). Now you could
get your installer to do that? Or just have a short cut to the bat
file for now.
Yes, exactly Jody, the variables needed would be:
GDAL_DATA pointing to the "gdal_data" folder we placed inside the
installation.
GDAL_DRIVER_PATH pointing to the jre\bin\ folder inside which we
placed the imageio-ext stuff.
By doing so we would be able to rename udig_internal.exe to udig.exe
as people expect it to be. The downside is that if someone executes it
from the program files folder, he will miss the imageio-ext
dependencies.
So perhaps easy way to go is to just link to the bat file.
Ciao
Andrea
Jody
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
