Skip to content

Commit

Permalink
add hint for dll, update install of wheels (#1)
Browse files Browse the repository at this point in the history
  • Loading branch information
KVB-MLX authored Aug 28, 2024
1 parent bb89305 commit c9c5b0d
Show file tree
Hide file tree
Showing 7 changed files with 8 additions and 11 deletions.
8 changes: 2 additions & 6 deletions MeLiBu_high_level/python_mbdf_parser/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,7 @@ Follow steps:

1. Start the PowerShell as admin
2. Use command cd folder_path to go to this folder (...\MeLiBu_high_level\python_mbdf_parser)
3. Get a list of all Melexis python wheels in folder. Use following command:
3. Install Melexis python wheels to the SALEAE logic folder. Please update the target folder according to your installation!
```
$WHEEL_FILES = get-childitem *.whl
pip install --target "C:\Program Files\Logic\resources\windows-x64\pythonlibs\lib\site-packages" -r py-requirements.txt
```
4. Install Melexis python wheels to the SALEAE logic folder. Please update the target folder according to your installation!
```
pip install --target "C:\Program Files\Logic\resources\windows-x64\pythonlibs\lib\site-packages" pathlib $WHEEL_FILES
```
9 changes: 5 additions & 4 deletions MeLiBu_high_level/python_mbdf_parser/py-requirements.txt
Original file line number Diff line number Diff line change
@@ -1,8 +1,9 @@
# public
#natsort==7.1.0
#pyparsing==2.4.7
natsort==7.1.0
pathlib

# melexis
./*.whl

pymlxabc-9.0.0-py3-none-any.whl
pymlxexceptions-0.5.0-py3-none-any.whl
pymelibuframe-5.0.4-py3-none-any.whl
pymbdfparser-2.4.0-py3-none-any.whl
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ For MeLiBu, both low level and high level analyzers are implemented.

This folder contains visual studion project files and initial built dll. To make changes to code open .sln file with visual studio and when the code is changed rebuild solution in release mode.

New dll is now located in `MeLiBu_low_level\build\Analyzers\Release`.
New dll is now located in `MeLiBu_low_level\build\Analyzers\Release` (pre-build available within the release artifact).

New dll can be copied to `MeLiBu_low_level\Release` folder and this folder can be used in Logic app or Custom Low Level Analyzer folder can be set to folder where new dll is.

Expand Down

0 comments on commit c9c5b0d

Please sign in to comment.