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

Improve DIM dependencies and installation #798

Merged
merged 1 commit into from Jul 18, 2017

Conversation

dberzano
Copy link
Contributor

No description provided.

@dberzano
Copy link
Contributor Author

@Barthelemy with this installation method, this is what we get in the installation directory:

.
./test_server
./etc
./etc/modulefiles
./etc/modulefiles/dim
./etc/modulefiles/dim.unrelocated
./etc/profile.d
./etc/profile.d/init.sh.unrelocated
./etc/profile.d/init.sh
./did
./dim
./dim/dim_core.hxx
./dim/tokenstring.hxx
./dim/dic.h
./dim/dim.h
./dim/dim.hxx
./dim/dim_jni.h
./dim/dic.hxx
./dim/dicLorenzo.hxx
./dim/dim_common.h
./dim/dis.h
./dim/sllist.hxx
./dim/dllist.hxx
./dim/dis.hxx
./lib
./lib/libdim.so
./lib/libdim.a
./testServer
./testClient
./dim_send_command
./checkDns
./.build-hash
./dim_get_service
./webDid
./DimBridge
./checkDimServers
./.original-unrelocated
./test_client
./relocate-me.sh
./dns

which means that:

  • headers go in <prefix>/dim
  • executables in <prefix>
  • libraries in <prefix>/lib

The directory structure is very questionable... but it's there for compatibility :-(

What do you think?

( export OS=Linux
source setup.sh
gmake realclean
gmake X64=yes )
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what are those parentheses ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Those parentheses are like the Fight Club. Whatever happens there (environment-wise), stays there :-)

Jokes aside: it's an inner shell, so whatever export, etc. will not be available outside of them.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok thank you !

dim.sh Outdated
# Installation
rsync -av dim/ $INSTALLROOT/dim/ # headers
rsync -av --exclude "*.o" --exclude "*.so" --exclude "*.a" linux/ $INSTALLROOT/ # executables
mkdir $INSTALLROOT/lib && cp -v linux/*.{a,so} $INSTALLROOT/lib/ # libraries
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we have any ways a messy installation folder, I would not move the libs in lib and keep them in the top dir along with the binaries.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No problem for me, but you told me:

cp -r linux/*.a linux/*.so $INSTALLROOT/lib

What would your preferred way be then? Toplevel?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

toplevel, sorry I mislead you.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK update coming.

@Barthelemy
Copy link
Contributor

can be merged

@dberzano dberzano merged commit 7209e1d into alisw:master Jul 18, 2017
@dberzano dberzano deleted the improve-dim branch July 18, 2017 13:56
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.

None yet

2 participants