Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update compilation-instructions.md #828

Merged
merged 1 commit into from
Nov 21, 2024

Conversation

maxistar
Copy link
Contributor

@maxistar maxistar commented Nov 3, 2024

There are inconsistent file names in the instructions for compiling binaries: fift and func are mentioned without a directory, while other executables include a directory. Sometimes the directory is prefixed with ./, and other times it’s not. I suggest consistently using the ./ notation, as it follows standard Unix conventions.

Why is it important?

This change would improve the consistency of the information, make it more reproducible, and speed up the process of mass adoption of the technology.

There are inconsistent file names in the instructions for compiling binaries: fift and func are mentioned without a directory, while other executables include a directory. Sometimes the directory is prefixed with ./, and other times it’s not. I suggest consistently using the ./ notation, as it follows standard Unix conventions. This change would improve the consistency of the information, make it more reproducible, and speed up the process of mass adoption of the technology.
@reveloper
Copy link
Contributor

@maxistar, thank you!

@reveloper reveloper merged commit 1723786 into ton-community:main Nov 21, 2024
github-actions bot pushed a commit to TownSquareXYZ/ton-docs that referenced this pull request Nov 22, 2024
There are inconsistent file names in the instructions for compiling binaries: fift and func are mentioned without a directory, while other executables include a directory. Sometimes the directory is prefixed with ./, and other times it’s not. I suggest consistently using the ./ notation, as it follows standard Unix conventions. This change would improve the consistency of the information, make it more reproducible, and speed up the process of mass adoption of the technology.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants