Empathy List Archives

NH

nop head

Sat, Nov 26, 2016 9:19 PM

I recently started using OPENSCADPATH to point to my own library. This
works in the GUI but doesn't seem to work for the command line. Is it
supposed to?

I recently started using OPENSCADPATH to point to my own library. This works in the GUI but doesn't seem to work for the command line. Is it supposed to?

TP

Torsten Paul

Sat, Nov 26, 2016 9:32 PM

On 11/26/2016 10:19 PM, nop head wrote:

I recently started using OPENSCADPATH to point to my own library.
This works in the GUI but doesn't seem to work for the command
line. Is it supposed to?

I just tried with the nightly build and that works, I did check
with an absolute path though.

Maybe it behaves differently for relative paths?

You can dump the effective library path with --info, it will
include those from OPENSCADPATH under "OpenSCAD library path".

ciao,
Torsten.

On 11/26/2016 10:19 PM, nop head wrote: > I recently started using OPENSCADPATH to point to my own library. > This works in the GUI but doesn't seem to work for the command > line. Is it supposed to? > I just tried with the nightly build and that works, I did check with an absolute path though. Maybe it behaves differently for relative paths? You can dump the effective library path with --info, it will include those from OPENSCADPATH under "OpenSCAD library path". ciao, Torsten.

NH

nop head

Sat, Nov 26, 2016 10:44 PM

Sorry, my fault. My path was pointing to Program Files (x86) instead of
Program Files and picking up an ancient 32 bit version.

On 26 November 2016 at 21:32, Torsten Paul Torsten.Paul@gmx.de wrote:

On 11/26/2016 10:19 PM, nop head wrote:

I recently started using OPENSCADPATH to point to my own library.
This works in the GUI but doesn't seem to work for the command
line. Is it supposed to?

I just tried with the nightly build and that works, I did check
with an absolute path though.

Maybe it behaves differently for relative paths?

You can dump the effective library path with --info, it will
include those from OPENSCADPATH under "OpenSCAD library path".

ciao,
Torsten.

OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

Sorry, my fault. My path was pointing to Program Files (x86) instead of Program Files and picking up an ancient 32 bit version. On 26 November 2016 at 21:32, Torsten Paul <Torsten.Paul@gmx.de> wrote: > On 11/26/2016 10:19 PM, nop head wrote: > > I recently started using OPENSCADPATH to point to my own library. > > This works in the GUI but doesn't seem to work for the command > > line. Is it supposed to? > > > I just tried with the nightly build and that works, I did check > with an absolute path though. > > Maybe it behaves differently for relative paths? > > You can dump the effective library path with --info, it will > include those from OPENSCADPATH under "OpenSCAD library path". > > ciao, > Torsten. > > > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >

NH

nop head

Sun, Nov 27, 2016 10:54 AM

I suppose that when installing a 64 bit version over a 32 bit version the
installer should remove the old one.

On 26 November 2016 at 22:44, nop head nop.head@gmail.com wrote:

Sorry, my fault. My path was pointing to Program Files (x86) instead of
Program Files and picking up an ancient 32 bit version.

On 26 November 2016 at 21:32, Torsten Paul Torsten.Paul@gmx.de wrote:

On 11/26/2016 10:19 PM, nop head wrote:

I recently started using OPENSCADPATH to point to my own library.
This works in the GUI but doesn't seem to work for the command
line. Is it supposed to?

I just tried with the nightly build and that works, I did check
with an absolute path though.

Maybe it behaves differently for relative paths?

You can dump the effective library path with --info, it will
include those from OPENSCADPATH under "OpenSCAD library path".

ciao,
Torsten.

OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

I suppose that when installing a 64 bit version over a 32 bit version the installer should remove the old one. On 26 November 2016 at 22:44, nop head <nop.head@gmail.com> wrote: > Sorry, my fault. My path was pointing to Program Files (x86) instead of > Program Files and picking up an ancient 32 bit version. > > On 26 November 2016 at 21:32, Torsten Paul <Torsten.Paul@gmx.de> wrote: > >> On 11/26/2016 10:19 PM, nop head wrote: >> > I recently started using OPENSCADPATH to point to my own library. >> > This works in the GUI but doesn't seem to work for the command >> > line. Is it supposed to? >> > >> I just tried with the nightly build and that works, I did check >> with an absolute path though. >> >> Maybe it behaves differently for relative paths? >> >> You can dump the effective library path with --info, it will >> include those from OPENSCADPATH under "OpenSCAD library path". >> >> ciao, >> Torsten. >> >> >> >> _______________________________________________ >> OpenSCAD mailing list >> Discuss@lists.openscad.org >> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >> > >

TP

Torsten Paul

Sun, Nov 27, 2016 6:21 PM

On 11/27/2016 11:54 AM, nop head wrote:

I suppose that when installing a 64 bit version over a 32 bit
version the installer should remove the old one.

I'm not sure that's easily doable, it's two separate installers
and I wonder if people might want both in some cases.

Are there other programs with installers that behave like that?

ciao,
Torsten.

On 11/27/2016 11:54 AM, nop head wrote: > I suppose that when installing a 64 bit version over a 32 bit > version the installer should remove the old one. > I'm not sure that's easily doable, it's two separate installers and I wonder if people might want both in some cases. Are there other programs with installers that behave like that? ciao, Torsten.

NH

nop head

Sun, Nov 27, 2016 6:53 PM

Not sure but when you install a new version of a program you expect it to
nuke the old one. This is an odd case because presumably the old one was so
old there wasn't a 64 bit version at the time, so I installed the 32 bit
version. Under Windows when you install 32 bit apps on a 64 bit system it
fools the installer into putting it in Program Files (x86), even when the
installer thinks it is putting it in Program Files.

On 27 November 2016 at 18:21, Torsten Paul Torsten.Paul@gmx.de wrote:

On 11/27/2016 11:54 AM, nop head wrote:

I suppose that when installing a 64 bit version over a 32 bit
version the installer should remove the old one.

I'm not sure that's easily doable, it's two separate installers
and I wonder if people might want both in some cases.

Are there other programs with installers that behave like that?

ciao,
Torsten.

OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

Not sure but when you install a new version of a program you expect it to nuke the old one. This is an odd case because presumably the old one was so old there wasn't a 64 bit version at the time, so I installed the 32 bit version. Under Windows when you install 32 bit apps on a 64 bit system it fools the installer into putting it in Program Files (x86), even when the installer thinks it is putting it in Program Files. On 27 November 2016 at 18:21, Torsten Paul <Torsten.Paul@gmx.de> wrote: > On 11/27/2016 11:54 AM, nop head wrote: > > I suppose that when installing a 64 bit version over a 32 bit > > version the installer should remove the old one. > > > I'm not sure that's easily doable, it's two separate installers > and I wonder if people might want both in some cases. > > Are there other programs with installers that behave like that? > > ciao, > Torsten. > > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >

M

MichaelAtOz

Sun, Nov 27, 2016 9:25 PM

In my experience few programs go the extra step to allow multiple versions to
be 'installed' together. it's nice when they do, especially for developer
tools where needing multiple versions is common.

Barring that, normally nice installers would update the installation,
including removing old/redundant files & settings (including registry).

Thus I would not expect a 32 bit & 64 bit to be able to co-exist, via an
'installer'.

I usually, baring any specific testing coming up to a new release, have the
latest official release installed (normally 64bit).
I then have a range of old releases and new snapshots manually "installed"
via zip files, copied to the appropriate Program Files for 32/64bit, and a
shortcut manually added to the start/programs list.

There has been registry setting conflict in the past, but that doesn't
change that often.

Admin - PM me if you need anything, or if I've done something stupid...

Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.

The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!

View this message in context: http://forum.openscad.org/OPENSCADPATH-and-command-line-tp19372p19386.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

In my experience few programs go the extra step to allow multiple versions to be 'installed' together. it's nice when they do, especially for developer tools where needing multiple versions is common. Barring that, normally nice installers would update the installation, including removing old/redundant files & settings (including registry). Thus I would not expect a 32 bit & 64 bit to be able to co-exist, via an 'installer'. I usually, baring any specific testing coming up to a new release, have the latest official release installed (normally 64bit). I then have a range of old releases and new snapshots manually "installed" via zip files, copied to the appropriate Program Files for 32/64bit, and a shortcut manually added to the start/programs list. There has been registry setting conflict in the past, but that doesn't change that often. ----- Admin - PM me if you need anything, or if I've done something stupid... Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above. The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out! -- View this message in context: http://forum.openscad.org/OPENSCADPATH-and-command-line-tp19372p19386.html Sent from the OpenSCAD mailing list archive at Nabble.com.

M

MichaelAtOz

Sun, Nov 27, 2016 9:27 PM

copied to the appropriate Program Files for 32/64bit, and a shortcut manually
added to the start/programs list.

With the release numbers as part of the directory/shortcut name. Thus
'OpenSCAD' is the installed version.

Admin - PM me if you need anything, or if I've done something stupid...

Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.

The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!

View this message in context: http://forum.openscad.org/OPENSCADPATH-and-command-line-tp19372p19387.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

copied to the appropriate Program Files for 32/64bit, and a shortcut manually added to the start/programs list. With the release numbers as part of the directory/shortcut name. Thus 'OpenSCAD' is the installed version. ----- Admin - PM me if you need anything, or if I've done something stupid... Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above. The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out! -- View this message in context: http://forum.openscad.org/OPENSCADPATH-and-command-line-tp19372p19387.html Sent from the OpenSCAD mailing list archive at Nabble.com.

TP

Torsten Paul

Sun, Nov 27, 2016 9:30 PM

On 11/27/2016 10:25 PM, MichaelAtOz wrote:

Barring that, normally nice installers would update the installation,
including removing old/redundant files & settings (including registry).

Thus I would not expect a 32 bit & 64 bit to be able to co-exist, via an
'installer'.

That's the thing, I'm not sure a 32-bit installer can actually access
the 64bit registry at all. It's enclosed into it's "WOW" cage which
looks to the process as normal but in fact is a special branch in the
registry.

ciao,
Torsten.

On 11/27/2016 10:25 PM, MichaelAtOz wrote: > Barring that, normally nice installers would update the installation, > including removing old/redundant files & settings (including registry). > > Thus I would not expect a 32 bit & 64 bit to be able to co-exist, via an > 'installer'. > That's the thing, I'm not sure a 32-bit installer can actually access the 64bit registry at all. It's enclosed into it's "WOW" cage which looks to the process as normal but in fact is a special branch in the registry. ciao, Torsten.

discuss@lists.openscad.org

OPENSCADPATH and command line

The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!

The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!