Wine running on MacOS #139
Comments
|
Hi, Is that something you could try? |
|
@nimrof I have downloaded v4.2.2 from Releases. 
# my command 1
dotnet EDSEditor.exe --infile something.xdd --outfile something.eds
# my command 2
dotnet exec EDSEditor.exe --infile something.xdd --outfile something.eds
# the result for both cases
It was not possible to find any compatible framework version
The framework 'Microsoft.WindowsDesktop.App', version '6.0.0' (arm64) was not found.
- No frameworks were found.
You can resolve the problem by installing the specified framework and/or SDK.
The specified framework can be found at:
- https://aka.ms/dotnet-core-applaunch?framework=Microsoft.WindowsDesktop.App&framework_version=6.0.0&arch=arm64&rid=osx.11.3-arm64
May be have I executed command not correctly? |
Yes #cd EDSSharp
#dotnet --framwork net6.0 runIf that works it should be building the cli program and running it. |
|
@nimrof # command in EDSSharp folder
dotnet --framwork net6.0 run
# result
Could not execute because the specified command or file was not found.
Possible reasons for this include:
* You misspelled a built-in dotnet command.
* You intended to execute a .NET program, but dotnet---framwork does not exist.
* You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH.If the framework allows to be executed on MacOS could you post releases with such package in future? |
|
@nimrof Still in progress, or should we close it? |
technical still in progress, but only waiting for a release |
|
@ruziev-dev The CLI tool is in the net8.0 folder |
|
@nimrof Could you help me with correct cli command? I have tried but it does not working dotnet EDSSharp.exe --infile something.xdd --outfile something.eds
|
Hi dont have mac so only testet on linux, and i get the same error if i use dotnet, but if i just use |
|
looks like ➜ net8.0 dotnet EDSSharp.dll
Usage: EDSEditor --infile file.[xdd|eds] --outfile [valid output file] [OPTIONAL] --type [exporter type]
The output file format depends on --outfile extension and --type
If --outfile extension matcher one exporter then --type IS NOT needed
If --outfile extension matcher multiple exporter then --type IS needed
If --outfile has no extension --type IS needed
Exporter types:
ElectronicDataSheet [.eds]
DeviceConfigurationFile [.dcf]
CanOpenNode [.h,.c]
CanOpenNodeV4 [.h,.c]
CanOpenXDDv1.0 [.xdd]
CanOpenNetworkv1.0 [.nxdd]
CanOpenXDDv1.1 [.xdd]
CanOpenXDDv1.1stripped [.xdd]
CanOpenXDCv1.1 [.xdc]
CanOpenNetworkXDDv1.1 [.nxdd]
CanOpenNetworkXDCv1.1 [.nxdc]
CanOpenNodeProtobuf(json) [.json]
CanOpenNodeProtobuf(binary) [.binpb]
DocumentationHTML [.html]
DocumentationMarkup [.md]
NetworkPDOReport [.md]But if I call with not enough arguments it shows me usage info, but if arguments are enough it executes but nothing changes in directory. 
|
Sorry for the delay, it should probably output a error when given a unsupported filetype instead of silence. Its on the todo-list |
I'm using MacOS for development.
CANopenEditor GUI application works good through the Wine.
But CLI tools are not available.
# test command wine cmd /c CANopenEditor/EDSEditor.exe --infile something.xdd --outfile something.edsThe command above load and run GUI program
I need it to automate project builds.
Does anybody know how to automatically export CANopenNode files from different
xddorxpdfiles with Wine?The text was updated successfully, but these errors were encountered: