Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
L
LabComm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Sven Gestegård Robertz
LabComm
Commits
61d106a2
Commit
61d106a2
authored
13 years ago
by
Sven Robertz
Browse files
Options
Downloads
Patches
Plain Diff
changed wording in README
parent
e79e7ead
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
examples/simple/README
+3
-2
3 additions, 2 deletions
examples/simple/README
with
3 additions
and
2 deletions
examples/simple/README
+
3
−
2
View file @
61d106a2
...
@@ -13,8 +13,9 @@ the datagram directory contains the same example, but over datagram (UDP and raw
...
@@ -13,8 +13,9 @@ the datagram directory contains the same example, but over datagram (UDP and raw
When running compile.sh, Java and C files for the two samples defined in simple.lc will
When running compile.sh, Java and C files for the two samples defined in simple.lc will
be generated in the gen directory.
be generated in the gen directory.
run.sh will then run first the encoder, writing to encoded_data, and then the decoders written
run.sh will then run first the encoder, writing to encoded_data, and then a
in Java and C, respectively, reading from the previously written encoded_data.
decoder, reading from the previously written encoded_data written (in Java and
C, respectively).
NB! Before trying to build and run examples, make sure you have built the LabComm compiler
NB! Before trying to build and run examples, make sure you have built the LabComm compiler
by running "ant jar" in the main directory (../../ seen from here) and compiled the labcomm
by running "ant jar" in the main directory (../../ seen from here) and compiled the labcomm
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment