Merge lp:~yrke/tapaal/tapaal-newlocateverifytapn into lp:tapaal
Proposed by
Kenneth Yrke Jørgensen
Status: | Merged |
---|---|
Approved by: | Jiri Srba |
Approved revision: | 552 |
Merged at revision: | 665 |
Proposed branch: | lp:~yrke/tapaal/tapaal-newlocateverifytapn |
Merge into: | lp:tapaal |
Diff against target: |
186 lines (+111/-6) 4 files modified
src/dk/aau/cs/verification/UPPAAL/Verifyta.java (+10/-2) src/dk/aau/cs/verification/VerifyTAPN/VerifyTAPN.java (+32/-2) src/net/tapaal/TAPAAL.java (+67/-0) src/pipe/gui/CreateGui.java (+2/-2) |
To merge this branch: | bzr merge lp:~yrke/tapaal/tapaal-newlocateverifytapn |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Mathias Andersen (community) | Approve | ||
Jiri Srba | Approve | ||
Jakob Taankvist | Pending | ||
Review via email: mp+94156@code.launchpad.net |
Commit message
Merged branch tapaal-
Improved search for verifytapn
Description of the change
Changes the serach order for verifytapn
1) Search for it to be set via env variable
2) Search the "install"/run dir for bin/verifytapn
The chagne assumes that the jar/class files are placed in lib/ and verifytapn is placed in bin
This means the bat script is no longer needed in order to run TAPAAL on windows
To post a comment you must log in.
There is a problem here. The engine can be called verifytapn or verifytapn64, depending on the version. I would like to keep the different names different, so that if a user reports a bug,
we can see (Tools/Verification engines) what version is he/she using. Perhaps you can check
for both variants in the bin directory and prefer the 32 bit version of both are present?