You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I have never ever build or used C# code, I’ve searched the Internet to gather the build instructions in order to test this piece of awesome code. I still miss some instructions.
I mean something like this (note that these instructions are for Linux, specifically tested on Fedora 32; this is mostly already done):
# Install dotnet 3.1# Note: The code does not work with 5.0, which might be a good idea to improve.
sudo dnf -y install dotnet-sdk-3.1 openssl
# Clone the repository# Note: You could also use https://github.com/Ladder99/fanuc-driver.git.
git clone --recurse-submodules [email protected]:Ladder99/fanuc-driver.git
# Build
dotnet build /nowarn:CS0618 /nowarn:CS8632 /nowarn:CS1998 -p:DefineConstants=LINUX64 fanuc-driver/fanuc/fanuc.csproj
# Run
dotnet run /nowarn:CS0618 /nowarn:CS8632 /nowarn:CS1998 fanuc-driver/fanuc/fanuc.csproj
# Or rather this one?
fanuc-driver/fanuc/bin/Debug/netcoreapp3.1/fanuc
It would be awesome if the contents of config.yml (it is already done) and nlog.config would be documented, as currently I need to try what some of the configuration options need to do.
Also the command-line options (like --nlog or --config) should be documented.
The text was updated successfully, but these errors were encountered:
tukusejssirs
changed the title
Add build instructions including the list of dependencies
Add build instructions including the list of dependencies and improve the docs
Jun 8, 2021
This is mostly done in the docs now. A related issue I created today (as I’ve forgotten about this issue) is #29.
We might close this issue, although commands like cd ~ should be removed from the instructions. I’d rather use a variable with path where fanuc-driver would be cloned and the user could easily change it to whatever they want.
As I have never ever build or used C# code, I’ve searched the Internet to gather the build instructions in order to test this piece of awesome code. I still miss some instructions.
I mean something like this (note that these instructions are for Linux, specifically tested on Fedora 32; this is mostly already done):
It would be awesome if the contents of
(it is already done) andconfig.yml
nlog.config
would be documented, as currently I need to try what some of the configuration options need to do.Also the command-line options (like
--nlog
or--config
) should be documented.The text was updated successfully, but these errors were encountered: