Migration Guide to Allegro

Migration Guide for Allegro Platform Products

Issue link: https://resources.pcb.cadence.com/i/1180190

Contents of this Issue

Navigation

Page 77 of 128

Migration Guide for Allegro Platform Products Core Allegro Platform Back-End Products October 2019 78 Product Version 17.4-2019 © 1999-2019 All Rights Reserved. Compatibility with other tools in the Allegro Platform 17.4 PCB Editor must be used with 17.x System Capture, Design Entry HDL and SCM. A mixed environment, such as 16.x and 17.x, is not supported. ❑ With 17.2 PCB Editor and 16.6 Front-end (Design Entry HDL or SCM), PCB Editor can import netlists but back-annotation fails. ❑ With 17.2 front-end applications (Design Entry HDL or SCM) and 16.6 PCB Editor, PCB Editor cannot import netlists but back-annotation works. ❑ The exception to this is if you are using a non-constraint manager enabled flow where a mix 16.6/17.2 will work. SKILL ■ New SKILL APIs are available, documentation has also been updated to reflect APIs added in the intermittent releases. ■ Due to 64bit migration, SKILL contexts must be rebuilt for 17.4 and placed in the a 64bit sub-directory. ■ If you obtain SKILL contexts from third parties, such as Ansoft or Cadence VARs, you need to obtain new 64bit compatible contexts from those vendors. Your 32bit 16.6 contexts will not work in 17.4 ■ If you use the axlDllOpen API, you must rebuild your dll/shared library as 64bit binary. On Windows, you must use Visual Studio 2012 or newer version, and on Linux use gcc 4.8.3. ■ Calls to axlShell due to script changes may not be compatible. ■ A new menu item cannot be added for a command using axlUIMenuInsert if there is an existing menu item for that command. Removed Commands ■ The following place commands have been removed: ❑ place insight ❑ place interactive ■ IGES format batch commands have been removed: ❑ iges_in

Articles in this issue

view archives of Migration Guide to Allegro - Migration Guide for Allegro Platform Products