new location for extensions?
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, LCMark
-
- VIP Livecode Opensource Backer
- Posts: 3581
- Joined: Mon Jan 22, 2007 7:36 am
- Location: Berkeley, CA, US
- Contact:
new location for extensions?
LC 9.1dp1 has the builtin extensions in a folder named "packaged_extensions" instead of "Extensions".
Is this an anomaly or should I count of this being the case moving forward?
Is this an anomaly or should I count of this being the case moving forward?
PowerDebug http://powerdebug.ahsoftware.net
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
-
- Livecode Opensource Backer
- Posts: 9446
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: new location for extensions?
Presumably you built this from source?LC 9.1dp1
-
- VIP Livecode Opensource Backer
- Posts: 3581
- Joined: Mon Jan 22, 2007 7:36 am
- Location: Berkeley, CA, US
- Contact:
Re: new location for extensions?
Hmmm... I'm getting the distinct impression that this is no longer the place to try to get answers.
PowerDebug http://powerdebug.ahsoftware.net
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
-
- VIP Livecode Opensource Backer
- Posts: 9850
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: new location for extensions?
In lieu of emoticons: ::laughing face:: ::sad face::
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
Re: new location for extensions?
@mwieder: As far as I'm aware the 9.1-dp-1 (when it appears) won't change anything in regards to where things are stored in a built/deployed distribution. When you build from source, it isn't quite the same though - the extensions are built into packaged_extensions (they always have been) and then the installer scripts build the deployed app and such based on the instructions in Installers/package.txt in the engine repository (which places the to-be-included extensions from packaged_extensions in Extensions).
-
- Livecode Opensource Backer
- Posts: 9446
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: new location for extensions?
That's what my wife and I discovered when we decided to have children.When you build from source, it isn't quite the same
Well, that all depends on your asking the right questions in the first place.this is no longer the place to try to get answers
Re: new location for extensions?
I would have answered, had it not been far and away beyond my level of knowledge
-
- VIP Livecode Opensource Backer
- Posts: 3581
- Joined: Mon Jan 22, 2007 7:36 am
- Location: Berkeley, CA, US
- Contact:
Re: new location for extensions?
LCMark- thanks for the details. That clears things up. I nonetheless had to adjust some PowerTools code to account for the fact that in my local build I wasn't seeing the builtin extensions, but it's good to know that things will keep on working the way they have in release versions.
bogs- given that, thanks for not answering.
bogs- given that, thanks for not answering.
PowerDebug http://powerdebug.ahsoftware.net
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
-
- Livecode Opensource Backer
- Posts: 9446
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: new location for extensions?
We all know who is being reproached here.
Re: new location for extensions?
@mwieder: You might want to use this instead - revEnvironmentExtensionsPath()
-
- Livecode Opensource Backer
- Posts: 9446
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: new location for extensions?
Will that make sure everything is in the right place, regardless of whether a build isrevEnvironmentExtensionsPath()
a release one or not?
Re: new location for extensions?
-
- VIP Livecode Opensource Backer
- Posts: 3581
- Joined: Mon Jan 22, 2007 7:36 am
- Location: Berkeley, CA, US
- Contact:
Re: new location for extensions?
LCMark-
Doh! I was trying to avoid that in order to maintain backward compatibility, but it finally sank in that for earlier versions we wouldn't have extensions anyway, so I'm good with that. Thanks for the jolt of reality. All I need to do is wrap it in a try clause and it's taken care of
Doh! I was trying to avoid that in order to maintain backward compatibility, but it finally sank in that for earlier versions we wouldn't have extensions anyway, so I'm good with that. Thanks for the jolt of reality. All I need to do is wrap it in a try clause and it's taken care of
Code: Select all
try
put revEnvironmentExtensionsPath() into tPath
catch e
end try
if tPath is not empty then ...
PowerDebug http://powerdebug.ahsoftware.net
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev