Hello,
I initially setup Komodo 12 in Windows 10 to use Strawberry Perl. I would like to change the configuration to instead use ActiveState Perl.
How can I confirm my ActiveState Perl configuration in Windows? It seems to arrive as part of the ActiveState State Tool.
Once I confirm that ActiveState Perl remains properly configured, what paths etc. do I use to configure Komodo Perl Language Preferences with ActiveState Perl ?
Thanks,
Wil Blake
One note I can make is that once you have your Perl install working and you understand how the state tool works with it, then either you need to start Komodo from the terminal you state activate in or get state activate working in Komodo itself which is what we are discussing in your other forum thread.
Thank you. I’m getting an error about switch.pm though I tried to install it in the Perl configuration.
How do I complete other Perl setup options :
PPM location?
cpan location?
cpanm location?
Additional Perl Import Directories?
@wblake, the State Tool will manage your Perl install.
You can install that package 3 different ways (2 are basically the same):
In Komodo, select the State Tool side bar menu > Run Command > then run state install [pacakge name]
In your projects folder, in a CMD terminal, in an Activate State (state activate) you can run `state install [package name]
Install it using the Platform Dashboard: Open you activestate.yaml file, put the URL in the Project: field in a browser window > Login (if you’re not already) > Configuration tab > Install Package
platform.activestate.com + the State Tool is how you should manage your environment if when using this tool chain setup.
Thanks again. Still another error ensues.
“The Platform failed to resolve the dependencies for this build \n Because root depends on every version of Feature |language|perl|switch which doesn’t match any versions, version solving failed.”
Thanks @wblake. I’m really not sure what that error means. I recommend looking at your project at platform.activestate.com though. It’ll perhaps make it easier to see what’s going on.
When you share error output from a terminal, always share the command you ran. It may seem obvious to you what you ran but there could be some nuance that is missing.