Allow installing OpenSim-Core into UNIX /usr/ or /usr/local

chrisdembia commented 10 years ago

The number of unix users is increasing. The organization of our installation currently does not permit one to safely install into /usr/ or /usr/local. The following changes should occur:

[x] On UNIX, do not copy over simbody libraries. #343
[x] Clean up CMake for api examples. #229
[x] Clean up CMake for lepton. #327
[x] Clean up "USING_NAMESPACE". #343
[x] Allow copying libraries to be an option. #343
[ ] Create versioned libraries (SOVERSION), as is now done with Simbody.
[x] Follow the FHS filesystem hierarchy standard for the layout of the installation. This is facilitated by using CMake GNUInstallDirs. (gnu-install-dirs; chrisdembia:unix-install-2) #671
- [x] configureOpenSim.m
- [x] location of Java wrapping (look at vtk).
- [x] location of python bindings (look at vtk). http://anonscm.debian.org/cgit/debian-science/packages/vtk6.git/tree/debian/python-vtk6.install, http://packages.ubuntu.com/trusty/amd64/python-vtk/filelist
[x] Rename the executables so their names are distinguishable. Right now, e.g., linux already has an id executable, and our id would overwrite this. I suggest a single executable that takes a tool name as an argument, or renaming the executables as opensim-ik, and creating an opensim executable that calls opensim-ik when opensim ik is called (this is how command-line git works I think).

chrisdembia commented 9 years ago

Reminder to self: https://github.com/chrisdembia/opensim-core/tree/unix-install-2

chrisdembia commented 9 years ago

next branches to merge: unix-dont-copy-simbody and unix-install-2

moorepants commented 9 years ago

@chrisdembia just came across this: http://click.pocoo.org

I think it is setup to do command line interfaces with lots of nested subcommands. Same guy that wrote Flask wrote this, so it is likely good. There example implements the git subcommands:

http://click.pocoo.org/3/complex/#complex-guide

Maybe you can use it for Opensim's command line access (although you'd have to provide Python then).

chrisdembia commented 9 years ago

Awesome!! Thanks for sharing that. That's exactly what I was thinking about. Having to use python might be a serious limitation though.

moorepants commented 9 years ago

I'm not sure how Python is a limitation :)

You can embed a Python interpreter with the open sim app on Windows and just use the system python on other OS's.

jimmyDunne commented 9 years ago

Rename the executables so their names are distinguishable. Right now, e.g., linux already has an id >executable, and our id would overwrite this. I suggest a single executable that takes a tool name as an >argument, or renaming the executables as opensim-ik, and creating an opensim executable that calls >opensim-ik when opensim ik is called (this is how command-line git works I think).

I just ran into this issue as well. Was struggling installing some python packages. The error isn't at first obvious because the exceptions are on tex-common/tex-live (font packages).

I fixed by deleting the opensim id since I don't use it from command line

chrisdembia commented 9 years ago

It sounds like we'll move toward opensim ik, opensim gui, etc.

sherm1 commented 9 years ago

It sounds like we'll move toward opensim ik, opensim gui, etc.

I hope this won't conflict with OpenSimulator! I see they use OpenSim.exe and OpenSim.ini but I didn't see a command line opensim.

tkuchida commented 9 years ago

I see they use OpenSim.exe and OpenSim.ini but I didn't see a command line opensim.

OpenSim.exe Command Line Options

sherm1 commented 9 years ago

OpenSim.exe Command Line Options

Oops! That's not good. I doubt we'll run into many users with both OpenSim and OpenSimulator (since they are totally unrelated) so we can probably just ignore that, but it is something to worry about. We could use osim instead, but opensim seems nicer.

chrisdembia commented 9 years ago

Thanks for those good finds. I'm okay with osim, though I agree that opensim is nicer. I think I'm okay with using opensim so long as popular package managers (apt-get, homebrew) don't install an OpenSimulator opensim or OpenSim executable into /usr/ or /usr/bin/. My end goal with the opensim umbrella executable is to support getting opensim into apt-get.

OpenSimulator is not in the apt-get repositories nor in homebrew.

sherm1 commented 9 years ago

OpenSimulator is not in the apt-get repositories nor in homebrew.

We should get there first!

aymanhab commented 9 years ago

So, what does it take to get in? On Oct 8, 2015 4:00 PM, "Michael Sherman" notifications@github.com wrote:

OpenSimulator is not in the apt-get repositories nor in homebrew.

We should get there first!

— Reply to this email directly or view it on GitHub https://github.com/opensim-org/opensim-core/issues/195#issuecomment-146711350 .

chrisdembia commented 9 years ago

Most of the items are at the top. The two other items I'd add are:

prototyping debian package config files (we have great examples in Simbody's repo thanks to OSRF).
getting someone at Debian to evaluate our package.

Homebrew would be really easy though.

jenhicks commented 1 year ago

@aymanhab thoughts on the status of this one?

opensim-org / opensim-core

Allow installing OpenSim-Core into UNIX /usr/ or /usr/local #195