How can I install imagick in current enabled PHP version?

may help you . I installed imagemagic and imagick successfully (using http://www.php.net/manual/en/imagick.installation.php#94169 steps ) and also put extension=imagick.so. but when i restart apache i am getting following error. , edit file

/Applications/MAMP/Library/bin/envvars

DYLD_LIBRARY_PATH="/Applications/MAMP/Library/lib:$DYLD_LIBRARY_PATH"
export DYLD_LIBRARY_PATH

hop of those help? ImageMagick is the distribution library, you have to now install php-imagick, or something along those lines for your distro.
Check PHP documentation, this can be done through PECL sudo pecl install imagick:

I wish this help you afaik, you'll either need an older installer (and some luck on the repos) or someone's older package directory and installer. All recent installers only go back one release which won't be enough to get you back in line with Clion's requirement.
Might also be worth reaching out to Clion and asking them when support for the recent versions is coming out.

will be helpful for those in need Your biggest issue is that the current portage tree does not contain a 2.5 package, and I suspect it's telling you 2.7 doesn't exist because you have not updated your tree (emerge --sync) in a long time. Any Python2 update you do will want to migrate you away from 2.5 and to 2.7. To maintain 2.5 as a portage supported atom, you would need to enable an overlay that supports it. A quick search found that the dberkholz and embedded-cross overlays might be a good place to start. At least at one time, they included python-2.5. You will need to use layman (Layman Wiki) to get these.
A better alternative might be to do an update (which should give you 2.7), and then install 2.5 manually. You will need to manage your environment properly, especially if your 2.5 modules are not command-line launched. A good place to start would be here: Eselect dev guide. That link will show you how to take your custom, non-supported build (python-2.5), and have the system recognize it. This way, you can keep your box current, keep your 2.5 python, and use eselect to do things the "proper way."

wish help you to fix your issue I reproduced your issue on my side. After some investigation, I found a way to make both Imagick and Composer work on Azure WebApp. I know it is not beautiful, however, it does work.
1) Go into D:\home\SiteExtensions\ComposerExtension fodler using FTP or SCM (websitename.SCM.azurewebsites.net), and delete applicationHost.xdt file.

<configuration xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform"> 
   <system.applicationHost>
     <sites>
       <site name="%XDT_SCMSITENAME%" xdt:Locator="Match(name)">
         <application path="/Composer"  applicationPool="%XDT_APPPOOLNAME%" xdt:Transform="Insert">
          <virtualDirectory path="/" physicalPath="%XDT_EXTENSIONPATH%" />
        </application>
      </site>
    </sites>
  </system.applicationHost>
  <system.webServer> 
    <runtime xdt:Transform="InsertIfMissing"> 
      <environmentVariables xdt:Transform="InsertIfMissing"> 
        <add name="MAGICK_HOME" value="d:\home\site\ext\" xdt:Locator="Match(name)" xdt:Transform="InsertIfMissing" /> 
        <add name="MAGICK_CODER_MODULE_PATH" value="d:\home\site\imagickwin\" xdt:Locator="Match(name)" xdt:Transform="InsertIfMissing" /> 
        <add name="APPSETTING_COMMAND" value="%HOME%\SiteExtensions\ComposerExtension\Hooks\deploy.cmd" />
        <add name="COMPOSER_ARGS" value="--prefer-dist --no-dev --optimize-autoloader --no-progress" />
        <add name="PATH" value="%PATH%;%PATH%d:\home\site\ext\;%HOME%\SiteExtensions\ComposerExtension\Commands;%APPDATA%\Composer\vendor\bin" />
      </environmentVariables> 
    </runtime> 
    <rewrite xdt:Transform="InsertIfMissing">
      <rules xdt:Transform="InsertIfMissing">
        <rule name="RequestBlockingRule1" xdt:Locator="Match(name)" xdt:Transform="InsertIfMissing" stopProcessing="true">
            <match url=".*" />
            <conditions>
                <add input="{URL}" pattern="vendor/(.*)$" />
            </conditions>
            <action type="CustomResponse" statusCode="403" statusReason="Forbidden: Access is denied." statusDescription="You do not have permission to view this directory or page using the credentials that you supplied." />
        </rule>
      </rules>
    </rewrite>
  </system.webServer> 
</configuration>