Path to petrify.lib should be only important for the technology mapping
Bug #1439238 reported by
Danil Sokolov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Workcraft |
Fix Committed
|
Low
|
Danil Sokolov | ||
Bug Description
Currently the path to petrify.lib is added as a parameter "-lib tools/petrify/
A solution is to move the path to petrify.lib to a dedicated parameter that will be appended to the petrify command line only for the technology mapping.
Related branches
lp:~danilovesky/workcraft/trunk-bug-1439238
- Danil Sokolov: Approve
-
Diff: 214 lines (+69/-4)8 files modifiedFsmPlugin/src/org/workcraft/plugins/fsm/VisualFsm.java (+9/-0)
FsmPlugin/src/org/workcraft/plugins/fsm/VisualState.java (+1/-1)
FstPlugin/src/org/workcraft/plugins/fst/tools/FstToFsmConverter.java (+15/-0)
PetrifyPlugin/src/org/workcraft/plugins/petrify/PetrifyUtilitySettings.java (+24/-1)
PetrifyPlugin/src/org/workcraft/plugins/petrify/tools/PetrifySynthesisTechnologyMapping.java (+13/-2)
WorkcraftCore/src/org/workcraft/gui/graph/tools/AbstractModelConverter.java (+1/-0)
WorkcraftCore/src/org/workcraft/gui/graph/tools/DefaultModelConverter.java (+4/-0)
WorkcraftCore/src/org/workcraft/gui/graph/tools/ModelConverter.java (+2/-0)
| Changed in workcraft: | |
| status: | In Progress → Fix Committed |
| summary: |
- Path to petrify.lib should be important for the technology mapping + Path to petrify.lib should be only important for the technology mapping |
| Changed in workcraft: | |
| importance: | Undecided → Low |
To post a comment you must log in.
