search

SeattleTestbed / nodemanager

Remote control server for SeattleTestbed nodes
MIT License
0 stars 10 forks source link

Add repy_v1 runtime and libraries to nodemanager build #112

Open aaaaalbert opened 9 years ago

aaaaalbert commented 9 years ago

Once #111 is merged, check choksi81@4adc8311509611d3fe908b7597e1fadc676f1ab3 (dependencies and build config for repy_v1) and amend it so that nodemanager builds have a correct, functional subdirectory containing the V1 runtime, repyV1.

Note that this precise name is required by the nmAPI.

aaaaalbert commented 9 years ago

Cross-checking with @XuefengHuang --- how much of the functionality to copy over files for the actual Repy (v1/v2) runtimes is still in your new installer-packaging scripts?

XuefengHuang commented 9 years ago

There are the actual Repy(v1/v2) runtimes in my installer-packaing.

# Nodemanager and RepyV2 runtime
DEPENDENCIES/nodemanager/* seattle_repy
DEPENDENCIES/portability/* seattle_repy
DEPENDENCIES/seattlelib_v2/* seattle_repy
DEPENDENCIES/repy_v2/* seattle_repy

# RepyV2 runtime for vessels
DEPENDENCIES/repy_v2/* seattle_repy/repy_v2
DEPENDENCIES/portability/* seattle_repy/repy_v2
DEPENDENCIES/seattlelib_v2/dylink.r2py seattle_repy/repy_v2
DEPENDENCIES/seattlelib_v2/textops.py seattle_repy/repy_v2
DEPENDENCIES/nodemanager/servicelogger.py seattle_repy/repy_v2

# RepyV1 runtime for vessels
DEPENDENCIES/repy_v1/* seattle_repy/repy_v1
aaaaalbert commented 9 years ago

Thanks for the quick reply. If we keep things like this, we will have to sync dependency updates between the installer-packaging and nodemanager build scripts (which I would rather not have to do, for obvious reasons).

The only other alternative I can think of right now would be modifying the build scripts to work recursively on selected dependencies. Let's discuss this in our next meeting.